In my case the issue is that if you delete /etc/machine-id, then
journald will crash.
I tracked it down with strace.
I would say it's a bug to crash if it's not available.
2016-10-21 16:39 GMT+02:00 Debian Bug Tracking System :
> Thank you for the additional information you have supplied regardi
No. Journald doesn't start from boot, rsyslog does but isn't listening
to the socket.
and if I run
$ logger ciao
logger: socket /dev/log: Connessione rifiutata
Files open by rsyslog are these:
root@mongibello /proc/948/fd # ll
totale 0
lr-x-- 1 root root 64 ott 21 14:53 0 -> /dev/null
l-wx
Am 21.10.2016 um 15:31 schrieb Salvo Tomaselli:
> Hello,
>
> me neither. I don't know when it 1st happened. I just wanted to see
> something in the logs and there were no logs besides the ones
> generated by the kernel in /var/log/syslog
/var/log/syslog is not generated by the kernel, but your s
Hello,
me neither. I don't know when it 1st happened. I just wanted to see
something in the logs and there were no logs besides the ones
generated by the kernel in /var/log/syslog
I don't know how you can reproduce the problem.
I did not change my journald.conf, which I attach.
2016-10-21 15:2
Control: severity -1 important unreproducible
Control: tags -1 moreinfo
Am 21.10.2016 um 15:02 schrieb Salvo Tomaselli:
> severity 793116 critical
> thanks
>
> I am experiencing the same problem, but upon reboot journald won't
> start, so I have no logging whatsoever.
>
> For this reason I'm ra
Processing control commands:
> severity -1 important unreproducible
Unknown command or malformed arguments to command.
> tags -1 moreinfo
Bug #793116 [systemd] systemd: journald randomly exits with USR1, leaving
/dev/log unusable
Added tag(s) moreinfo.
--
793116: http://bugs.debian.org/cgi-bin
severity 793116 critical
thanks
I am experiencing the same problem, but upon reboot journald won't
start, so I have no logging whatsoever.
For this reason I'm raising the severity of the problem, since I have
no way of knowing what the daemons on my machine are up to.
___
