[Buildbot-devel] Buildbot under Centos 4.2 causes exit code 129 when running ant build step

Daren Grant d.grant at psenterprise.com
Tue Nov 29 12:46:34 UTC 2005

[  > From: "Daren Grant" <d.grant at psenterprise.com> Exception in thread 
[  > "SIGHUP handler"
[  > java.lang.IllegalThreadStateException
[  From: "Brian Warner" 
[  So, I don't know if would make a difference, but since the 
[  problem appears to be related to a SIGHUP, you might 
[  investigate nohup.
[  good luck,
[   -Brian

Thanks for the pointer to nohup Brian,  using nohup results in a
successful build, however no logs and no status can be extracted as
everything gets written to hohup.out.  I would prefer to find the root
of the problem and fix that compared to a dirty hack, and so the battle

A slightly cleaner workaround that works is to place the ant command in
a script and run the script as this too results in the ant command
sucessfully executing, but this time all the output and return status
can be handled.  My guess is that all java processes are going to have
this problem on my setup and not just ant.

I have been scouring through the buildbot code attempting to find out
why the ant task succeeds on suse 9.1 with kernel 2.4.21 but dies on
Centos 4 with kernel 2.6.9-22.  It is definitely linked to SIGHUP, but
why is the ant command receiving a SIGHUP signal ?  I've found a comment
within buildbot/slave/commands.py<Line 80> that talks about a bug in
recent debian glibc and SIGHUP.  Could this be related ?

More information about the devel mailing list