On Mon, 03.08.15 22:09, Dan Checkoway (d...@layer.com) wrote:
> Hello,
>
> Before filing a bug report, I wanted to run this by the group to make sure
> I'm not doing something dumb (it happens). We're seeing systemd-journald
> crash with:
As a follow-up, for the sake of the archives' completene
On 08/05/2015 12:50 PM, Sebastian Schindler wrote:
> Hi,
>
> I have Systemd v216 on a VM, there I was able to reproduce this.
> I did use this tool https://github.com/carosio/jlog to create the logs:
>
> jlog 'MESSAGE=this will crash' 'SYSLOG_IDENTIFIER=foobar' 'SYSLOG_FACILITY=3'
> 'PRIORITY=5'
Hi,
I have Systemd v216 on a VM, there I was able to reproduce this.
I did use this tool https://github.com/carosio/jlog to create the logs:
jlog 'MESSAGE=this will crash' 'SYSLOG_IDENTIFIER=foobar' 'SYSLOG_FACILITY=3'
'PRIORITY=5' 'KEY5=foobar' 'KEY6=foobar' 'KEY7=foobar' 'KEY8=foobar'
'KEY9=f
Hello,
Before filing a bug report, I wanted to run this by the group to make sure
I'm not doing something dumb (it happens). We're seeing systemd-journald
crash with:
Assertion 'n + 20 + (object_pid ? 11 : 0) <= m' failed at
/build/amd64-usr/var/tmp/portage/sys-apps/systemd-218-r5/work/systemd-2
