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 aga
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).
>
> Som
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/syst
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
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
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 mar
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 pen
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
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 d
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
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
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 d
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 l
#
# 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
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
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 Tracki
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%.
>
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
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
Sto
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
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
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
Processing commands for cont...@bugs.debian.org:
> tags 850074 + pending
Bug #850074 [systemd] systemd crashes on daemon-reexec when /run is full
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
850074: http://bugs.debian.org/cgi-bin/bugreport
Processing commands for cont...@bugs.debian.org:
> tags 851164 + pending
Bug #851164 [systemd] udev: NVMe symlinks broken by devices with spaces in
model or serial strings
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
851164: http://bugs.d
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
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 sig
26 matches
Mail list logo
