systemd-journald flush hangs system

[Ralf Corsepius]

On 12/11/2013 03:04 PM, "Jóhann B. Guðmundsson" wrote:
>
> On 12/11/2013 01:50 PM, Ralf Corsepius wrote:
>> Received request to flush runtime journal from PID 1"
>
> With limited info it could be the kernel or it could simply be short on
> space on /var ?

No. Though this is a small RAM and small disk system, space doesn't seem 
to be the issue, this time.

> Follow http://freedesktop.org/wiki/Software/systemd/Debugging/ and see
> if you get something more meaningful
Though this issue meanwhile has happened 3 times, I am still pretty 
clueless. I can't spot anything remarkable or deterministic error 
message in /var/log/messages (rsp. journalctl).

The only noteworthy systemd messages, I am observing is frequent 
messages of this kind in /var/log/messages:
...
Dec 11 16:57:02 gunvald1 dbus-daemon: dbus[580]: [system] Activating via 
systemd: service name='org.freedesktop.ModemManager1' 
unit='dbus-org.freedesktop.ModemManager1.service'
Dec 11 16:57:02 gunvald1 dbus-daemon: dbus[580]: [system] Activation via 
systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': 
Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such 
file or directory.
Dec 11 16:57:02 gunvald1 dbus[580]: [system] Activating via systemd: 
service name='org.freedesktop.ModemManager1' 
unit='dbus-org.freedesktop.ModemManager1.service'
Dec 11 16:57:02 gunvald1 dbus[580]: [system] Activation via systemd 
failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit 
dbus-org.freedesktop.ModemManager1.service failed to load: No such file 
or directory.
...


However, when the "hanger" happened for the 3rd time, I was logged in 
from remote. From this, I can tell the system is still alive, except 
that the console appears to be gone.

Ralf