On Tuesday, March 6, 2012 9:17:57 PM UTC+1, John Hinnegan wrote: > > We recently set up a Jenkins server on OS X. We had been using Jenkins > prior to this in the cloud, but decided it was worth it to just buy a > little machine to do our builds for us. Now our Jenkins is going > unresponsive -- pretty consistently after 12-18 hours with only a couple of > days of observations. I don't know what the issue is, how can I diagnose? > > PS. The worst part of this is that the process doesn't die, it just stops > answering requests. If it would actually die, the the process manager would > restart it (which would be more acceptable) >
I had a similar issue that was caused by OutOfMemoryError due to insufficiant permGen space. I just commited https://github.com/jenkinsci/jenkins/commit/fb9f0679c7c75ea1e6c85bbe4f663896714bf63e which will allow you to configure this properly. If that is your problem you might want to modify: /Library/Application Support/Jenkins/jenkins-runner.sh<https://github.com/jenkinsci/jenkins/commit/fb9f0679c7c75ea1e6c85bbe4f663896714bf63e#diff-0> to contain that new line and configure the launch daemon appropriately using the defaults command. E.g. defaults write /Library/Preferences/org.jenkins-ci permGen 128M Cheers, Jerome
