Bug #8049
closed
rudder-webapp and rudder-slapd does not register themself on boot on Debian 7
Added by Nicolas CHARLES over 8 years ago.
Updated over 7 years ago.
Category:
System techniques
Description
When installing 2.11.19, on a debian 7, I get no reports for check on boot rudder-jetty and rudder-slapd
Indeed, there are no /etc/rc2.d/S.*rudder-jetty nor rudder-slapd
so service is not registered at boot
There is no report, because we are promising on an empty promiser (file is not there -> nothing to promise -> no class created -> no repair)
This may happen also on 3.0, 3.1 and 3.2
Ok, this happened already in 2.11.17
- Related to Bug #6833: System techniques tries to add old services at boot added
does not happen on 3.0 nor 3.1
- Target version changed from 2.11.20 to 2.11.21
- Target version changed from 2.11.21 to 2.11.22
- Target version changed from 2.11.22 to 2.11.23
- Target version changed from 2.11.23 to 2.11.24
- Target version changed from 2.11.24 to 308
- Target version changed from 308 to 3.1.14
- Target version changed from 3.1.14 to 3.1.15
- Target version changed from 3.1.15 to 3.1.16
- Target version changed from 3.1.16 to 3.1.17
- Target version changed from 3.1.17 to 3.1.18
- Target version changed from 3.1.18 to 3.1.19
- Status changed from New to Rejected
2.11 is not supported anymore
Also available in: Atom
PDF