Well, it survived the night so it looks like that might have been the problem - thanks for the help!
On Monday, 10 November 2014 15:53:29 UTC, Charles Blessing wrote: > > I have a Windows-based master and a single OSX client. Builds are run on > the OSX client using the Jenkins slave agent which is launched manually by > downloading and running the appropriate jnlp file from the master web > server. > > Once running, builds and notifications progress as expected. > > However, approximately once a day - usually overnight when no builds are > running, the slave agent closes. Sometimes when I go to check it just isn't > running any more, once or twice it has crashed. I'm intending to gather > more information next time a crash occurs, although typically since > deciding to do this it has just been closing 'cleanly'. > > Unfortunately I'm not entirely sure when this started to happen as there > was an extended period of one project being left in a 'known broken state', > resulting in Jenkins getting turned off. > > Any suggestions on how to fix this situation would be much appreciated. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
