On Fri, 10 Jun 2016 11:32:02 +0200 John Paul Adrian Glaubitz 
<glaub...@physik.fu-berlin.de> wrote:
> 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.

could this be the same problem as #577421?


cheers, josch

Attachment: signature.asc
Description: signature

Reply via email to