Hi,
Michael Biebl wrote:
> tags 755062 + moreinfo unreproducible
[...]
> I just tested various upgrades from 204-14 (with and without persistent
> journal, VM and real hardware) and was not able to reproduce the
> problem.
Ok, so it's nothing which seems to happen in too many cases. Glad to
hear.
Anyway, you tagged it "moreinfo" but didn't specify what kund of info
you would like to have?
Since I plan to reboot soon (and then can also tell if a reboot
"fixes" the issue), it'd be nice to know what kind of information you
expect or how I can get some debug info from systemd without rebooting
and without journalctl...
I've tried so far:
# systemctl reload-or-restart systemd-journald.service
# systemctl -l status systemd-journald.service
systemd-journald.service - Journal Service
Loaded: loaded (/lib/systemd/system/systemd-journald.service; static)
Active: active (running) since Thu 2014-07-17 23:18:02 CEST; 2min 12s ago
Docs: man:systemd-journald.service(8)
man:journald.conf(5)
Main PID: 21568 (systemd-journal)
Status: "Processing requests..."
CGroup: /system.slice/systemd-journald.service
└─21568 /lib/systemd/systemd-journald
Jul 17 23:18:02 c-cactus systemd-journal[21568]: Runtime journal is using 67.7M
(max allowed 153.9M, trying to leave 230.8M free of 1.4G available → current
limit 153.9M).
Jul 17 23:18:02 c-cactus systemd-journal[21568]: Runtime journal is using 67.7M
(max allowed 153.9M, trying to leave 230.8M free of 1.4G available → current
limit 153.9M).
Jul 17 23:18:02 c-cactus systemd-journal[21568]: Journal started
Jul 17 23:18:02 c-cactus systemd-journal[21568]: Runtime journal is using 67.7M
(max allowed 153.9M, trying to leave 230.8M free of 1.4G available → current
limit 153.9M).
#
So journald seems running and has been restarted by the first command.
Still no output in the log, though.
> Also considering, that we still install rsyslog by default, I'm
> going to lower the severity to important.
I'll also try to install rsyslog before rebooting to see if that
receives something if I call "echo foo | logger" -- "journalctl -f"
remains silent in that case. Shall I raise the severity again, if even
that doesn't work?
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
`- | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
