Bug#793116: systemd-journald exiting with SIGUSR1

2016-10-15 Thread Daniel Povey 
Another observation about this bug, which might be helpful.

If the signal is sent to systemd-journald via
/bin/systemctl kill --kill-who=main --signal=SIGUSR1
systemd-journald.service
then messages like the following show up in the kernel messages from `dmesg
-T`, like:

[Sat Oct 15 21:02:35 2016] systemd-journald[26517]: Received request to
flush runtime journal from PID 1

but they don't show up in the output of 'journalctl -r'.
In  /etc/systemd/journald.conf, it says:

#MaxLevelStore=debug
#MaxLevelSyslog=debug

so I would have thought the same messages would go to both places.
I don't know if I'm misunderstanding something here..

Dan





On Sat, Oct 15, 2016 at 9:07 PM, Daniel Povey  wrote:

> BTW, I attach the output from `systemd-analyze dump`, as dump.txt.
> It would be great if the debian people could help us look into this.
> Lennart has a policy that his team will only look into bug reports in the
> latest two versions of systemd, and obviously we are well behind that.
>
> Dan
>
>
> On Sat, Oct 15, 2016 at 8:53 PM, Daniel Povey  wrote:
>
>>
>> I just want to report that we are suffering from this bug, and it is
>> quite frequent.
>> This is with version  215-17+deb8u5 .
>>
>> root@a12:~# systemctl status systemd-journald
>>
>> *** systemd-journald.service - Journal Service
>>
>>Loaded: loaded (/lib/systemd/system/systemd-journald.service; static)
>>
>>Active: *failed* (Result: start-limit) since Sat 2016-10-15 12:01:57
>> EDT; 8h ago
>>
>>  Docs: man:systemd-journald.service(8)
>>
>>man:journald.conf(5)
>>
>>   Process: 51561 ExecStart=/lib/systemd/systemd-journald *(code=killed,
>> signal=USR1)*
>>
>>  Main PID: 51561 (code=killed, signal=USR1)
>>
>>
>>
>
___
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#793116: systemd-journald exiting with SIGUSR1

2016-10-15 Thread Daniel Povey 
I just want to report that we are suffering from this bug, and it is quite
frequent.
This is with version  215-17+deb8u5 .

root@a12:~# systemctl status systemd-journald

*** systemd-journald.service - Journal Service

   Loaded: loaded (/lib/systemd/system/systemd-journald.service; static)

   Active: *failed* (Result: start-limit) since Sat 2016-10-15 12:01:57
EDT; 8h ago

 Docs: man:systemd-journald.service(8)

   man:journald.conf(5)

  Process: 51561 ExecStart=/lib/systemd/systemd-journald *(code=killed,
signal=USR1)*

 Main PID: 51561 (code=killed, signal=USR1)
___
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#791944: My workaround

2016-10-15 Thread Guilhem Moulin 
On Sat, 15 Oct 2016 at 08:13:27 +0700, Theppitak Karoonboonyanan wrote:
> Reassigning the bug to udev to hear its maintainer's opinion.

I think this is a initscripts bug, not a udev bug.  Both the
‘cryptdisks-early’ and ‘cryptdisks’ LSB init scripts have had a
“Should-Stop: udev” header.  Shouldn't this be enough to have udevd
still running during cryptdisks shutdown?  If that's the case then the
culprit is sendsigs as it violates shutdown dependencies.

-- 
Guilhem.

PS. pkg-cryptsetup-de...@lists.alioth.debian.org added to X-Debbugs-CC.


signature.asc
Description: PGP 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