Bug#848044: Any solution?

[lumin]

On Fri, 2017-02-10 at 03:22 +0100, Michael Biebl wrote:
> I suspect this is a problem in either LVM/DM or cryptsetup.
> 
> You should probably talk to those maintainers.

a similar bug reported against cryptsetup:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824098

a similar bug reported against lvm2:

https://bugzilla.redhat.com/show_bug.cgi?id=1299178

No solution is found.

___
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#854699: Shutdown fails with an encrypted filesystem on virtio device

[Michael Biebl]

Am 09.02.2017 um 16:39 schrieb Yuri D'Elia:
> Package: systemd
> Version: 232-15
> Severity: normal
> 
> I've setup a VM using kvm with a virtio block device, running debian
> unstable
> and an encrypted root filesystem (automatically setup during
> installation as
> lvm+encrypted volume).
> 
> Somehow, systemd tries to stop the lvm/crypto block devices way too early
> during shutdown, causing the root filesystem to be left unsynced.
> 
> I'm running an identical setup on the real hardware, and the shutdown
> sequence
> is correct, so I assume there is some issue with how virtio block
> devices are
> seen by systemd? Aside from the system using /dev/vda instead of
> /dev/sda, the
> partition scheme and the rest of the setup is identical.
> 
> This is the visible shutdown sequence on the console:
> 
> 
> [  OK  ] Stopped target System Time Synchronized.
> [  OK  ] Stopped target Network is Online.
> [  OK  ] Stopped target Network.
> Stopping Raise network interfaces...
> [  OK  ] Started Show Plymouth Reboot Screen.
> [11899.805246] systemd[1]: Stopped (with error)
> /dev/disk/by-id/lvm-pv-uuid-sHRNAT-RMhn-Xhi6-8maP-jAdc-OLVu-nS2bY3.
> [FAILED] Stopped (with error)
> /dev/disk/by-i…T-RMhn-Xhi6-8maP-jAdc-OLVu-nS2bY3.
> [11899.808206] systemd[1]: Stopped (with error)
> /dev/disk/by-id/dm-name-vda5_crypt.
> [FAILED] Stopped (with error) /dev/disk/by-id/dm-name-vda5_crypt.
> [11899.813510] systemd[1]: Stopped (with error)
> /sys/devices/virtual/block/dm-3.
> [FAILED] Stopped (with error) /sys/devices/virtual/block/dm-3.
> [11899.815784] systemd[1]: Stopped (with error) /dev/dm-3.
> [FAILED] Stopped (with error) /dev/dm-3.
> [11899.817433] systemd[1]: Stopped (with error) /dev/dm-0.
> [FAILED] Stopped (with error) /dev/dm-0.
> [11899.819205] systemd[1]: Stopped (with error)
> /sys/devices/virtual/block/dm-0.
> [FAILED] Stopped (with error) /sys/devices/virtual/block/dm-0.
> [11899.821010] systemd[1]: Stopped (with error) /dev/mapper/backup_crypt.
> [FAILED] Stopped (with error) /dev/mapper/backup_crypt.
> [11899.822558] systemd[1]: Stopped (with error) /dev/mapper/vda5_crypt.
> [FAILED] Stopped (with error) /dev/mapper/vda5_crypt.
> [FAILED] Stopped (with error)
> /dev/disk/by-i…0b4d27a1048270f285d317-vda5_crypt.

Looks similar to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848044 and a lot like
https://github.com/systemd/systemd/issues/1620


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
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: bug 848044 is forwarded to https://github.com/systemd/systemd/issues/1620

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 848044 https://github.com/systemd/systemd/issues/1620
Bug #848044 [systemd] systemd: Stretch+Luks system encryption + LVM = delayed 
shutdown - A stop job is waiting for..
Set Bug forwarded-to-address to 
'https://github.com/systemd/systemd/issues/1620'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
848044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848044
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#848044: Any solution?

[Michael Biebl]

Am 10.02.2017 um 02:16 schrieb lumin:
> Version: 232-16
> 
> Same here.
> Does anyone have a solution to this problem?

I suspect this is a problem in either LVM/DM or cryptsetup.

You should probably talk to those maintainers.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
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#848044: Any solution?

[lumin]

Version: 232-16

Same here.
Does anyone have a solution to this problem?

___
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#764231: marked as done (systemd: boot hangs when starting bluetooth)

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2017 01:32:28 +0100
with message-id <404a8ba5-a9c9-ac79-c230-93073d0ff...@debian.org>
and subject line Re: Bug#764231: systemd: boot hangs when starting bluetooth
has caused the Debian Bug report #764231,
regarding systemd: boot hangs when starting bluetooth
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.)


-- 
764231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: systemd
Version: 215-5

When booting, the system hangs when "[] Starting bluetooth:" for an 
indefinite period of time after updating my system. I have been running 
Testing for many months now without this problem.


I am running the latest version of Debian Jessie as of yesterday at around 
5pm on a Lenovo Thinkpad X230.


Thank you,
Blake

