Actions
Bug #13833
closed
Continuous repair on "service enabled at boot"
Pull Request:
Severity:
UX impact:
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Very Small
Priority:
0
Name check:
Fix check:
Regression:
Description
On debian 9:
R: [INFO] Executing is-enabled on ferm using the /etc/rcX.d/ method warning Ferm_firewall_with_ports| Service enabled at boot ferm Check if service ferm is started at boot could not be repaired rudder info: Executing 'no timeout' ... '/usr/sbin/update-rc.d ferm enable' rudder info: Completed execution of '/usr/sbin/update-rc.d ferm enable' R: [INFO] Executing enable on ferm using the update-rc.d method E| repaired Ferm_firewall_with_ports| Service enabled at boot ferm Ensure service ferm is started at boot was repaired
Updated by Alexis Mousset over 5 years ago
- Related to Bug #13740: Service having both an init script and a real systemd unit are managed through the init script added
Updated by Alexis Mousset about 5 years ago
- Status changed from New to Rejected
This happens because the enable action with update-rc.d does not create links in etc/rcX.d as there are no Default-Start levels in the init script.
This is definitely linked to #13740, closing this one as we can't fix anything about this specific service without addressing the root cause.
Updated by Alexis Mousset almost 2 years ago
- Project changed from 41 to Rudder
- Category changed from Generic methods - Service Management to Generic methods
Actions