Package: systemd
Version: 230-1
Severity: normal
Dear Maintainer,
I installed Nagios from source, including an init.d script, but this script
mysteriously failed to start Nagios.
When installing packages from source, it is normal to install an initscript in
/etc/init.d. These scripts no longer work in Debian >= Jessie because
/lib/lsb/init-functions.d/40-systemd intercepts their execution and tries to
make systemd start the service, but systemd-sysv-generator has not been invoked
to generate a service file for it yet, so systemd cannot be used yet.
The failure of traditional initscripts defies expectations of backwards
compatibility by invoking magic (in 40-systemd) which does not work in this
case.
Workarounds are to manually execute "systemctl daemon-reload" (which runs
systemd-sysv-generator in a special way) or reboot the system, which generates
these service files, but it's not clear from the error that either is
necessary, since it just says:
[....] Starting nagios (via systemctl): nagios.serviceFailed to start
nagios.service: Unit nagios.service failed to load: No such file or
directory.
failed!
Jessie's 40-systemd script automatically invokes "systemctl daemon-reload" but
only when run from a dpkg install. Even this backwards-compatibility measure
seems to have been removed in unstable.
Please consider invoking "systemctl -p LoadState show $service" from 40-systemd,
and if it says "not-found" then run "systemctl daemon-reload" to generate a
service file for it.
-- Package-specific info:
-- System Information:
Debian Release: 8.4
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Foreign Architectures: amd64
Kernel: Linux 4.4.0-22-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii adduser 3.113+nmu3
ii libacl1 2.2.52-2
ii libapparmor1 2.10-4
ii libaudit1 1:2.4-1+b1
ii libblkid1 2.25.2-6
ii libc6 2.19-18+deb8u4
ii libcap2 1:2.24-8
ii libcap2-bin 1:2.24-8
ii libcryptsetup4 2:1.6.6-5
ii libgcc1 1:4.9.2-10
ii libgcrypt20 1.7.0-2
ii libgpg-error0 1.17-3
ii libkmod2 18-3
ii liblzma5 5.1.1alpha+20120614-2+b3
ii libmount1 2.28-5
ii libpam0g 1.1.8-3.1+deb8u1+b1
ii libseccomp2 2.3.1-2
ii libselinux1 2.3-2
ii libsystemd0 230-1
ii mount 2.28-5
ii util-linux 2.28-5
Versions of packages systemd recommends:
pn dbus <none>
pn libpam-systemd <none>
Versions of packages systemd suggests:
pn systemd-container <none>
pn systemd-ui <none>
Versions of packages systemd is related to:
ii udev 230-1
-- no debconf information
[EXTENDED] /lib/systemd/system/rc-local.service -> /lib/systemd/system/rc-local.service.d/debian.conf
[MASKED] /etc/systemd/system/udev.service -> /lib/systemd/system/udev.service
[OVERRIDDEN] /etc/systemd/system/getty@.service -> /lib/systemd/system/getty@.service
--- /lib/systemd/system/getty@.service 2016-05-23 11:33:34.000000000 +0000
+++ /etc/systemd/system/getty@.service 2016-05-26 22:47:13.000000000 +0000
@@ -21,7 +21,7 @@
# On systems without virtual consoles, don't start any getty. Note
# that serial gettys are covered by serial-getty@.service, not this
# unit.
-ConditionPathExists=/dev/tty0
+# ConditionPathExists=/dev/tty0
[Service]
# the VT is cleared by TTYVTDisallocate
[EXTENDED] /lib/systemd/system/systemd-timesyncd.service -> /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
[REDIRECTED] /etc/systemd/system/default.target -> /lib/systemd/system/default.target
[OVERRIDDEN] /etc/systemd/system/getty-static.service -> /lib/systemd/system/getty-static.service
--- /lib/systemd/system/getty-static.service 2016-05-23 07:42:55.000000000 +0000
+++ /etc/systemd/system/getty-static.service 2016-05-26 22:47:13.000000000 +0000
@@ -1,10 +1,10 @@
[Unit]
-Description=getty on tty2-tty6 if dbus and logind are not available
+Description=getty on tty2-tty4 if dbus and logind are not available
ConditionPathExists=/dev/tty2
ConditionPathExists=!/lib/systemd/system/dbus.service
[Service]
Type=oneshot
-ExecStart=/bin/systemctl --no-block start getty@tty2.service getty@tty3.service getty@tty4.service getty@tty5.service getty@tty6.service
+ExecStart=/bin/systemctl --no-block start getty@tty2.service getty@tty3.service getty@tty4.service
RemainAfterExit=true
[MASKED] /etc/systemd/system/systemd-udevd.service -> /lib/systemd/system/systemd-udevd.service
[REDIRECTED] /etc/systemd/system/sigpwr.target -> /lib/systemd/system/sigpwr.target
[OVERRIDDEN] /etc/udev/rules.d/80-net-setup-link.rules -> /lib/udev/rules.d/80-net-setup-link.rules
--- /lib/udev/rules.d/80-net-setup-link.rules 2016-05-23 11:33:34.000000000 +0000
+++ /etc/udev/rules.d/80-net-setup-link.rules 2016-05-31 09:45:19.677070523 +0000
@@ -1,13 +1,6 @@
-# do not edit this file, it will be overwritten on update
-
-SUBSYSTEM!="net", GOTO="net_setup_link_end"
-
-IMPORT{builtin}="path_id"
-
-ACTION!="add", GOTO="net_setup_link_end"
-
-IMPORT{builtin}="net_setup_link"
-
-NAME=="", ENV{ID_NET_NAME}!="", NAME="$env{ID_NET_NAME}"
-
-LABEL="net_setup_link_end"
+# This machine is most likely a virtualized guest, where the old persistent
+# network interface mechanism (75-persistent-net-generator.rules) did not work.
+# This file disables /lib/udev/rules.d/80-net-setup-link.rules to avoid
+# changing network interface names on upgrade. Please read
+# /usr/share/doc/udev/README.Debian.gz about how to migrate to the currently
+# supported mechanism.
9 overridden configuration files found.
Failed to create bus connection: No such file or directory
==> /var/lib/systemd/deb-systemd-helper-enabled/networking.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/networking.service
/etc/systemd/system/network-online.target.wants/networking.service
==>
/var/lib/systemd/deb-systemd-helper-enabled/network-online.target.wants/networking.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/open-vm-tools.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/networking.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/cron.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/ssh.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/rsyslog.service
<==
==> /var/lib/systemd/deb-systemd-helper-enabled/open-vm-tools.service.dsh-also
<==
/etc/systemd/system/multi-user.target.wants/open-vm-tools.service
==> /var/lib/systemd/deb-systemd-helper-enabled/cron.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/cron.service
==> /var/lib/systemd/deb-systemd-helper-enabled/ssh.socket.dsh-also <==
/etc/systemd/system/sockets.target.wants/ssh.socket
==> /var/lib/systemd/deb-systemd-helper-enabled/ssh.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/ssh.service
/etc/systemd/system/sshd.service
==> /var/lib/systemd/deb-systemd-helper-enabled/sshd.service <==
==> /var/lib/systemd/deb-systemd-helper-enabled/rsyslog.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/rsyslog.service
/etc/systemd/system/syslog.service
==> /var/lib/systemd/deb-systemd-helper-enabled/syslog.service <==
# UNCONFIGURED FSTAB FOR BASE SYSTEM
_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