PS: Please disregard my last accidental bug report. (#764227)
--- End Message ---
--- Begin Message ---
Am 20.12.2016 um 00:53 schrieb Michael Biebl:
> Control: tags -1 + moreinfo
> 
> On Mon, 6 Oct 2014 10:10:49 -0400 (CLT) Blake Pantoja
>  wrote:
>> Package: systemd
>> Version: 215-5
>>
>> When booting, the system hangs when "[] Starting bluetooth:" for an 
>> indefinite period of time after updating my system. I have been running 
>> Testing for many months now without this problem.
>>
>> I am running the latest version of Debian Jessie as of yesterday at around 
>> 5pm on a Lenovo Thinkpad X230.
> 
> Is this problem still reproducible? If so, can you please tell us the
> systemd version and boot with "systemd.log_level=debug
> systemd.debug-shell" on the kernel-command-line.
> 
> This will give you a debug shell on tty9, which you can switch to with
> ALT+F9. There you can inspect the system.
> 
> The output of systemctl list-jobs, journalctl -alb and pstree would be
> helpful.

Closing as no further information was provided. The existing information
is not sufficient.

Regards,
Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
--- End Message ---
___
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: pending-bugs

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 854392 pending
Bug #854392 [src:systemd] Run "make check" as root via autopkgtest
Added tag(s) pending.
> tag 854396 pending
Bug #854396 [src:systemd] test_exec_privatenetwork is not run due to missing ip
Added tag(s) pending.
> tag 854394 pending
Bug #854394 [src:systemd] test_exec_capabilityboundingset is not run due to 
missing capsh
Added tag(s) pending.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
854392: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854392
854394: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854394
854396: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854396
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#808884: marked as done (filesystem check progress messages to boot console always remain at 0.0% if more than one filesystem is being checked)

[Debian Bug Tracking System]

Your message dated Fri, 10 Feb 2017 02:25:36 +0800
with message-id <87vasj8bmn@jidanni.org>
and subject line Re: filesystem check progress messages to boot console always 
remain at 0.0% if more than one filesystem is being checked
has caused the Debian Bug report #808884,
regarding filesystem check progress messages to boot console always remain at 
0.0% if more than one filesystem is being checked
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.)


-- 
808884: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808884
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 228-2+b1
Severity: minor

If there are any "(checking 2 filesystems)" type messages to the console
upon boot, the progress will always just show 0.0%.

checking one filesystem messages work fine, but if it is checking more
than one, then progress percentages stay at 0.0% though indeed after a
minute the check still completes.


# journalctl |grep check\ forced
12月 24 10:39:06 jidanni2 systemd-fsck[368]: /dev/sda7 has been mounted 21 times 
without being checked, check forced.
12月 24 10:40:35 jidanni2 systemd-fsck[373]: /dev/sda6 has been mounted 35 times 
without being checked, check forced.


12月 24 10:39:04 jidanni2 systemdstemd[1]: Found device FUJITSU_MHT2040AT 12.
12月 24 10:39:04 jidanni2 systemd[1]: Found device FUJITSU_MHT2040AT 7.
12月 24 10:39:04 jidanni2 systemd[1]: Starting File System Check on 
/dev/disk/by-uuid/34610b6a-70a3-48d9-b135-9
6907dc2ba16...
12月 24 10:39:04 jidanni2 systemd[1]: Activating swap 
/dev/disk/by-uuid/ce5499e2-019e-44cc-8f95-d027832b3d7d...
12月 24 10:39:04 jidanni2 systemd[1]: Reached target Sound Card.
12月 24 10:39:04 jidanni2 systemd[1]: Listening on Load/Save RF Kill Switch 
Status /dev/rfkill Watch.
12月 24 10:39:05 jidanni2 kernel: Adding 997884k swap on /dev/sda12.  
Priority:-1 extents:1 across:997884k FS
12月 24 10:39:05 jidanni2 systemd[1]: Activated swap 
/dev/disk/by-uuid/ce5499e2-019e-44cc-8f95-d027832b3d7d.
12月 24 10:39:05 jidanni2 systemd[1]: Reached target Swap.
12月 24 10:39:06 jidanni2 systemd-fsck[368]: /dev/sda7 has been mounted 21 times 
without being checked, check f
orced.
12月 24 10:39:06 jidanni2 systemd[1]: Found device FUJITSU_MHT2040AT 6.
12月 24 10:39:06 jidanni2 systemd[1]: Starting File System Check on 
/dev/disk/by-uuid/355d426a-cbfc-4faf-91d6-4
f9405199517...
12月 24 10:39:09 jidanni2 systemd-udevd[335]: Process '/usr/sbin/alsactl -E 
HOME=/var/run/alsa restore 1' faile
d with exit code 99.
12月 24 10:39:09 jidanni2 systemd-udevd[330]: Process '/usr/sbin/alsactl -E 
HOME=/var/run/alsa restore 29' fail
ed with exit code 99.
12月 24 10:39:09 jidanni2 systemd-udevd[334]: Process '/usr/sbin/alsactl -E 
HOME=/var/run/alsa restore 0' faile
d with exit code 99.
12月 24 10:40:35 jidanni2 systemd-fsck[368]: /dev/sda7: 13217/678912 files 
(11.4% non-contiguous), 2570599/5428
048 blocks
12月 24 10:40:35 jidanni2 systemd[1]: Started File System Check on
/dev/disk/by-uuid/34610b6a-70a3
...
--- End Message ---
--- Begin Message ---
OK perhaps better now. Closing.--- End Message ---
___
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#852811: marked as done (udev: Doesn't start after upgrade mipsel, powerpc)

