Bug #10258
closed
If rudder server component is stopped on Rudder root server, it is never restarted
Added by Nicolas CHARLES almost 8 years ago.
Updated over 7 years ago.
Description
At least on Centos6, stoping cf-serverd means it will never restart
- Subject changed from If rudder server component is stopped, it is never restarted to If rudder server component is stopped on Rudder root server, it is never restarted
- Target version changed from 4.1.0~rc1 to 4.0.4
it used to be repaired in
2017-02-22T11:24:24+0100 info: /default/check_cf_processes/methods/'any'/default/check_cf_processes_running/processes/'/var/rudder/cfengine-community/bin/cf-serverd'[0]: Making a one-time restart promise for '/var/rudder/cfengine-community/bin/cf-serverd'
- Related to Bug #7381: Process management issues on nodes hosting LXC containers added
Ok, as discussed with Alexis, the correction should be in rudder agent check, that should check for cf-serverd component and start it if stopped.
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-agent/pull/110
- Status changed from Pending technical review to Pending release
- Related to Bug #10088: Inventory is not resent in case of error - and agent don't report the error added
- Status changed from Pending release to Released
- Priority set to 0
This bug has been fixed in Rudder 4.0.4 and 4.1.1 which were released today.
Also available in: Atom
PDF
Updated by 
Updated by