Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 438744

Summary: dev-util/buildbot-slave-0.8.3 init.d script reports crashed status
Product: Gentoo Linux Reporter: Yun Zheng Hu <hu>
Component: Current packagesAssignee: Python Gentoo Team <python>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: Normal    
Version: autobuilds   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Yun Zheng Hu 2012-10-17 21:08:39 UTC
The init.d script of buildbot-slave-0.8.3 seems to always report status 'crashed', even if buildslave succesfully started and is still running. Also the pid file is there and matches the process table.

I have no idea what causes this.

Example:

# /etc/init.d/buildslave status
 * status: stopped
# /etc/init.d/buildslave start
 * Starting buildslave in /home/buildbot/buildslave ...                                                                                [ ok ]
# /etc/init.d/buildslave status
 * status: crashed
# ps auxww | grep buildslave
buildbot  2572  0.0  0.6 188296 14088 ?        Sl   23:06   0:00 /usr/bin/python2.7 /usr/bin/twistd --no_save --logfile=/home/buildbot/buildslave/twistd.log --pidfile=/home/buildbot/buildslave/buildslave.pid --python=/home/buildbot/buildslave/buildbot.tac
# cat /home/buildbot/buildslave/buildslave.pid
2572
Comment 1 Mike Gilbert gentoo-dev 2012-10-18 00:55:07 UTC
What version of openrc are you using?
Comment 2 Johan Bergström 2012-10-18 00:58:06 UTC
Sounds like bug 397759. Could you make sure you have the latest version and try again?
Comment 3 Mike Gilbert gentoo-dev 2012-10-18 01:01:11 UTC
Ah, yeah that looks like the issue. Re-installing any version of buildbot-slave should pull in the new init script, which should resolve this.
Comment 4 Yun Zheng Hu 2012-10-18 08:34:20 UTC
Thanks, i re-emerged dev-util/buildbot-slave-0.8.3 and it works properly now.
Comment 5 Yun Zheng Hu 2012-10-27 20:01:46 UTC

*** This bug has been marked as a duplicate of bug 397759 ***