[Debian Bug Tracking System]

Your message dated Thu, 09 Feb 2017 17:34:33 +
with message-id 
and subject line Bug#852811: fixed in systemd 232-16
has caused the Debian Bug report #852811,
regarding udev: Doesn't start after upgrade mipsel, powerpc
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.)


-- 
852811: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852811
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: udev
Version: 232-14
Severity: important

Dear Maintainer,

Maybe the problem is because / is a RAID0 ?

Setting up udev (232-14) ...
addgroup: The group `input' already exists as a system group. Exiting.
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: activating (start) since Fri 2017-01-27 14:50:00 CET; 16ms ago
 Docs: man:systemd-udevd.service(8)
   man:udev(7)
 Main PID: 13630 ((md-udevd))
Tasks: 1
   CGroup: /system.slice/systemd-udevd.service
   ‣ 13630 [(md-udevd)]

Jan 27 14:50:00 fabian.marillat.net systemd[1]: Starting udev Kernel Device 
Manager...
dpkg: error processing package udev (--configure):
 subprocess installed post-installation script returned error exit status 1


$ systemctl status systemd-udevd.service
● 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 Fri 2017-01-27 14:51:23 CET; 3min 
52s ago
 Docs: man:systemd-udevd.service(8)
   man:udev(7)
  Process: 15711 ExecStart=/lib/systemd/systemd-udevd (code=exited, 
status=232/ADDRESS_FAMILIES)
 Main PID: 15711 (code=exited, status=232/ADDRESS_FAMILIES)

Jan 27 14:51:23 fabian.marillat.net systemd[1]: systemd-udevd.service: Main 
process exited, code=exited, status=232/ADDRESS_FAMILIES
Jan 27 14:51:23 fabian.marillat.net systemd[1]: Failed to start udev Kernel 
Device Manager.
Jan 27 14:51:23 fabian.marillat.net systemd[1]: systemd-udevd.service: Unit 
entered failed state.
Jan 27 14:51:23 fabian.marillat.net systemd[1]: systemd-udevd.service: Failed 
with result 'exit-code'.
Jan 27 14:51:23 fabian.marillat.net systemd[1]: systemd-udevd.service: Service 
has no hold-off time, scheduling restart.
Jan 27 14:51:23 fabian.marillat.net systemd[1]: Stopped udev Kernel Device 
Manager.
Jan 27 14:51:23 fabian.marillat.net systemd[1]: systemd-udevd.service: Start 
request repeated too quickly.
Jan 27 14:51:23 fabian.marillat.net systemd[1]: Failed to start udev Kernel 
Device Manager.
Jan 27 14:51:23 fabian.marillat.net systemd[1]: systemd-udevd.service: Unit 
entered failed state.
Jan 27 14:51:23 fabian.marillat.net systemd[1]: systemd-udevd.service: Failed 
with result 'exit-code'.




Christian

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: powerpc (ppc64)

Kernel: Linux 4.9.0-1-powerpc64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages udev depends on:
ii  adduser  3.115
ii  dpkg 1.18.19
ii  libacl1  2.2.52-3
ii  libblkid12.28.2-1
ii  libc62.24-9
ii  libgcc1  1:6.3.0-5
ii  libkmod2 23-2
ii  libselinux1  2.6-2
ii  libudev1 232-14
ii  lsb-base 9.20161125
ii  procps   2:3.3.12-3
ii  util-linux   2.28.2-1

udev recommends no packages.

udev suggests no packages.

Versions of packages udev is related to:
ii  systemd  232-14

-- debconf information:
  udev/new_kernel_needed: false
  udev/title/upgrade:
  udev/reboot_needed:
  udev/sysfs_deprecated_incompatibility:

P: /devices/breakpoint
E: DEVPATH=/devices/breakpoint
E: SUBSYSTEM=event_source

P: /devices/cpu
E: DEVPATH=/devices/cpu
E: SUBSYSTEM=event_source

P: /devices/pci:00/:00:0b.0
E: DEVPATH=/devices/pci:00/:00:0b.0
E: ID_MODEL_FROM_DATABASE=CPC945 PCIe Bridge
E: ID_PCI_CLASS_FROM_DATABASE=Bridge
E: ID_PCI_INTERFACE_FROM_DATABASE=Normal decode
E: ID_PCI_SUBCLASS_FROM_DATABASE=PCI bridge
E: ID_VENDOR_FROM_DATABASE=Apple Inc.
E: MODALIAS=pci:v106Bd005Bsvsdbc06sc04i00
E: OF_ALIAS_0=pci0
E: OF_COMPATIBLE_0=u4-pcie
E: OF_COMPATIBLE_N=1
E: OF_FULLNAME=/pci@0,f000
E: 

Bug#850074: marked as done (systemd crashes on daemon-reexec when /run is full)

[Debian Bug Tracking System]

Your message dated Thu, 09 Feb 2017 17:34:33 +
with message-id 
and subject line Bug#850074: fixed in systemd 232-16
has caused the Debian Bug report #850074,
regarding systemd crashes on daemon-reexec when /run is full
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.)


-- 
850074: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850074
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 232-8
Severity: normal

When the systemd package is upgraded, the running instance of systemd is
likely to go into 'freezing execution' mode, in which it is unresponsive
to D-Bus requests until the computer is rebooted.  If a daemon package is
being upgraded at the same time, its postinst is therefore liable to fail,
as it will be unable to ask systemd to restart the daemon.  Here's what
this syndrome looks like in the upgrade crawl:

Extracting templates from packages: 100%
Preconfiguring packages ...
(Reading database ... 271106 files and directories currently installed.)

...
Preparing to unpack .../4-systemd_232-8_amd64.deb ...
Unpacking systemd (232-8) over (232-7) ...
Setting up systemd (232-8) ...
addgroup: The group `systemd-journal' already exists as a system group. Exiting.

