Hello, 2015-02-12 13:48 GMT+01:00 Thomas Pierson <cont...@thomaspierson.fr>: > Hello Thibault, > >> Could you try to reinstall on a fresh Debian Jessie and try this with >> root user (without restart): >> # mkdir -p /usr/share/pyshared/shinken/modules >> # service shinken start > > > I got the same errors on a new fresh Debian Jessie using your steps: > ---- > root@jessie:/home/vagrant# apt-get install shinken > […] > root@jessie:/home/vagrant# mkdir -p /usr/share/pyshared/shinken/modules > root@jessie:/home/vagrant# service shinken start > Failed to start shinken.service: Unit shinken.service failed to load: No > such file or directory. > root@jessie:/home/vagrant# > ---- > > After a reboot, the `service shinken` command seems to work but I get back > the same strange behavior than before with individual and grouped services > started.
I think there are two problems here: - We need to call "systemctl daemon-reload" on shinken-common.postinst => This is needed for systemd to know about the new init file - We probably need to mask the shinken service, as this is a bad-designed initscript which start all daemons from the same cgroup. See #740942 for a similar problem Regards -- Mathieu Parent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
