Bug #2734
closed
"/etc/init.d/rudder-agent restart" is broken
Added by Gonéri Le Bouder almost 12 years ago.
Updated about 9 years ago.
Description
root@srv00015:/srv/tftp# ps aux|grep cf
root 31306 0.0 0.0 6028 684 pts/1 S+ 21:48 0:00 grep cf
root@srv00015:/srv/tftp# /etc/init.d/rudder-agent start
rudder-agent[31315]: [INFO] Using /etc/default/rudder-agent for configuration
rudder-agent[31318]: [INFO] Using /var/rudder/cfengine-community for Cfengine workdir
rudder-agent[31319]: [INFO] Launching Cfengine Community cf-serverd...
rudder-agent[31325]: [OK] Cfengine Community cf-serverd started after 1 seconds
rudder-agent[31326]: [INFO] Launching Cfengine Community cf-execd...
rudder-agent[31333]: [OK] Cfengine Community cf-execd started after 1 seconds
root@srv00015:/srv/tftp# ps aux|grep cf
root 31322 0.0 0.0 35492 2740 ? Ss 21:49 0:00 /var/rudder/cfengine-community/bin/cf-serverd
root 31330 0.0 0.0 35404 2468 ? Ss 21:49 0:00 /var/rudder/cfengine-community/bin/cf-execd
root 31335 0.0 0.0 6028 684 pts/1 S+ 21:49 0:00 grep cf
root@srv00015:/srv/tftp# /etc/init.d/rudder-agent restart
rudder-agent[31343]: [INFO] Using /etc/default/rudder-agent for configuration
rudder-agent[31346]: [INFO] Using /var/rudder/cfengine-community for Cfengine workdir
rudder-agent[31347]: [INFO] Halting Cfengine Community cf-serverd...
rudder-agent[31351]: [OK] Cfengine Community cf-serverd stopped after 2 seconds
rudder-agent[31352]: [INFO] Halting Cfengine Community cf-execd...
rudder-agent[31356]: [OK] Cfengine Community cf-execd stopped after 2 seconds
rudder-agent[31357]: [INFO] Launching Cfengine Community cf-serverd...
rudder-agent[31363]: [OK] Cfengine Community cf-serverd started after 1 seconds
rudder-agent[31364]: [INFO] Launching Cfengine Community cf-execd...
rudder-agent[31486]: [ALERT] no PID file for cf-execd after 30 seconds. Trying again...
Hum, the agent managed to start after 2 retry.
The server hostname is in /etc/hosts and I use the IP address in /var/rudder/cfengine-community/policy_server.dat.
Did you launch /opt/rudder/sbin/cf-agent ?
I just started "/etc/init.d/rudder-agent start" after the package installation.
Do you have a cf-execd running when you launch "ps aux|grep cf-execd" ?
The init scripts have no LSB header and are started all in parallel whereas it's not expected. See:
- Status changed from New to Discussion
- Assignee changed from Jonathan CLARKE to Gonéri Le Bouder
- Target version set to 2.4.0~beta4
Gonéri, am I right in understanding that this happens on a Debian Wheezy system, or also on Squeeze?
What makes you think that this is related to the boot order sequence? I'm not sure I understand the link.
I'd like to fix this in the next upcoming 2.4 beta version if possible.
This is a Squeeze system.
Gonéri Le Bouder wrote:
This is a Squeeze system.
OK, thanks for confirming.
Then can you explain what makes you think this is related to not having LSB-headers? (I agree that we should add them, but that's already in another ticket, I'm just not sure where this bug comes from...)
- Assignee changed from Gonéri Le Bouder to Matthieu CERDA
- Target version changed from 2.4.0~beta4 to 2.4.0~rc1
Let's see if this still happens when we've added the LSB headers
- Assignee changed from Matthieu CERDA to Nicolas PERRON
- Status changed from Discussion to 2
- Priority changed from N/A to 3
I'm not sure to understand the problem here, but it can't be related to non-LSB header since there are LSB header in rudder-agent init script.
I suppose the related issue is: #2735
I don't think there is a problem at all. the LSB header seem valid.
Gonéri Le Bouder wrote:
I don't think there is a problem at all. the LSB header seem valid.
Ok, then I suppose we can reject this bug.
Reject? There where no LSB header when did my test.
Gonéri Le Bouder wrote:
Reject? There where no LSB header when did my test.
Are you sure ? I've just checked and the LSB header exist on rudder-agent at least since Rudder 2.3.0 .
- Status changed from 2 to Rejected
Gonéri Le Bouder wrote:
I don't think there is a problem at all. the LSB header seem valid.
Thanks for confirming Gonéri.
cf-execd sometimes takes a while to stop gracefully, which is what you're seeing here, I think.
This is unrelated to LSB headers, which have been in the rudder-agent init script since the original 2.3.0 release in October 2011.
Marking this bug as "Rejected", since there is no actual bug here. Feel free to re-open if you disagree, or we have misunderstood you.
- Target version changed from 2.4.0~rc1 to 2.4.0~beta5
- Project changed from Rudder to 34
- Category deleted (
11)
- Project changed from 34 to Rudder
- Category set to Packaging
Also available in: Atom
PDF
Updated by 
Updated by Nicolas PERRON 
Updated by Matthieu CERDA 
Updated by 
Updated by