Broadcast message from systemd-journald@kenaz (Tue 2017-01-03 13:59:01 EST):

systemd[1]: Freezing execution.
Failed to try-restart systemd-networkd.service: Failed to activate service 
'org.freedesktop.systemd1': timed out
See system logs and 'systemctl status systemd-networkd.service' for details.
Failed to try-restart systemd-resolved.service: Connection timed out
See system logs and 'systemctl status systemd-resolved.service' for details.
Failed to try-restart systemd-timesyncd.service: Failed to activate service 
'org.freedesktop.systemd1': timed out
See system logs and 'systemctl status systemd-timesyncd.service' for details.
(Reading database ... 271105 files and directories currently installed.)
Preparing to unpack .../0-udev_232-8_amd64.deb ...
Unpacking udev (232-8) over (232-7) ...
Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': 
timed out

...
Preparing to unpack .../00-cups-daemon_2.2.1-4_amd64.deb ...
Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': 
timed out
Failed to retrieve unit: Connection timed out
Failed to stop cups.service: Connection timed out
See system logs and 'systemctl status cups.service' for details.
Failed to get load state of cups.service: Failed to activate service 
'org.freedesktop.systemd1': timed out
invoke-rc.d: initscript cups, action "stop" failed.
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': 
timed out
Failed to retrieve unit: Failed to activate service 'org.freedesktop.systemd1': 
timed out
Failed to stop cups.service: Connection timed out
See system logs and 'systemctl status cups.service' for details.
Failed to get load state of cups.service: Failed to activate service 
'org.freedesktop.systemd1': timed out
invoke-rc.d: initscript cups, action "stop" failed.
dpkg: error processing archive 
/tmp/apt-dpkg-install-RbqGAG/00-cups-daemon_2.2.1-4_amd64.deb (--unpack):
 subprocess new pre-removal script returned error exit status 1
Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': 
timed out
Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': 
timed out
Failed to retrieve unit: Connection timed out
Failed to start cups.service: Connection timed out
See system logs and 'systemctl status cups.service' for details.
invoke-rc.d: initscript cups, action "start" failed.
Failed to get properties: Connection timed out
dpkg: error while cleaning up:
 subprocess installed post-installation script returned error exit status 1

...
Errors were encountered while processing:
 /tmp/apt-dpkg-install-RbqGAG/00-cups-daemon_2.2.1-4_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

(There will usually then be a flood of additional error messages from packages
whose dependencies are broken.)

I have been able to work around this by temporarily creating an
/usr/sbin/policy-rc.d that always exits with code 101, but I shouldn't
have to do that.

An ideal fix would be for systemd to support seamless upgrades of itself,
i.e. pid 1 would re-exec itself using the new binary, without losing
any state.  I realize that if this were easy it would already have 

Bug#851164: marked as done (udev: NVMe symlinks broken by devices with spaces in model or serial strings)

[Debian Bug Tracking System]

Your message dated Thu, 09 Feb 2017 17:34:33 +
with message-id 
and subject line Bug#851164: fixed in systemd 232-16
has caused the Debian Bug report #851164,
regarding udev: NVMe symlinks broken by devices with spaces in model or serial 
strings
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.)


-- 
851164: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851164
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 232-8
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu zesty ubuntu-patch

Dear Maintainer,

udev creates symlinks for all NVMe drives at /dev/disk/by-id/nvme-MODEL_SERIAL.
The MODEL and SERIAL strings come directly from the NVMe device, and may
contain whitespace; if they do, this breaks the creation of the symlink
because udev treats it as multiple symlinks, separated by the whitespace.

These patches, which are merged upstream, change udev default behavior to
replace all whitespace, when added to a SYMLINK value as a result of variable
substitution, with underscores.  This results in a single symlink for each
NVMe drive, which is the correct behavior.  Note that this also fixes any
broken symlinks for other devices/buses that are a result of unexpected
whitespace included in variables.

This is tracked upstream in github bug 4833:
https://github.com/systemd/systemd/issues/4833

