Bug#761951: systemd: Did not start network in default
Simon McVittie
smcv at debian.org
Sun Nov 23 00:29:49 GMT 2014
On Mon, 22 Sep 2014 at 15:30:00 +0900, K.Ohta wrote:
> 007_dump_network.txt.lz : systemd-analyze dump (lzipped).
I tried using my script from
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763315 to find the
dependency cycles, but its answers make no sense, because neither do
the dependencies in the "systemd-analyze dump" output.
For instance, a dependency relationship between mdadm.service and
nmbd.service doesn't seem to me as though it makes any logical sense.
For another example, here are the dependencies of clamav-freshclam.service
when I do "systemd-analyze dump" on my laptop:
-> Unit clamav-freshclam.service:
Requires: basic.target
Wants: system.slice
WantedBy: multi-user.target
Conflicts: shutdown.target
Before: shutdown.target
Before: multi-user.target
After: systemd-journald.socket
After: basic.target
After: system.slice
References: systemd-journald.socket
References: basic.target
References: shutdown.target
References: system.slice
ReferencedBy: multi-user.target
Fine, that all looks reasonable. But here's what it says on the
bug submitter's system:
-> Unit clamav-freshclam.service:
Before: smbd.service
Before: sysfsutils.service
Before: saned.service
Before: reniced.service
Before: kdm.service
Before: fetchmail.service
Before: boinc-client.service
Before: graphical.target
Before: shutdown.target
Before: multi-user.target
After: popa3d.service
After: partimaged.service
After: iptotal.service
After: mythtv-backend.service
After: ifetch-tools.service
After: mcelog.service
After: mailavenger.service
After: nscd.service
After: mono-xsp4.service
After: mbmon.service
After: hylafax.service
After: udftools.service
After: nmbd.service
After: loadcpufreq.service
After: timidity.service
After: stone.service
After: inetutils-inetd.service
After: kdump-tools.service
After: php5-fpm.service
After: mdadm.service
After: ntp.service
After: apport.service
After: htpdate.service
After: glances.service
After: cpufreqd.service
After: hddtemp.service
After: openbsd-inetd.service
After: clamsmtp.service
After: ntop.service
After: mysql.service
After: apache2.service
After: nvidia-kernel.service
After: samba-ad-dc.service
After: sensord.service
After: aumix.service
After: clamav-daemon.service
After: proxsmtp.service
After: solid-pop3d.service
After: deluged.service
After: smartmontools.service
After: stunnel4.service
After: jove.service
After: remote-fs.target
After: systemd-journald-dev-log.socket
After: vboxdrv.service
After: qemu-guest-agent.service
After: schroot.service
After: speech-dispatcher.service
After: polipo.service
After: restartd.service
After: fglrx-atieventsd.service
After: winbind.service
After: systemd-journald.socket
After: basic.target
After: system.slice
References: graphical.target
References: shutdown.target
References: remote-fs.target
References: systemd-journald-dev-log.socket
References: clamav-daemon.service
References: vboxdrv.service
References: qemu-guest-agent.service
References: schroot.service
References: speech-dispatcher.service
References: polipo.service
References: restartd.service
References: fglrx-atieventsd.service
References: winbind.service
References: systemd-journald.socket
References: basic.target
References: system.slice
References: multi-user.target
ReferencedBy: graphical.target
ReferencedBy: popa3d.service
ReferencedBy: partimaged.service
ReferencedBy: iptotal.service
ReferencedBy: mythtv-backend.service
ReferencedBy: ifetch-tools.service
ReferencedBy: mcelog.service
ReferencedBy: smbd.service
ReferencedBy: mailavenger.service
ReferencedBy: sysfsutils.service
ReferencedBy: nscd.service
ReferencedBy: mono-xsp4.service
ReferencedBy: mbmon.service
ReferencedBy: hylafax.service
ReferencedBy: udftools.service
ReferencedBy: nmbd.service
ReferencedBy: loadcpufreq.service
ReferencedBy: saned.service
ReferencedBy: timidity.service
ReferencedBy: stone.service
ReferencedBy: inetutils-inetd.service
ReferencedBy: kdump-tools.service
ReferencedBy: php5-fpm.service
ReferencedBy: mdadm.service
ReferencedBy: ntp.service
ReferencedBy: apport.service
ReferencedBy: htpdate.service
ReferencedBy: glances.service
ReferencedBy: cpufreqd.service
ReferencedBy: hddtemp.service
ReferencedBy: openbsd-inetd.service
ReferencedBy: clamsmtp.service
ReferencedBy: ntop.service
ReferencedBy: mysql.service
ReferencedBy: apache2.service
ReferencedBy: nvidia-kernel.service
ReferencedBy: samba-ad-dc.service
ReferencedBy: reniced.service
ReferencedBy: sensord.service
ReferencedBy: aumix.service
ReferencedBy: clamav-daemon.service
ReferencedBy: proxsmtp.service
ReferencedBy: kdm.service
ReferencedBy: fetchmail.service
ReferencedBy: solid-pop3d.service
ReferencedBy: deluged.service
ReferencedBy: smartmontools.service
ReferencedBy: boinc-client.service
ReferencedBy: stunnel4.service
ReferencedBy: jove.service
ReferencedBy: multi-user.target
... what?
I hope someone who knows systemd better can figure this out...
Other things from the journalctl log:
> Sep 22 15:15:12 melchior systemd[1]: /usr appears to be
> on its own filesytem and is not already mounted. This
> is not a supported setup. Some things will probably
> break (sometimes even silently) in mysterious ways. Consult
> http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken for
> more information.
That's not going to help. initramfs-tools 0.117 fixes this by mounting
/usr in the initramfs, but is not migrating to testing because it
has new RC bugs.
> Sep 22 15:15:18 melchior systemd-fsck[1765]: CP437: Invalid argument
I asssume that's not ideal either.
Regards,
S
More information about the Pkg-systemd-maintainers
mailing list