Your message dated Thu, 19 Jul 2018 07:04:23 +0000 with message-id <[email protected]> and subject line Bug#903224: fixed in systemd 239-6 has caused the Debian Bug report #903224, regarding udev: Fails to upgrade 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 [email protected] immediately.) -- 903224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903224 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: udev Version: 239-5 Severity: serious Hi, When upgrading udev, it failed to upgrade, because udev didn't want to start. I think there might be some ordering problem. This is the apt history log: Start-Date: 2018-07-07 23:51:34 Commandline: apt-get upgrade Upgrade: libsystemd0:amd64 (238-5, 239-5), udev:amd64 (238-5, 239-5), libudev1:amd64 (238-5, 239-5), systemd-sysv:amd64 (238-5, 239-5), debootstrap:amd64 (1.0.105, 1.0.106), libpam-systemd:amd64 (238-5, 239-5), systemd:amd64 (238-5, 239-5) Error: Sub-process /usr/bin/dpkg returned an error code (1) End-Date: 2018-07-07 23:53:25 Start-Date: 2018-07-07 23:53:32 Commandline: apt-get -f install End-Date: 2018-07-07 23:53:58 The term.log: Log started: 2018-07-07 23:51:34 (Reading database ... 360672 files and directories currently installed.) Preparing to unpack .../systemd-sysv_239-5_amd64.deb ... Unpacking systemd-sysv (239-5) over (238-5) ... Preparing to unpack .../libpam-systemd_239-5_amd64.deb ... Unpacking libpam-systemd:amd64 (239-5) over (238-5) ... Preparing to unpack .../libsystemd0_239-5_amd64.deb ... Unpacking libsystemd0:amd64 (239-5) over (238-5) ... Setting up libsystemd0:amd64 (239-5) ... (Reading database ... 360672 files and directories currently installed.) Preparing to unpack .../systemd_239-5_amd64.deb ... Unpacking systemd (239-5) over (238-5) ... Preparing to unpack .../archives/udev_239-5_amd64.deb ... Unpacking udev (239-5) over (238-5) ... Preparing to unpack .../libudev1_239-5_amd64.deb ... Unpacking libudev1:amd64 (239-5) over (238-5) ... Setting up libudev1:amd64 (239-5) ... (Reading database ... 360697 files and directories currently installed.) Preparing to unpack .../debootstrap_1.0.106_all.deb ... Unpacking debootstrap (1.0.106) over (1.0.105) ... Processing triggers for libc-bin (2.27-3) ... Setting up udev (239-5) ... Job for systemd-udevd.service failed because the control process exited with error code. See "systemctl status systemd-udevd.service" and "journalctl -xe" for details. invoke-rc.d: initscript udev, action "restart" failed. • systemd-udevd.service - udev Kernel Device Manager Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2018-07-07 23:52:19 CEST; 10ms ago Docs: man:systemd-udevd.service(8) man:udev(7) Process: 21914 ExecStart=/lib/systemd/systemd-udevd (code=exited, status=127) Main PID: 21914 (code=exited, status=127) Jul 07 23:52:19 intrepid systemd[1]: Stopped udev Kernel Device Manager. Jul 07 23:52:19 intrepid systemd[1]: Starting udev Kernel Device Manager... Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Main process exited, code=exited, status=127/n/a Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Failed with result 'exit-code'. Jul 07 23:52:19 intrepid systemd[1]: Failed to start udev Kernel Device Manager. Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Service has no hold-off time, scheduling restart. Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Scheduled restart job, restart counter is at 3. Jul 07 23:52:19 intrepid systemd[1]: Stopped udev Kernel Device Manager. Jul 07 23:52:19 intrepid systemd[1]: Starting udev Kernel Device Manager... Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Main process exited, code=exited, status=127/n/a Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Failed with result 'exit-code'. Jul 07 23:52:19 intrepid systemd[1]: Failed to start udev Kernel Device Manager. Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Service has no hold-off time, scheduling restart. Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Scheduled restart job, restart counter is at 4. Jul 07 23:52:19 intrepid systemd[1]: Stopped udev Kernel Device Manager. Jul 07 23:52:19 intrepid systemd[1]: Starting udev Kernel Device Manager... Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Main process exited, code=exited, status=127/n/a Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Failed with result 'exit-code'. Jul 07 23:52:19 intrepid systemd[1]: Failed to start udev Kernel Device Manager. Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Service has no hold-off time, scheduling restart. Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Scheduled restart job, restart counter is at 5. Jul 07 23:52:19 intrepid systemd[1]: Stopped udev Kernel Device Manager. Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Start request repeated too quickly. Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Failed with result 'exit-code'. Jul 07 23:52:19 intrepid systemd[1]: Failed to start udev Kernel Device Manager. dpkg: error processing package udev (--configure): installed udev package post-installation script subprocess returned error exit status 1 Setting up systemd (239-5) ... Installing new version of config file /etc/systemd/journald.conf ... Configuration file '/etc/systemd/logind.conf' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** logind.conf (Y/I/N/O/D/Z) [default=N] ? Installing new version of config file /etc/systemd/resolved.conf ... Installing new version of config file /etc/systemd/system.conf ... Processing triggers for man-db (2.8.3-2) ... Setting up debootstrap (1.0.106) ... Processing triggers for dbus (1.12.8-3) ... Setting up systemd-sysv (239-5) ... Setting up libpam-systemd:amd64 (239-5) ... Errors were encountered while processing: udev Log ended: 2018-07-07 23:53:25 Log started: 2018-07-07 23:53:32 Setting up udev (239-5) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.130) ... update-initramfs: Generating /boot/initrd.img-4.16.0-2-amd64 I: The initramfs will attempt to resume from /dev/sdb2 I: (UUID=38d3dda0-1fc3-4398-926b-ce9b8d03c05a) I: Set the RESUME variable to override this. Log ended: 2018-07-07 23:53:58 journalctl -xe output: Jul 07 23:47:14 intrepid systemd[1]: Starting Hostname Service... -- Subject: Unit systemd-hostnamed.service has begun start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-hostnamed.service has begun starting up. Jul 07 23:47:14 intrepid systemd[1]: Started Hostname Service. -- Subject: Unit systemd-hostnamed.service has finished start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-hostnamed.service has finished starting up. -- -- The start-up result is RESULT. Jul 07 23:52:10 intrepid systemd[1]: Reloading. Jul 07 23:52:11 intrepid systemd[1]: /lib/systemd/system/systemd-networkd.service:38: Unknown system call group, ignoring: @system-service Jul 07 23:52:11 intrepid systemd[1]: /lib/systemd/system/systemd-logind.service:34: Unknown system call group, ignoring: @system-service Jul 07 23:52:11 intrepid systemd[1]: /lib/systemd/system/systemd-udevd.service:28: Unknown lvalue 'PrivateMounts' in section 'Service' Jul 07 23:52:11 intrepid systemd[1]: /lib/systemd/system/systemd-udevd.service:32: Unknown system call group, ignoring: @system-service Jul 07 23:52:12 intrepid systemd[1]: /lib/systemd/system/systemd-timesyncd.service:41: Unknown system call group, ignoring: @system-service Jul 07 23:52:12 intrepid systemd[1]: /lib/systemd/system/systemd-journald.service:32: Unknown system call group, ignoring: @system-service Jul 07 23:52:12 intrepid systemd[1]: Starting Daily apt download activities... -- Subject: Unit apt-daily.service has begun start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit apt-daily.service has begun starting up. Jul 07 23:52:12 intrepid systemd[1]: Started Daily apt download activities. -- Subject: Unit apt-daily.service has finished start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit apt-daily.service has finished starting up. -- -- The start-up result is RESULT. Jul 07 23:52:18 intrepid systemd[1]: Reloading. Jul 07 23:52:18 intrepid systemd[1]: /lib/systemd/system/systemd-networkd.service:38: Unknown system call group, ignoring: @system-service Jul 07 23:52:18 intrepid systemd[1]: /lib/systemd/system/systemd-logind.service:34: Unknown system call group, ignoring: @system-service Jul 07 23:52:18 intrepid systemd[1]: /lib/systemd/system/systemd-udevd.service:28: Unknown lvalue 'PrivateMounts' in section 'Service' Jul 07 23:52:18 intrepid systemd[1]: /lib/systemd/system/systemd-udevd.service:32: Unknown system call group, ignoring: @system-service Jul 07 23:52:18 intrepid systemd[1]: /lib/systemd/system/systemd-timesyncd.service:41: Unknown system call group, ignoring: @system-service Jul 07 23:52:18 intrepid systemd[1]: /lib/systemd/system/systemd-journald.service:32: Unknown system call group, ignoring: @system-service Jul 07 23:52:19 intrepid systemd[1]: Reloading. Jul 07 23:52:19 intrepid systemd[1]: /lib/systemd/system/systemd-networkd.service:38: Unknown system call group, ignoring: @system-service Jul 07 23:52:19 intrepid systemd[1]: /lib/systemd/system/systemd-logind.service:34: Unknown system call group, ignoring: @system-service Jul 07 23:52:19 intrepid systemd[1]: /lib/systemd/system/systemd-udevd.service:28: Unknown lvalue 'PrivateMounts' in section 'Service' Jul 07 23:52:19 intrepid systemd[1]: /lib/systemd/system/systemd-udevd.service:32: Unknown system call group, ignoring: @system-service Jul 07 23:52:19 intrepid systemd[1]: /lib/systemd/system/systemd-timesyncd.service:41: Unknown system call group, ignoring: @system-service Jul 07 23:52:19 intrepid systemd[1]: /lib/systemd/system/systemd-journald.service:32: Unknown system call group, ignoring: @system-service Jul 07 23:52:19 intrepid systemd[1]: Stopping udev Kernel Device Manager... -- Subject: Unit systemd-udevd.service has begun shutting down -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-udevd.service has begun shutting down. Jul 07 23:52:19 intrepid systemd[1]: Stopped udev Kernel Device Manager. -- Subject: Unit systemd-udevd.service has finished shutting down -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- -- Unit systemd-udevd.service has finished shutting down. Jul 07 23:52:19 intrepid systemd[1]: Starting udev Kernel Device Manager... -- Subject: Unit systemd-udevd.service has begun start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-udevd.service has begun starting up. Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Main process exited, code=exited, status=127/n/a Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Failed with result 'exit-code'. Jul 07 23:52:19 intrepid systemd[1]: Failed to start udev Kernel Device Manager. -- Subject: Unit systemd-udevd.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-udevd.service has failed. -- -- The result is RESULT. Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Service has no hold-off time, scheduling restart. Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Scheduled restart job, restart counter is at 1. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Automatic restarting of the unit systemd-udevd.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Jul 07 23:52:19 intrepid systemd[1]: Stopped udev Kernel Device Manager. -- Subject: Unit systemd-udevd.service has finished shutting down -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-udevd.service has finished shutting down. Jul 07 23:52:19 intrepid systemd[1]: Starting udev Kernel Device Manager... -- Subject: Unit systemd-udevd.service has begun start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-udevd.service has begun starting up. Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Main process exited, code=exited, status=127/n/a Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Failed with result 'exit-code'. Jul 07 23:52:19 intrepid systemd[1]: Failed to start udev Kernel Device Manager. -- Subject: Unit systemd-udevd.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-udevd.service has failed. -- -- The result is RESULT. Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Service has no hold-off time, scheduling restart. Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Scheduled restart job, restart counter is at 2. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Automatic restarting of the unit systemd-udevd.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Jul 07 23:52:19 intrepid systemd[1]: Stopped udev Kernel Device Manager. -- Subject: Unit systemd-udevd.service has finished shutting down -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-udevd.service has finished shutting down. Jul 07 23:52:19 intrepid systemd[1]: Starting udev Kernel Device Manager... -- Subject: Unit systemd-udevd.service has begun start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-udevd.service has begun starting up. Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Main process exited, code=exited, status=127/n/a Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Failed with result 'exit-code'. Jul 07 23:52:19 intrepid systemd[1]: Failed to start udev Kernel Device Manager. -- Subject: Unit systemd-udevd.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-udevd.service has failed. -- -- The result is RESULT. Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Service has no hold-off time, scheduling restart. Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Scheduled restart job, restart counter is at 3. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Automatic restarting of the unit systemd-udevd.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Jul 07 23:52:19 intrepid systemd[1]: Stopped udev Kernel Device Manager. -- Subject: Unit systemd-udevd.service has finished shutting down -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-udevd.service has finished shutting down. Jul 07 23:52:19 intrepid systemd[1]: Starting udev Kernel Device Manager... -- Subject: Unit systemd-udevd.service has begun start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-udevd.service has begun starting up. Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Main process exited, code=exited, status=127/n/a Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Failed with result 'exit-code'. Jul 07 23:52:19 intrepid systemd[1]: Failed to start udev Kernel Device Manager. -- Subject: Unit systemd-udevd.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-udevd.service has failed. -- -- The result is RESULT. Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Service has no hold-off time, scheduling restart. Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Scheduled restart job, restart counter is at 4. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Automatic restarting of the unit systemd-udevd.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Jul 07 23:52:19 intrepid systemd[1]: Stopped udev Kernel Device Manager. -- Subject: Unit systemd-udevd.service has finished shutting down -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-udevd.service has finished shutting down. Jul 07 23:52:19 intrepid systemd[1]: Starting udev Kernel Device Manager... -- Subject: Unit systemd-udevd.service has begun start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-udevd.service has begun starting up. Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Main process exited, code=exited, status=127/n/a Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Failed with result 'exit-code'. Jul 07 23:52:19 intrepid systemd[1]: Failed to start udev Kernel Device Manager. -- Subject: Unit systemd-udevd.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-udevd.service has failed. -- -- The result is RESULT. Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Service has no hold-off time, scheduling restart. Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Scheduled restart job, restart counter is at 5. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Automatic restarting of the unit systemd-udevd.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Jul 07 23:52:19 intrepid systemd[1]: Stopped udev Kernel Device Manager. -- Subject: Unit systemd-udevd.service has finished shutting down -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-udevd.service has finished shutting down. Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Start request repeated too quickly. Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Failed with result 'exit-code'. Jul 07 23:52:19 intrepid systemd[1]: Failed to start udev Kernel Device Manager. -- Subject: Unit systemd-udevd.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-udevd.service has failed. -- -- The result is RESULT. Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd-control.socket: Failed with result 'service-start-limit-hit'. Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd-kernel.socket: Failed with result 'service-start-limit-hit'. Jul 07 23:53:09 intrepid systemd[1]: Reexecuting. Jul 07 23:53:09 intrepid kernel: systemd: 63 output lines suppressed due to ratelimiting Jul 07 23:53:09 intrepid kernel[808]: [2247329.242827] systemd: 63 output lines suppressed due to ratelimiting Jul 07 23:53:09 intrepid systemd[1]: systemd 239 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierJul 07 23:53:09 intrepid systemd[1]: Detected architecture x86-64. Jul 07 23:53:09 intrepid kernel[808]: <30>[2247329.308302] systemd[1]: systemd 239 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KJul 07 23:53:09 intrepid kernel[808]: <30>[2247329.330383] systemd[1]: Detected architecture x86-64. Jul 07 23:53:09 intrepid chronyd[995]: chronyd exiting Jul 07 23:53:09 intrepid systemd[1]: Stopping chrony, an NTP client/server... -- Subject: Unit chrony.service has begun shutting down -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit chrony.service has begun shutting down. Jul 07 23:53:09 intrepid systemd[1]: Stopping Network Time Synchronization... -- Subject: Unit systemd-timesyncd.service has begun shutting down -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-timesyncd.service has begun shutting down. Jul 07 23:53:10 intrepid systemd[1]: Stopped chrony, an NTP client/server. -- Subject: Unit chrony.service has finished shutting down -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit chrony.service has finished shutting down. Jul 07 23:53:11 intrepid systemd[1]: Stopped Network Time Synchronization. -- Subject: Unit systemd-timesyncd.service has finished shutting down -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-timesyncd.service has finished shutting down. Jul 07 23:53:11 intrepid systemd[1]: Starting Network Time Synchronization... -- Subject: Unit systemd-timesyncd.service has begun start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-timesyncd.service has begun starting up. Jul 07 23:53:11 intrepid slapd[1316]: <= bdb_equality_candidates: (uidNumber) not indexed Jul 07 23:53:11 intrepid slapd[1316]: <= bdb_equality_candidates: (uidNumber) not indexed Jul 07 23:53:11 intrepid systemd[1]: Stopping Journal Service... Jul 07 23:53:11 intrepid systemd[1]: Started Network Time Synchronization. -- Subject: Unit systemd-timesyncd.service has finished start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-timesyncd.service has finished starting up. -- -- The start-up result is RESULT. Jul 07 23:53:11 intrepid kernel[808]: <30>[2247331.346957] systemd[1]: Stopping Journal Service... Jul 07 23:53:11 intrepid systemd[1]: Stopped Flush Journal to Persistent Storage. -- Subject: Unit systemd-journal-flush.service has finished shutting down -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-journal-flush.service has finished shutting down. Jul 07 23:53:11 intrepid systemd[1]: Stopping Flush Journal to Persistent Storage... -- Subject: Unit systemd-journal-flush.service has begun shutting down -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-journal-flush.service has begun shutting down. Jul 07 23:53:11 intrepid systemd-journald[357]: Journal stopped -- Subject: The journal has been stopped -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The system journal process has shut down and closed all currently -- active journal files. Jul 07 23:53:11 intrepid systemd-journald[357]: Received SIGTERM from PID 1 (systemd). Jul 07 23:53:11 intrepid systemd[1]: Stopped Journal Service. Jul 07 23:53:11 intrepid systemd[1]: Starting Journal Service... Jul 07 23:53:11 intrepid systemd-journald[22011]: Journal started -- Subject: The journal has been started -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The system journal process has started up, opened the journal -- files for writing and is now ready to process requests. Jul 07 23:53:11 intrepid systemd-journald[22011]: Runtime journal (/run/log/journal/550bcb02bb9723df1ae4fd004617e089) is 72.0M, max 78.8M, 6.8M free. -- Subject: Disk space used by the journal -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Runtime journal (/run/log/journal/550bcb02bb9723df1ae4fd004617e089) is currently using 72.0M. -- Maximum allowed usage is set to 78.8M. -- Leaving at least 118.3M free (of currently available 715.4M of disk space). -- Enforced usage limit is thus 78.8M, of which 6.8M are still available. -- -- The limits controlling how much disk space is used by the journal may -- be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=, -- RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in -- /etc/systemd/journald.conf. See journald.conf(5) for details. Jul 07 23:53:11 intrepid kernel[808]: <46>[2247331.381668] systemd-journald[357]: Received SIGTERM from PID 1 (systemd). Jul 07 23:53:11 intrepid kernel[808]: <30>[2247331.563731] systemd[1]: Stopped Journal Service. Jul 07 23:53:11 intrepid kernel[808]: <30>[2247331.566955] systemd[1]: Starting Journal Service... Jul 07 23:53:11 intrepid systemd[1]: Started Journal Service. Jul 07 23:53:11 intrepid kernel[808]: <30>[2247331.744761] systemd[1]: Started Journal Service. Jul 07 23:53:11 intrepid systemd[1]: Starting Flush Journal to Persistent Storage... -- Subject: Unit systemd-journal-flush.service has begun start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-journal-flush.service has begun starting up. Jul 07 23:53:11 intrepid systemd[1]: Started Flush Journal to Persistent Storage. -- Subject: Unit systemd-journal-flush.service has finished start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-journal-flush.service has finished starting up. -- -- The start-up result is RESULT. Jul 07 23:53:12 intrepid systemd-timesyncd[22007]: Synchronized to time server 91.121.216.238:123 (0.debian.pool.ntp.org). Jul 07 23:53:32 intrepid systemd[1]: Reloading. Jul 07 23:53:33 intrepid systemd[1]: Reloading. Jul 07 23:53:33 intrepid systemd[1]: Listening on udev Kernel Socket. -- Subject: Unit systemd-udevd-kernel.socket has finished start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-udevd-kernel.socket has finished starting up. -- -- The start-up result is RESULT. Jul 07 23:53:33 intrepid systemd[1]: Listening on udev Control Socket. -- Subject: Unit systemd-udevd-control.socket has finished start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-udevd-control.socket has finished starting up. -- -- The start-up result is RESULT. Jul 07 23:53:33 intrepid systemd[1]: Starting udev Kernel Device Manager... -- Subject: Unit systemd-udevd.service has begun start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-udevd.service has begun starting up. Jul 07 23:53:34 intrepid systemd[1]: Started udev Kernel Device Manager. -- Subject: Unit systemd-udevd.service has finished start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit systemd-udevd.service has finished starting up. -- -- The start-up result is RESULT. Jul 07 23:53:36 intrepid systemd[1]: Reloading.
--- End Message ---
--- Begin Message ---Source: systemd Source-Version: 239-6 We believe that the bug you reported is fixed in the latest version of systemd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl <[email protected]> (supplier of updated systemd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Thu, 19 Jul 2018 00:04:54 +0200 Source: systemd Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump systemd-tests libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb Architecture: source Version: 239-6 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers <[email protected]> Changed-By: Michael Biebl <[email protected]> Description: libnss-myhostname - nss module providing fallback resolution for the current hostname libnss-mymachines - nss module to resolve hostnames for local container instances libnss-resolve - nss module to resolve names via systemd-resolved libnss-systemd - nss module providing dynamic user and group name resolution libpam-systemd - system and service manager - PAM module libsystemd-dev - systemd utility library - development files libsystemd0 - systemd utility library libudev-dev - libudev development files libudev1 - libudev shared library libudev1-udeb - libudev shared library (udeb) systemd - system and service manager systemd-container - systemd container/nspawn tools systemd-coredump - tools for storing and retrieving coredumps systemd-journal-remote - tools for sending and receiving remote journal logs systemd-sysv - system and service manager - SysV links systemd-tests - tests for systemd udev - /dev/ and hotplug management daemon udev-udeb - /dev/ and hotplug management daemon (udeb) Closes: 887852 902971 903224 903557 Changes: systemd (239-6) unstable; urgency=medium . [ Martin Pitt ] * autopkgtest: Install libnss-systemd. Make sure that dynamic users can be resolved. This e. g. prevents a startup failure for systemd-resolved. * autopkgtest: Add missing python3 test dependency for udev test . [ Michael Biebl ] * autopkgtest: Make AppArmor violator test work with merged-usr * Make /dev/kvm accessible to local users and group kvm. Re-add the uaccess tag to /dev/kvm to make it accessible to local users. Access is also granted via group kvm, so create that in udev.postinst. (Closes: #887852) * Move a few man pages from systemd to systemd-journal-remote. The systemd package shipped a few systemd-journal-remote and systemd-journal-upload related man pages which really belong into the systemd-journal-remote package. Move those man pages into the correct package and add a Breaks/Replaces against systemd accordingly. (Closes: #903557) * autopkgtest: Drop no-longer needed workaround from upstream test * Go back to statically allocate system users for timesyncd, networkd and resolved. There are currently too many open issues related to D-Bus and the usage of DynamicUser. (Closes: #902971) * Change python3-minimal dependency to python3. While we strictly only need python3-minimal, the usage of python3-minimal triggers a lintian error: depends-on-python-minimal * test: Drop SKIP_INITRD for QEMU-based tests. The Debian Linux kernel ships ext4 support as a module, so we require an initrd to successfully start the QEMU images. * debian/tests/localed-x11-keymap: Deal with absence of /etc/default/keyboard more gracefully * autopkgtest: Add various dependencies to make upstream test pass on Debian - netcat-openbsd: Required by TEST-12-ISSUE-3171. - busybox-static: Required by TEST-13-NSPAWN-SMOKE. - plymouth: Required by TEST-15-DROPIN and TEST-22-TMPFILES. * Drop seccomp system call filter for udev. The seccomp based system call whitelist requires at least systemd 239 to be the active init and during a dist-upgrade we can't guarantee that systemd has been fully configured before udev is restarted. The versioned systemd Breaks that was added to udev for #902185 didn't really fix this issue, so revert that change again. (Closes: #903224) Checksums-Sha1: 4009df952a29a328b8dd34c592495eae15f285b7 4835 systemd_239-6.dsc 38c17e4a85d4c8358f080f468ee774dd8de98d9d 141596 systemd_239-6.debian.tar.xz b1e16527cc2116f6b449a5cb9f4cb53074ee955d 9270 systemd_239-6_source.buildinfo Checksums-Sha256: 234a8f7a190f2eae2acf325cbd4cf606423f6abfebed3ec391059bb2397199e7 4835 systemd_239-6.dsc ffe18429d3f7184cddd11058a0633d04768aab11f8ddf982b506b0cd8c2c97e9 141596 systemd_239-6.debian.tar.xz 14da36cafd90e1f4d2b0415b32b4195efb7859204a45b0a36d3d61b56cd90a71 9270 systemd_239-6_source.buildinfo Files: b0297cc89f8f3d75f8e17420812cbdaf 4835 admin optional systemd_239-6.dsc 7dec862da4c060e49adeba5f583c11da 141596 admin optional systemd_239-6.debian.tar.xz 281061bd8700ef73b1aacd255cc71bbc 9270 admin optional systemd_239-6_source.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAltQMmgACgkQauHfDWCP ItzHCA//Ti9DOauc2bYXwFzlmnNGmZKYg3Als2aI7eXil8bkkToSIiwQH3cU1ieH /x8YPgWfGuoRne7zhQ83DpGtMELVvcLXXWY1OZfnZcS5PNeMIbZo6OeBJkf1OsDM TWqJ4l4tnhU2sEWtWHGdHaPCwkzChPSYmMuDiR0stWPTAeyhYLq7kWR8Yh2TMSL5 NB+6rDbUj5edNAaCJSbsRN/ESwgy2fvRL7r3eORSshHB4DesTdSXq+FOp7Yf8zOK U29VI7cjpV1onbLGjlw/WVVfcKXPrSVoN9/EYVa/4NUTRkFAX9hCIoR3R43sRyyJ C/hRgBMWRhWCjRfnPclcsspkXP7u+QSzt/AjZKSWtcUryGRSF9fzueLDUB66wxLZ K8dIzpS/SCjlIMeQJ6Rk5N/viJmVNUJfx5xWCvq3DZKQ3vCUbkgp3MYdjUdeWF00 6BovVLE3jYYtcQZSTM5P+VtqX6pwgLmYK+BGV8cJri4Cx0F2kltbr8vCWixaCnrP iue1hmw7Cxey2ENbCLJ4B/+PV1d7iJxhS1MLcyuiqCKFq2inDwiokRkDc5cw+i1c 1frRxcHFaAppehqoR+fG4HARyyRHvuTmzMuAIMoUvGwjqbaOgQ65FKHbNWoXOYps KNsts9TCy7YKCMH9aiY23R3AbubmsFBcR3quZTAE2ai2Nk6s0iE= =NsFv -----END PGP SIGNATURE-----
--- End Message ---
_______________________________________________ Pkg-systemd-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