and in Ubuntu in launchpad bug 1647485:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647485
diff -Nru systemd-232/debian/patches/0001-libudev-util-change-util_replace_whitespace-to-retur.patch systemd-232/debian/patches/0001-libudev-util-change-util_replace_whitespace-to-retur.patch
--- systemd-232/debian/patches/0001-libudev-util-change-util_replace_whitespace-to-retur.patch	1969-12-31 19:00:00.0 -0500
+++ systemd-232/debian/patches/0001-libudev-util-change-util_replace_whitespace-to-retur.patch	2017-01-12 09:55:40.0 -0500
@@ -0,0 +1,32 @@
+From a9d99b32a34589777e95898dac0597dbfbede4ea Mon Sep 17 00:00:00 2001
+From: Dan Streetman 
+Date: Tue, 3 Jan 2017 14:31:45 -0500
+Subject: [PATCH 1/3] libudev-util: change util_replace_whitespace to return
+ number of chars in dest
+
+Instead of returning 0, which is unhelpful, return the number of chars
+copied into the dest string.  This allows callers that care about that
+to easily use it, instead of having to calculate the strlen.
+
+No current users of the function check the return value, so this does not
+break any existing code; it is used in the following patch.
+---
+ src/libudev/libudev-util.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/libudev/libudev-util.c b/src/libudev/libudev-util.c
+index 574cfea..a9819b9 100644
+--- a/src/libudev/libudev-util.c
 b/src/libudev/libudev-util.c
+@@ -186,7 +186,7 @@ int util_replace_whitespace(const char *str, char *to, size_t len)
+ to[j++] = str[i++];
+ }
+ to[j] = '\0';
+-return 0;
++return j;
+ }
+ 
+ /* allow chars in whitelist, plain ascii, hex-escaping and valid utf8 */
+-- 
+2.9.3
+
diff -Nru systemd-232/debian/patches/0002-udev-event-add-replace_whitespace-param-to-udev_even.patch systemd-232/debian/patches/0002-udev-event-add-replace_whitespace-param-to-udev_even.patch
--- systemd-232/debian/patches/0002-udev-event-add-replace_whitespace-param-to-udev_even.patch	1969-12-31 19:00:00.0 -0500
+++ systemd-232/debian/patches/0002-udev-event-add-replace_whitespace-param-to-udev_even.patch	2017-01-12 09:55:40.0 -0500
@@ -0,0 +1,309 @@
+From e20a917105b9c41e7e552ca5f11f9077897db505 Mon Sep 17 00:00:00 2001
+From: Dan Streetman 
+Date: Tue, 3 Jan 2017 14:37:59 -0500
+Subject: [PATCH 2/3] udev-event: add replace_whitespace param to
+ udev_event_apply_format
+
+If replace_whitespace is true, each substitution value has all its
+whitespace removed/replaced by util_replace_whitespace (except the
+SUBST_RESULT substitution - $result{} or %c{} - which handles spaces
+itself as field separators).  All existing callers are updated to
+pass false, so no functional change is made by this patch.
+
+This is needed so the SYMLINK assignment can replace any spaces
+introduced through variable substitution, becuase the SYMLINK value is
+a space-separated list of symlinks to create.  Any variables that
+contain spaces will thus unexpectedly change the symlink value from
+a single symlink to multiple incorrectly-named symlinks.
+
+This is used in the next patch, which 

systemd_232-16_amd64.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 09 Feb 2017 16:22:43 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines 
libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev libudev1 
libudev-dev udev-udeb libudev1-udeb
Architecture: source amd64
Version: 232-16
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Martin Pitt 
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
 udev   - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Closes: 850074 851164 852811
