Bug#794210: systemd reboots spontaneously and with no trace on uninstalling ipmi
David Liontooth
lionteeth at cogweb.net
Fri Jul 31 10:23:14 BST 2015
Package: systemd
Version: 215-17+deb8u1
Severity: normal
On first installing systemd, I see that ipmi is taking five minutes out of a six-minute boot process:
root at cartago:~# systemd --version
systemd 215
+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR
root at cartago:~# systemd-analyze
Startup finished in 15.456s (kernel) + 6min 2.630s (userspace) = 6min 18.086s
root at cartago:~# systemd-analyze blame
5min 83ms ipmiutil_evt.service
11.210s mysql.service
8.139s denyhosts.service
8.023s rssdler.service
7.405s ipmiutil_wdt.service
7.067s munin-node.service
4.103s ModemManager.service
3.297s kerneloops.service
2.829s binfmt-support.service
2.589s sensord.service
2.177s systemd-fsck at dev-disk-by\x2duuid-b2954996\x2d1c3b\x2d4873\x2d955e\x2db6461e0c48a8.service
1.904s ipmidetectd.service
1.904s bmc-watchdog.service
1.904s openbsd-inetd.service
1.903s ipmiutil_asy.service
1.902s gpm.service
1.902s irqbalance.service
1.901s ipmi_port.service
1.879s lm-sensors.service
1.800s rsyslog.service
1.633s avahi-daemon.service
1.571s systemd-logind.service
1.559s rc-local.service
1.496s nfs-kernel-server.service
1.433s networking.service
1.248s keyboard-setup.service
1.153s mdadm-raid.service
1.108s systemd-tmpfiles-setup.service
1.022s systemd-modules-load.service
635ms nfs-common.service
572ms hdparm.service
540ms systemd-tmpfiles-clean.service
506ms exim4.service
490ms saned.service
391ms console-screen.service
334ms systemd-tmpfiles-setup-dev.service
237ms systemd-udev-trigger.service
236ms rpcbind.service
228ms console-setup.service
221ms systemd-setup-dgram-qlen.service
220ms sys-kernel-debug.mount
219ms dev-mqueue.mount
179ms systemd-sysctl.service
160ms systemd-remount-fs.service
159ms systemd-user-sessions.service
133ms proc-sys-fs-binfmt_misc.mount
99ms dev-disk-by\x2duuid-a9f9050b\x2da1f3\x2d4132\x2da29a\x2daf3b2277cc80.swap
51ms boot.mount
49ms systemd-random-seed.service
45ms udev-finish.service
30ms user at 1028.service
29ms systemd-update-utmp.service
28ms user at 500.service
27ms user at 501.service
21ms portmap.service
16ms kmod-static-nodes.service
15ms systemd-udevd.service
4ms systemd-journal-flush.service
3ms systemd-update-utmp-runlevel.service
1ms sys-fs-fuse-connections.mount
1ms dev-hugepages.mount
Since ipmi is not in fact working on this machine, I checked which were uninstalled:
root at cartago:~# just list ipmi
ii freeipmi-bmc-watchdog 1.4.5-3 amd64 GNU implementation of the IPMI protocol - BMC watchdog
ii freeipmi-common 1.4.5-3 all GNU implementation of the IPMI protocol - common files
ii freeipmi-ipmidetect 1.4.5-3 amd64 GNU IPMI - IPMI node detection tool
ii freeipmi-tools 1.4.5-3 amd64 GNU implementation of the IPMI protocol - tools
ii ipmitool 1.8.14-4 amd64 utility for IPMI control with kernel driver or LAN interface
ii ipmiutil 2.7.6 amd64 IPMIUTIL performs a series of common IPMI server management
ii libfreeipmi16 1.4.5-3 amd64 GNU IPMI - libraries
ii libipmiconsole2 1.4.5-3 amd64 GNU IPMI - Serial-over-Lan library
ii libipmidetect0 1.4.5-3 amd64 GNU IPMI - IPMI node detection library
ii libopenipmi0 2.0.16-1.4 amd64 Intelligent Platform Management Interface - runtime
ii openipmi 2.0.16-1.4 amd64 Intelligent Platform Management Interface (for servers)
rc libfreeipmi12 1.1.5-3 amd64 GNU IPMI - libraries
rc libipmimonitoring4 0.8.12-3 amd64 GNU IPMI - Sensor monitoring library
and then removed them all, purging the configuration files. The removal completed with no complaints.
At that moment, however, the machine just rebooted. /var/log/messages around the reboot show only this:
Jul 30 22:37:17 cartago ipmiutil: igetevent waiting for events ...
Jul 30 23:28:22 cartago uptimed: moving up to position 18: 0 days, 06:30:26
Jul 31 01:33:05 cartago rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="2299" x-info="http://www.rsyslog.com"] start
Jul 31 01:33:05 cartago kernel: [ 0.577333] pci 0000:00:1a.0: System wakeup disabled by ACPI
No trace of an error. On the positive side, the reboot was much faster, with no problems (below).
Instant reboot without a trace should perhaps be classified as a more serious error than normal.
Cheers,
David
root at cartago:~# systemd-analyze
Startup finished in 31.974s (kernel) + 1min 31.370s (userspace) = 2min 3.345s
root at cartago:~# systemd-analyze blame
12.171s denyhosts.service
11.856s mysql.service
8.076s rssdler.service
5.525s munin-node.service
4.194s ModemManager.service
2.989s mnt-ifs.mount
2.640s kerneloops.service
2.631s sensord.service
2.124s networking.service
2.037s binfmt-support.service
1.872s openbsd-inetd.service
1.871s irqbalance.service
1.871s gpm.service
1.786s lm-sensors.service
1.715s rsyslog.service
1.655s keyboard-setup.service
1.618s avahi-daemon.service
1.496s mdadm-raid.service
1.473s systemd-logind.service
1.458s rc-local.service
1.329s systemd-tmpfiles-setup.service
1.205s user at 500.service
843ms systemd-fsck at dev-disk-by\x2duuid-b2954996\x2d1c3b\x2d4873\x2d955e\x2db6461e0c48a8.service
822ms systemd-modules-load.service
774ms nfs-kernel-server.service
607ms nfs-common.service
548ms systemd-random-seed.service
440ms console-screen.service
353ms hdparm.service
337ms systemd-tmpfiles-setup-dev.service
279ms rpcbind.service
226ms proc-sys-fs-binfmt_misc.mount
223ms systemd-udev-trigger.service
207ms systemd-setup-dgram-qlen.service
206ms sys-kernel-debug.mount
205ms dev-mqueue.mount
185ms console-setup.service
166ms systemd-remount-fs.service
162ms systemd-sysctl.service
151ms systemd-tmpfiles-clean.service
87ms boot.mount
71ms dev-disk-by\x2duuid-a9f9050b\x2da1f3\x2d4132\x2da29a\x2daf3b2277cc80.swap
63ms kmod-static-nodes.service
51ms systemd-update-utmp.service
40ms saned.service
40ms systemd-user-sessions.service
39ms udev-finish.service
28ms user at 501.service
27ms user at 1028.service
8ms portmap.service
7ms systemd-udevd.service
4ms systemd-journal-flush.service
3ms dev-hugepages.mount
2ms systemd-update-utmp-runlevel.service
1ms sys-fs-fuse-connections.mount
-- Package-specific info:
-- System Information:
Debian Release: 8.1
APT prefers stable
APT policy: (990, 'stable'), (500, 'testing'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.0.0-2-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii acl 2.2.52-2
ii adduser 3.113+nmu3
ii initscripts 2.88dsf-59
ii libacl1 2.2.52-2
ii libaudit1 1:2.4-1+b1
ii libblkid1 2.25.2-6
ii libc6 2.19-18
ii libcap2 1:2.24-8
ii libcap2-bin 1:2.24-8
ii libcryptsetup4 2:1.6.6-5
ii libgcrypt20 1.6.3-2
ii libkmod2 18-3
ii liblzma5 5.1.1alpha+20120614-2+b3
ii libpam0g 1.1.8-3.1
ii libselinux1 2.3-2
ii libsystemd0 215-17+deb8u1
ii mount 2.25.2-6
ii sysv-rc 2.88dsf-59
ii udev 215-17+deb8u1
ii util-linux 2.25.2-6
Versions of packages systemd recommends:
ii dbus 1.8.18-0+deb8u1
ii libpam-systemd 215-17+deb8u1
Versions of packages systemd suggests:
pn systemd-ui <none>
-- no debconf information
More information about the Pkg-systemd-maintainers
mailing list