Bug#788303: (no subject)
I'm also having this problem. I have this problem in jessie VM running on jessie host (KVM). Somehow, swap filesystem cannot be unmounted and there is no timeout. BR, -Risto Subject: Re: systemd: Hangs indefinitely on 90% of reboot attempts Followup-For: Bug #788303 Package: systemd Version: 215-17+deb8u1 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 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 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 libkmod218-3 ii liblzma55.1.1alpha+20120614-2+b3 ii libpam0g1.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 udev215-17+deb8u1 ii util-linux 2.25.2-6 Versions of packages systemd recommends: ii dbus1.8.18-0+deb8u1 ii libpam-systemd 215-17+deb8u1 Versions of packages systemd suggests: pn systemd-ui none -- Configuration Files: /etc/systemd/logind.conf changed: [Login] HandleSuspendKey=ignore HandleHibernateKey=ignore HandleLidSwitch=ignore -- no debconf information ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed (with 1 errors): Re: Bug#794625: /sbin/hwclock: hwclock: not saves time to hardware clock during halt/reboot
Processing control commands: reassign -1 systemd Bug #794625 [util-linux] /sbin/hwclock: hwclock: not saves time to hardware clock during halt/reboot Bug reassigned from package 'util-linux' to 'systemd'. No longer marked as found in versions util-linux/2.25.2-6. Ignoring request to alter fixed versions of bug #794625 to the same values previously set forcemerge 755722 -1 Failed to forcibly merge 755722: Not altering archived bugs; see unarchive. -- 794625: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794625 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#795269: TMPTIME not honored anymore
Package: systemd Version: 215-17+deb8u1 /etc/default/rcS contains a line # delete files in /tmp during boot older than x days. # '0' means always, -1 or 'infinite' disables the feature #TMPTIME=0 TMPTIME=10 This setting is completely ignored by systemd during system boot. I would consider this a bug and breaks functionality during an upgrade. Hint for the interested reader: Copy /usr/lib/tmpfiles.d/tmp.conf into /etc/tmpfiles.d and modify it as you like. This should override the system file. Regards Joey -- A mathematician is a machine for converting coffee into theorems. Paul Erdös ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: unarchive before forcemerge
Processing commands for cont...@bugs.debian.org:
unarchive 755722
Bug #755722 {Done: Martin Pitt mp...@debian.org} [systemd] systemd must sync
systemclock to RTC on shutdown
Unarchived Bug 755722
forcemerge 755722 794625
Bug #755722 {Done: Martin Pitt mp...@debian.org} [systemd] systemd must sync
systemclock to RTC on shutdown
Bug #794625 [systemd] /sbin/hwclock: hwclock: not saves time to hardware clock
during halt/reboot
Marked Bug as done
Marked as fixed in versions systemd/219-1 and systemd/215-13.
Marked as found in versions systemd/215-11.
Added tag(s) sid and jessie.
Bug #755722 {Done: Martin Pitt mp...@debian.org} [systemd] systemd must sync
systemclock to RTC on shutdown
Added tag(s) moreinfo.
Merged 755722 794625
archive 755722
Bug #755722 {Done: Martin Pitt mp...@debian.org} [systemd] systemd must sync
systemclock to RTC on shutdown
Bug #794625 {Done: Martin Pitt mp...@debian.org} [systemd] /sbin/hwclock:
hwclock: not saves time to hardware clock during halt/reboot
archived 755722 to archive/22 (from 755722)
archived 794625 to archive/25 (from 755722)
thanks
Stopping processing here.
Please contact me if you need assistance.
--
755722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755722
794625: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794625
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#794210: marked as done (systemd reboots spontaneously and with no trace on uninstalling ipmi)
Your message dated Wed, 12 Aug 2015 15:13:15 +0200 with message-id 20150812131315.gi3...@piware.de and subject line Re: Bug#794210: systemd reboots spontaneously and with no trace on uninstalling ipmi has caused the Debian Bug report #794210, regarding systemd reboots spontaneously and with no trace on uninstalling ipmi to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 794210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- 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@cartago:~# systemd --version systemd 215 +PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR root@cartago:~# systemd-analyze Startup finished in 15.456s (kernel) + 6min 2.630s (userspace) = 6min 18.086s root@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@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@1028.service 29ms systemd-update-utmp.service 28ms user@500.service 27ms user@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@cartago:~# just list ipmi ii freeipmi-bmc-watchdog 1.4.5-3 amd64GNU implementation of the IPMI protocol - BMC watchdog ii freeipmi-common1.4.5-3 all GNU implementation of the IPMI protocol - common files ii freeipmi-ipmidetect1.4.5-3 amd64GNU IPMI - IPMI node detection tool ii freeipmi-tools 1.4.5-3 amd64GNU implementation of the IPMI protocol - tools ii ipmitool 1.8.14-4 amd64utility for IPMI control with kernel driver or LAN interface ii ipmiutil 2.7.6 amd64IPMIUTIL performs a series of common IPMI server management ii libfreeipmi16 1.4.5-3 amd64GNU IPMI - libraries ii libipmiconsole2
Bug#795269: TMPTIME not honored anymore
On Wed, 12 Aug 2015 15:00:22 +0200 Joey Schulze j...@infodrom.org wrote:
Package: systemd
Version: 215-17+deb8u1
/etc/default/rcS contains a line
# delete files in /tmp during boot older than x days.
# '0' means always, -1 or 'infinite' disables the feature
#TMPTIME=0
TMPTIME=10
This setting is completely ignored by systemd during system boot.
I would consider this a bug and breaks functionality during an upgrade.
systemd's postinst does a one-time migration from TMPTIME in
/etc/default/rcS to /etc/tmpfiles.d/tmp.conf , if the former has tmp
wiping disabled. That migration, however, doesn't handle the case of
TMPTIME set to a non-zero, non-infinite value. It should be possible to
do so, by copying /usr/lib/tmpfiles.d/tmp.conf to
/etc/tmpfiles.d/tmp.conf by way of a sed that changes the '-' on the D
line to ${TMPTIME}d, assuming TMPTIME is numeric. The following patch
to systemd.postinst *should* work (not tested).
--- /var/lib/dpkg/info/systemd.postinst 2015-08-01 05:20:45.0 -0700
+++ /tmp/systemd.postinst 2015-08-12 10:33:21.108381657 -0700
@@ -72,6 +72,15 @@
# /etc/default/rcS where TMPTIME was set to infinite.
EOF
;;
+0)
+;;
+[0-9]*)
+{
+echo # Automatically generated to migrate
TMPTIME=${TMPTIME} from /etc/default/rcS
+echo
+sed -e /^D /s/-\$/${TMPTIME%%[^0-9]*}d/
/usr/lib/tmpfiles.d/tmp.conf
+} /etc/tmpfiles.d/tmp.conf
+;;
esac
fi
fi
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
How to have dh_installinit create the systemd-tmpfiles snippet for systemd-only packages?
Hi! I would like to have the following debhelper auto generated snippet in the maintainer script. # Automatically added by dh_installinit # In case this system is running systemd, we need to ensure that all # necessary tmpfiles (if any) are created before starting. if [ -d /run/systemd/system ] ; then systemd-tmpfiles --create /usr/lib/tmpfiles.d/sdwdate.conf /dev/null || true fi # End automatically added section Attempt (1): Let's suppose that upstream's make install ships installs usr/lib/tmpfiles.d/sdwdate.conf to /usr/lib/tmpfiles.d/sdwdate.conf. That is rightly processed by dh_auto_install and rightly landing in /usr/lib/tmpfiles.d/sdwdate.conf by the installed package. debhelper / dh_installinit does not notice that. Adds no snippet to the maintainer script. Is this a missing feature or am I using it wrong? Attempt (2): A file debian/sdwdate.tmpfile however would be picked up by dh_installinit and rightly land in /usr/lib/tmpfiles.d/sdwdate.conf. However, also no snippet will be added to the maintainer script. Is this a missing feature or am I using it wrong? Attempt (3): So I tried adding to debian/rules: override_dh_installinit: dh_installinit --onlyscripts Better. The wanted snippet has been added. But another unwanted snippet has also been added. # Automatically added by dh_installinit if [ -x /etc/init.d/sdwdate ]; then update-rc.d sdwdate defaults /dev/null invoke-rc.d sdwdate start || exit $? fi # End automatically added section This leads to lintian warnings. (init.d-script-not-included-in-package; init.d-script-not-marked-as-conffile) It seems like dh_installinit doesn't play nice with 'systemd-only packages' + 'create systemd-tmpfiles' snippet? (We really would like to avoid maintaining sysvinit scripts, because we don't use them.) Are these known issues or am I just using it wrong? Cheers, Patrick https://github.com/troubadoour/sdwdate/tree/python ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
