[Buildbot-commits] [Buildbot] #2454: SiGHUP doesn't always work

[Buildbot trac]

#2454: SiGHUP doesn't always work
--------------------+------------------------
Reporter:  virgilg  |       Owner:
    Type:  defect   |      Status:  new
Priority:  major    |   Milestone:  undecided
 Version:  0.8.7p1  |  Resolution:
Keywords:           |
--------------------+------------------------

Comment (by virgilg):

 I installed the same buildbot instance on Linux (creating my own Debian
 packages from 0.8.7-p1):
 # uname -r
 2.6.32-5-amd64
 # dpkg -l python buildbot
 ii  buildbot         0.8.7p1-1
 ii  python           2.7.3-3
 # cat /etc/debian_version
 7.0

 # gdb -p 5170
 (gdb) info threads
   Id   Target Id         Frame
   10   Thread 0x7f8ce7d6d700 (LWP 5172) 0x00007f8cee64b420 in sem_wait ()
 from /lib/x86_64-linux-gnu/libpthread.so.0
   9    Thread 0x7f8ce756c700 (LWP 5174) 0x00007f8cee64b420 in sem_wait ()
 from /lib/x86_64-linux-gnu/libpthread.so.0
   8    Thread 0x7f8ce6d6b700 (LWP 5175) 0x00007f8cee64b420 in sem_wait ()
 from /lib/x86_64-linux-gnu/libpthread.so.0
   7    Thread 0x7f8ce656a700 (LWP 5176) 0x00007f8cee64b420 in sem_wait ()
 from /lib/x86_64-linux-gnu/libpthread.so.0
   6    Thread 0x7f8ce5d69700 (LWP 5178) 0x00007f8cee64b420 in sem_wait ()
 from /lib/x86_64-linux-gnu/libpthread.so.0
   5    Thread 0x7f8ce5568700 (LWP 5179) 0x00007f8cee64b420 in sem_wait ()
 from /lib/x86_64-linux-gnu/libpthread.so.0
   4    Thread 0x7f8ce494b700 (LWP 5217) 0x00007f8cee64b420 in sem_wait ()
 from /lib/x86_64-linux-gnu/libpthread.so.0
   3    Thread 0x7f8cdffff700 (LWP 5218) 0x00007f8cee64b420 in sem_wait ()
 from /lib/x86_64-linux-gnu/libpthread.so.0
   2    Thread 0x7f8cdf7fe700 (LWP 5219) 0x00007f8cee64b420 in sem_wait ()
 from /lib/x86_64-linux-gnu/libpthread.so.0
 * 1    Thread 0x7f8ceea6c700 (LWP 5170) 0x00007f8cedae23e5 in __xstat64 ()
 from /lib/x86_64-linux-gnu/libc.so.6

 # strace -p 5170
 stat("events_submittalmachine.company.com/48838284", 0x7fff20b33b80) = -1
 ENOENT (No such file or directory)
 stat("events_submittalmachine.company.com/48838285", 0x7fff20b33b80) = -1
 ENOENT (No such file or directory)
 stat("events_submittalmachine.company.com/48838286", 0x7fff20b33b80) = -1
 ENOENT (No such file or directory)
 stat("events_submittalmachine.company.com/48838287", 0x7fff20b33b80) = -1
 ENOENT (No such file or directory)
 stat("events_submittalmachine.company.com/48838288", 0x7fff20b33b80) = -1
 ENOENT (No such file or directory)
 stat("events_submittalmachine.company.com/48838289", 0x7fff20b33b80) = -1
 ENOENT (No such file or directory)
 stat("events_submittalmachine.company.com/48838290", 0x7fff20b33b80) = -1
 ENOENT (No such file or directory)
 stat("events_submittalmachine.company.com/48838302", 0x7fff20b33b80) = -1
 ENOENT (No such file or directory)
 …

 # service buildmaster restart
 Restarting buildmaster "WirelessAutomation" ... failed!

 # kill -SIGTERM 5170; ps ax|grep -i twi
  5170 ?        Rl    15:30 /usr/bin/python -c from twisted.scripts import
 twistd; twistd.run() --no_save --logfile=twistd.log --python=buildbot.tac

 # kill -SIGHUP 5170; ps ax|grep -i twi
  5170 ?        Rl    15:40 /usr/bin/python -c from twisted.scripts import
 twistd; twistd.run() --no_save --logfile=twistd.log --python=buildbot.tac

 # kill -SIGKILL 5170; ps ax|grep -i twi
 Nothing. Finally killed.

 Therefore the problem appears to be in the submittal code and unrelated to
 something specific to Python on OS X.
 This confirms my hypothesis that other colleagues using buildbot on OS X
 but not using the submit code did not see this.

-- 
Ticket URL: <http://trac.buildbot.net/ticket/2454#comment:5>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation