User story #856
closed
Make promises in order to assure that Rudder services are still running
Added by Jonathan CLARKE about 13 years ago.
Updated about 12 years ago.
Category:
System techniques
Description
It would be unfortunable if Rudder root server didn't work since one of its necessary service has been stopped (slapd, jetty, apache, postgres).
Promises could be made in order to assure that these process are running or to start them if not.
- Assignee set to Matthieu CERDA
- Priority changed from N/A to 3
- Priority changed from 3 to 4
- Target version deleted (
8)
- Assignee deleted (
Matthieu CERDA)
- Target version changed from 10 to 24
- Target version changed from 24 to 18
- Priority changed from 4 to 3
- Subject changed from Faire des promesses pour s'assurer que les services du serveur racine sont lances to Make promises in order to assure that Rudder services are still running
- Description updated (diff)
- Target version changed from 18 to 2.4.0~alpha1
- Target version changed from 2.4.0~alpha1 to 2.4.0~alpha2
- Target version changed from 2.4.0~alpha2 to 2.4.0~alpha3
- Target version changed from 2.4.0~alpha3 to 2.4.0~alpha4
- Status changed from New to In progress
- Assignee set to Matthieu CERDA
- % Done changed from 0 to 70
This task has been cut up into several smaller ones:
- #2202: PT distributePolicy: Check if all the core rudder daemons are launched and set to start on boot
- #2203: PT common: Make the common PT copy the CFengine binaries from /opt/rudder/sbin to sys.workdir/bin
- #2207: PT distributePolicy : Implement the SuSE postgresql configuration hack in the distributePolicy
- #2209: PT distributePolicy : Copy the logrotate configuration if not present
- #2210: PT distributePolicy : Implement an integrity check to warn the user if the configuration-repository directory is absent
- #2211: PT distributePolicy : Check if the WebDAV password is OK
- #2213: PT distributePolicy: LDAP password synchronization
- #2222: PT distributePolicy: Check status of webapp and endpoint, and restart jetty if several continuous tests fail
- Target version changed from 2.4.0~alpha4 to 2.4.0~alpha5
- Status changed from In progress to Released
- % Done changed from 70 to 100
All subtasks have now been addressed!
Also available in: Atom
PDF
Updated by Matthieu CERDA 
Updated by 
Updated by 
Updated by Nicolas PERRON