Changes:
 systemd (232-16) unstable; urgency=medium
 .
   [ Martin Pitt ]
   * Add autopkgtest for test-seccomp
   * udev: Fix by-id symlinks for devices whose IDs contain whitespace
 (Closes: #851164, LP: #1647485)
   * Add lintian overrides for binary-or-shlib-defines-rpath on shipped test
 programs. This is apparently a new lintian warning on which uploads get
 rejected.  These are only test programs, not in $PATH, and they need to
 link against systemd's internal library.
 .
   [ Michael Biebl ]
   * Fix seccomp filtering. (Closes: #852811)
   * Do not crash on daemon-reexec when /run is full (Closes: #850074)
Checksums-Sha1:
 4eea53199288a21aefb65e7e4dc697aff80cbafd 4688 systemd_232-16.dsc
 3eca6ea448eb90ec24b51a5bd9855c0b566a5975 178044 systemd_232-16.debian.tar.xz
 417442864d7269afac993cfdda5c7d3ccb99f605 86934 
libnss-myhostname-dbgsym_232-16_amd64.deb
 db87a7a839c21058b7b8d1a787be4c35068f70c9 100768 
libnss-myhostname_232-16_amd64.deb
 e4e6456d925c3addd829f269c9c3ae06bd61e19c 440664 
libnss-mymachines-dbgsym_232-16_amd64.deb
 8ab99c8552a8bdcd2ec932faf521aea4b2b11b78 182936 
libnss-mymachines_232-16_amd64.deb
 f162caed1c56c9c7ae0c8c5b0fcefea06bc566ba 429944 
libnss-resolve-dbgsym_232-16_amd64.deb
 3fc948c31dedbf026a953b2ada4b1482d29ce588 182408 libnss-resolve_232-16_amd64.deb
 e70fd1af1570e477c00939c087b737e1bd23bde2 427188 
libnss-systemd-dbgsym_232-16_amd64.deb
 5f728cd7fbe85c1971f85b3754d04d9a2909a723 180828 libnss-systemd_232-16_amd64.deb
 08a1ca52af12630bf39629d65f6e2ff3c7a5cb11 424328 
libpam-systemd-dbgsym_232-16_amd64.deb
 fe3d868ef8ba9fcc1906c876986d1ac1b6b383e9 183492 libpam-systemd_232-16_amd64.deb
 f26e3a945b56279b7ef86c8033c93fa08d9643cb 11456 
libsystemd-dev-dbgsym_232-16_amd64.deb
 91c813973d00849ca26731bdbd279e9492901317 244900 libsystemd-dev_232-16_amd64.deb
 7feeada311ed6edd68f031acaf5e088216b36c8e 661478 
libsystemd0-dbgsym_232-16_amd64.deb
 f75eaeb7918f72cb6e145c12b2eff4d908545f4e 275702 libsystemd0_232-16_amd64.deb
 6609dbf7685243911be0efcfe1eb87a873362d65 521088 
libudev-dev-dbgsym_232-16_amd64.deb
 b0eafb6d0e72b7dc2f217c5918d57261bcc59493 257680 libudev-dev_232-16_amd64.deb
 7f8d7fe59dae5854f44069659deb68030612585f 157550 
libudev1-dbgsym_232-16_amd64.deb
 10970fc9f62e79fc81df5975eed0f7e462b25217 48640 libudev1-udeb_232-16_amd64.udeb
 ba1eaf4b079649c2f77e263703b8e9ec9f09e16c 120466 libudev1_232-16_amd64.deb
 5edcabc4730005298137c103756c67a937f6af1c 485138 
systemd-container-dbgsym_232-16_amd64.deb
 1f7676e1b5e7462abb7260ffb687e25c68302d03 285132 
systemd-container_232-16_amd64.deb
 48f7dc37f0712a3a081ba44b54fee6e899b84041 71712 
systemd-coredump-dbgsym_232-16_amd64.deb
 6f80c89eeda6bdc392f34186c260579aa9982c9a 105594 
systemd-coredump_232-16_amd64.deb
 194b921904d568992a5d93b7717bbfdf5decf7d6 5991800 
systemd-dbgsym_232-16_amd64.deb
 852ac2c7c8945038c9bd2c7fd21f456b46f1 110772 
systemd-journal-remote-dbgsym_232-16_amd64.deb
 bb0c1efd6d702f98eba4ce8efc0aecb3e26e9771 125058 
systemd-journal-remote_232-16_amd64.deb
 7a34aa83464f38465442166343c5aecb428fed13 76966 systemd-sysv_232-16_amd64.deb
 4ce6d662eccb71617249080a8302de2273d7c4a0 16558 systemd_232-16_amd64.buildinfo
 b9f6f9222fb8c2c4a59781325e2a332f178cb078 2461628 systemd_232-16_amd64.deb
 02c7e9db5de7482a88a7bc853e79aee4279cb8ab 1331700 udev-dbgsym_232-16_amd64.deb
 

[bts-link] source package systemd

[bts-link-upstream]

#
# bts-link upstream status pull for source package systemd
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#

user bts-link-upstr...@lists.alioth.debian.org

# remote status report for #850074 (http://bugs.debian.org/850074)
# Bug title: systemd crashes on daemon-reexec when /run is full
#  * https://github.com/systemd/systemd/issues/5016
#  * remote status changed: open -> closed
usertags 850074 - status-open
usertags 850074 + status-closed

# remote status report for #852811 (http://bugs.debian.org/852811)
# Bug title: udev: Doesn't start after upgrade mipsel, powerpc
#  * https://github.com/systemd/systemd/issues/5215
#  * remote status changed: (?) -> closed
usertags 852811 + status-closed

# remote status report for #853755 (http://bugs.debian.org/853755)
# Bug title: udev: Doesn't start after upgrade mipsel, powerpc
#  * https://github.com/systemd/systemd/issues/5215
#  * remote status changed: (?) -> closed
usertags 853755 + status-closed

# remote status report for #853940 (http://bugs.debian.org/853940)
# Bug title: udev: Doesn't start after upgrade mipsel, powerpc
#  * https://github.com/systemd/systemd/issues/5215
#  * remote status changed: (?) -> closed
usertags 853940 + status-closed

thanks

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Processing of systemd_232-16_amd64.changes

[Debian FTP Masters]

systemd_232-16_amd64.changes uploaded successfully to localhost
along with the files:
  systemd_232-16.dsc
  systemd_232-16.debian.tar.xz
  libnss-myhostname-dbgsym_232-16_amd64.deb
  libnss-myhostname_232-16_amd64.deb
  libnss-mymachines-dbgsym_232-16_amd64.deb
  libnss-mymachines_232-16_amd64.deb
  libnss-resolve-dbgsym_232-16_amd64.deb
  libnss-resolve_232-16_amd64.deb
  libnss-systemd-dbgsym_232-16_amd64.deb
  libnss-systemd_232-16_amd64.deb
  libpam-systemd-dbgsym_232-16_amd64.deb
  libpam-systemd_232-16_amd64.deb
  libsystemd-dev-dbgsym_232-16_amd64.deb
  libsystemd-dev_232-16_amd64.deb
  libsystemd0-dbgsym_232-16_amd64.deb
  libsystemd0_232-16_amd64.deb
  libudev-dev-dbgsym_232-16_amd64.deb
  libudev-dev_232-16_amd64.deb
  libudev1-dbgsym_232-16_amd64.deb
  libudev1-udeb_232-16_amd64.udeb
  libudev1_232-16_amd64.deb
  systemd-container-dbgsym_232-16_amd64.deb
  systemd-container_232-16_amd64.deb
  systemd-coredump-dbgsym_232-16_amd64.deb
  systemd-coredump_232-16_amd64.deb
  systemd-dbgsym_232-16_amd64.deb
  systemd-journal-remote-dbgsym_232-16_amd64.deb
  systemd-journal-remote_232-16_amd64.deb
  systemd-sysv_232-16_amd64.deb
  systemd_232-16_amd64.buildinfo
  systemd_232-16_amd64.deb
  udev-dbgsym_232-16_amd64.deb
  udev-udeb_232-16_amd64.udeb
  udev_232-16_amd64.deb

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

___
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: Re: filesystem check progress messages to boot console always remain at 0.0% if more than one filesystem is being checked

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #808884 [systemd] filesystem check progress messages to boot console always 
remain at 0.0% if more than one filesystem is being checked
Added tag(s) moreinfo.

-- 
808884: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808884
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#808884: filesystem check progress messages to boot console always remain at 0.0% if more than one filesystem is being checked

[Michael Biebl]

Control: tags -1 moreinfo

On Thu, 24 Dec 2015 10:52:16 +0800 =?utf-8?B?56mN5Li55bC8?= Dan Jacobson
 wrote:
> Package: systemd
> Version: 228-2+b1
> Severity: minor
> 
> If there are any "(checking 2 filesystems)" type messages to the console
> upon boot, the progress will always just show 0.0%.
> 
> checking one filesystem messages work fine, but if it is checking more
> than one, then progress percentages stay at 0.0% though indeed after a
> minute the check still completes.

Seems to work fine here (using 232-15).

Can you still reproduce the problem with an up-to-date version?
What file system is that? Does the fsck utility for that file system
provide progress information?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

systemd_232-16_amd64.changes REJECTED

[Debian FTP Masters]

libsystemd-dev: lintian output: 'binary-or-shlib-defines-rpath 
usr/lib/x86_64-linux-gnu/systemd/test-seccomp /lib/systemd', automatically 
rejected package.
libsystemd-dev: If you have a good reason, you may override this lintian tag.
libudev-dev: lintian output: 'binary-or-shlib-defines-rpath 
usr/lib/x86_64-linux-gnu/udev/test-udev /lib/systemd', automatically rejected 
package.
libudev-dev: If you have a good reason, you may override this lintian tag.



===

Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.


___
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: retitle 851402 to /var stays busy at shutdown due to journald

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 851402 /var stays busy at shutdown due to journald
Bug #851402 [systemd] failed unmounting /var during shutdown
Changed Bug title to '/var stays busy at shutdown due to journald' from 'failed 
unmounting /var during shutdown'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
851402: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851402
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#854699: Shutdown fails with an encrypted filesystem on virtio device

[Yuri D'Elia]

Package: systemd
Version: 232-15
Severity: normal

I've setup a VM using kvm with a virtio block device, running debian unstable
and an encrypted root filesystem (automatically setup during installation as
lvm+encrypted volume).

Somehow, systemd tries to stop the lvm/crypto block devices way too early
during shutdown, causing the root filesystem to be left unsynced.

I'm running an identical setup on the real hardware, and the shutdown sequence
is correct, so I assume there is some issue with how virtio block devices are
seen by systemd? Aside from the system using /dev/vda instead of /dev/sda, the
partition scheme and the rest of the setup is identical.

This is the visible shutdown sequence on the console:


[  OK  ] Stopped target System Time Synchronized.
[  OK  ] Stopped target Network is Online.
[  OK  ] Stopped target Network.
Stopping Raise network interfaces...
[  OK  ] Started Show Plymouth Reboot Screen.
[11899.805246] systemd[1]: Stopped (with error) 
/dev/disk/by-id/lvm-pv-uuid-sHRNAT-RMhn-Xhi6-8maP-jAdc-OLVu-nS2bY3.
[FAILED] Stopped (with error) /dev/disk/by-i…T-RMhn-Xhi6-8maP-jAdc-OLVu-nS2bY3.
[11899.808206] systemd[1]: Stopped (with error) 
/dev/disk/by-id/dm-name-vda5_crypt.
[FAILED] Stopped (with error) /dev/disk/by-id/dm-name-vda5_crypt.
[11899.813510] systemd[1]: Stopped (with error) /sys/devices/virtual/block/dm-3.
[FAILED] Stopped (with error) /sys/devices/virtual/block/dm-3.
[11899.815784] systemd[1]: Stopped (with error) /dev/dm-3.
[FAILED] Stopped (with error) /dev/dm-3.
[11899.817433] systemd[1]: Stopped (with error) /dev/dm-0.
[FAILED] Stopped (with error) /dev/dm-0.
[11899.819205] systemd[1]: Stopped (with error) /sys/devices/virtual/block/dm-0.
[FAILED] Stopped (with error) /sys/devices/virtual/block/dm-0.
[11899.821010] systemd[1]: Stopped (with error) /dev/mapper/backup_crypt.
[FAILED] Stopped (with error) /dev/mapper/backup_crypt.
[11899.822558] systemd[1]: Stopped (with error) /dev/mapper/vda5_crypt.
[FAILED] Stopped (with error) /dev/mapper/vda5_crypt.
[FAILED] Stopped (with error) /dev/disk/by-i…0b4d27a1048270f285d317-vda5_crypt.
[  OK  ] Stopped LSB: Start/stop the postgrey daemon.
[  OK  ] Stopped target Basic System.
[  OK  ] Stopped target Sockets.
[  OK  ] Closed Syslog Socket.
[  OK  ] Closed UUID daemon activation socket.
[  OK  ] Closed D-Bus System Message Bus Socket.
[  OK  ] Stopped target Remote File Systems.
[  OK  ] Stopped target Slices.
[  OK  ] Removed slice User and Session Slice.
[  OK  ] Stopped target Paths.
[  OK  ] Stopped systemd-cron path monitor.
[  OK  ] Stopped ACPI Events Check.
[  OK  ] Closed ACPID Listen Socket.
[  OK  ] Stopped target System Initialization.
Stopping Load/Save Random Seed...
Stopping Update UTMP about System Boot/Shutdown...
[  OK  ] Stopped target Encrypted Volumes.
Stopping Cryptography Setup for backup_crypt...
[  OK  ] Stopped Forward Password Requests to Wall Directory Watch.
Stopping Cryptography Setup for vda5_crypt...
Stopping Network Time Synchronization...
[  OK  ] Stopped Load/Save Random Seed.
[  OK  ] Stopped Network Time Synchronization.
[  OK  ] Stopped Update UTMP about System Boot/Shutdown.
[  OK  ] Stopped Create Volatile Files and Directories.
[  OK  ] Stopped Cryptography Setup for backup_crypt.
[  OK  ] Stopped Raise network interfaces.
[  OK  ] Stopped target Network (Pre).
Stopping ferm firewall configuration...
[  OK  ] Stopped target Local File Systems.
Unmounting /boot...
Unmounting Temporary Directory...
Unmounting /run/user/0...
[  OK  ] Stopped Apply Kernel Variables.
[  OK  ] Stopped Load Kernel Modules.
[  OK  ] Unmounted /run/user/0.
[  OK  ] Unmounted Temporary Directory.
[  OK  ] Stopped target Swap.
Deactivating swap /dev/test-vg/swap_1...
[  OK  ] Deactivated swap /dev/test-vg/swap_1.
[  OK  ] Deactivated swap /dev/disk/by-uuid/…b58ce-41b3-4341-bd9d-98c4a7bab372.
[  OK  ] Deactivated swap /dev/disk/by-id/dm…vo0DXoVoelCMxoj00n4D8AA9T0tuJtogp.
[  OK  ] Deactivated swap /dev/disk/by-id/dm-name-test--vg-swap_1.
[  OK  ] Deactivated swap /dev/dm-2.
[  OK  ] Deactivated swap /dev/mapper/test--vg-swap_1.
[  OK  ] Unmounted /boot.
[  OK  ] Stopped File System Check on /dev/d…24dbc-8f9e-44c4-8f4b-82c25271a2a4.
[  OK  ] Stopped target Local File Systems (Pre).
[  OK  ] Stopped Remount Root and Kernel File Systems.
Stopping Monitoring of LVM2 mirrors…ng dmeventd or progress polling...
[  OK  ] Stopped Create Static Device Nodes in /dev.
[  OK  ] Removed slice system-systemd\x2dfsck.slice.
[  OK  ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling.
Stopping LVM2 metadata daemon...
[  OK  ] Stopped LVM2 metadata daemon.
[  OK  ] Stopped ferm firewall configuration.
[  OK  ] Stopped Cryptography Setup for vda5_crypt.
[  OK  ] Reached target Unmount All Filesystems.
[  OK  ] Removed slice system-systemd\x2dcryptsetup.slice.
[  OK  ] Reached target Shutdown.

Since the 

Bug#793116: systemd-journald exiting with SIGUSR1

[Joseph Landry]

I came to the same conclusion as Daniel Povey in Message #56.

RestartSec in systemd-journal-flush does not help in this case. it is a 
one-shot service and it will not be restarted.

Note that in my case systemd-journald is killed due to a watchdog timeout when 
the server is under heavy load.

As a workaround, I set "Type=notify" (instead of the default "Type=simple") in 
systemd-journald's [Service] section . I assume it should delay 
systemd-journal-flush.service until systemd-journald is ready to handle the 
signal.
Worst case scenario : systemd-journald does notify that it has started before 
installing the signal-handler. Then the workaround would only minimize the 
effect and I guess it would be an upstream bug. 

But to stay on the safe side I also added these settings to give 
systemd-journald a chance to restart at a latter time (still in the [Service] 
section):
# wait 5s at restart.
# fails if restarted more than 100 times within 10mn
RestartSec=5
StartLimitBurst=100
StartLimitInterval=600

Finally I increased WatchdogSec in order to be more tolerant to high load but I 
think it is out of the scope of this bug.

___
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: tagging 850074

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 850074 + fixed-upstream
Bug #850074 [systemd] systemd crashes on daemon-reexec when /run is full
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
850074: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850074
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#853755: installation-reports: ppc64el fails to boot after installation

[Erwan Prioul]

I ran successful tests from [1] which includes the upstream commit from [2].

[1] 
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=4de2441f351136a0f6f5b9797a77f9705879ccdf
[2] https://github.com/systemd/systemd/issues/5230

Erwan.



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers