Actually, 502 gateway issues usually indicate that the HTTP proxy is timing
out -- meaning the application behind updates.jenkins-ci.org is taking too
long to respond. It's probably working beyond capacity (these are my
guesses without being able to actually see anything about it)
Doug J
I have a follow-up question. I've run into issues with some of my
slave.jar clients forking processes. A little less than 10% of the
executions result in:
$ /bin/bash -l -c "exit 0"
bash: xmalloc: ../bash/locale.c:73: cannot allocate 2 bytes (0 bytes allocated)
Exit status: 2
In the build log
