Source: sbuild Version: 0.69.0-2 Severity: normal Hi!
I just ran into a minor annoyance with buildd-uploader after one of our sparc64 buildds crashed. buildd-uploader got stuck consuming lots of CPU time after being invoked by the cronjob after the machine was recovered after the crash. Looking into the daemon.log file, there was also no output from the uploader script to be seen. Since buildd-uploader worked fine for the other instances of the buildd on the same machine, I assumed it was some issue specific to this particular buildd user. Turns out, the lockfile was still there and keeping the buildd-uploader busy. After deleting the lockfile, the uploader works as expected again: root@atlantis:~# su - buildd buildd@atlantis:~$ touch buildd-uploader.lock buildd@atlantis:~$ /usr/bin/buildd-uploader ^C # stuck here buildd@atlantis:~$ rm buildd-uploader.lock buildd@atlantis:~$ /usr/bin/buildd-uploader buildd@atlantis:~$ I guess buildd-uploader should be modified to check for stale lockfiles and remove them. Cheers, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
