On 04/23/2013 09:06 AM, Bradley M. Kuhn wrote:
Ken Causey wrote at 22:25 (EDT) on Monday:
When it is convenient for you could you please reboot that system?
I did a reboot, just now. Sorry that Gandi's interface doesn't allow me to delegate that to one of you.
Hopefully the system came back up. I was out sick yesterday, but I'm online all day and findable on Freenode and other IRC networks if you need more help.
Yes, I checked for you on Freenode and was a bit worried when I didn't find you. ;)
Thanks for the reboot. As long as you don't mind us bugging you when we need this (hopefully rarely) I imagine we can deal with a bit of delay in the process.
It seems something has gone haywire with one or more of our Jenkins build tasks on build.squeak.org (aka box3.squeak.org, 173.246.101.237) resulting in the system being unresponsive now for some hours.
Another of Conservancy's projects is using Jenkins and they noticed they needed a LOT of RAM to make it work. Do you perhaps need more RAM? Was it an OOM error that caused this?
At this point I have no idea. OOM is a definite possibility but I doubt Jenkins is to blame. We are still working out issues with our customization of the build system and really still learning how to adapt a Smalltalk view of the world to a Ruby/Java/Unix one. Those who actually deal with the Jenkins side of it (not me) will hopefully have more useful information than the hand-waving I am doing here.
Ken