Bug #13774
closed
rudder-cf-execd and rudder-cf-serverd are not enabled nor running after a server install on debian 8
Added by Félix DALLIDET about 6 years ago.
Updated about 6 years ago.
Description
I tried to install a 4.3 nightly on debian8, update the agent was not possible since rudder-cf-execd and rudder-cf-serverd were not running.
Most likely a problem in the postinstall, which should execute "/bin/systemctl enable rudder-agent rudder-cf-execd rudder-cf-serverd" but does not.
I did not try on any other version with a debian8.
- Status changed from New to In progress
- Assignee set to Alexis Mousset
- Status changed from In progress to New
- Assignee deleted (
Alexis Mousset)
This come from a wrong detection of systemd during the postinstall.
We detect it with:
if grep -q systemd /proc/1/cmdline > /dev/null ; then CFRUDDER_USE_SYSTEMD=1; fi
But if I check what is in this "folder":
root@server:/var/cache/apt/archives/tmp/DEBIAN# cat /proc/1/cmdline
/sbin/init
root@server:/var/cache/apt/archives/tmp/DEBIAN# ls -l /sbin/init
lrwxrwxrwx 1 root root 20 Apr 8 2017 /sbin/init -> /lib/systemd/systemd
There is a path to a symlink so it does not appear in the grep. We should traverse the path before doing anything.
- Assignee set to Alexis Mousset
- Status changed from New to Pending technical review
- Assignee changed from Alexis Mousset to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-packages/pull/1707
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.3.6 and 5.0.2 which were released today.
Changelog
Changelog
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by