Am 17.07.2014 13:00, schrieb Axel Beckert: > > I upgraded from 204-14 to 208-6 last night and today in the morning, I > noticed that journalctl doesn't show any entries from after the > upgrade. Neither the at that time running "journalctl -f" nor a freshly > called journalctl show anything new. Just calling journalctl, it shows > all messages from boot up to when the upgrade happened. > > There is no syslog daemon like e.g. rsyslog installed. > > I have not yet rebooted, but I do expect that syslog must work after > upgrading systemd without having rebooted. Otherwise it would be a > severe data loss. And even if that would be the case: Either the running > "jpurnalctl -f" from 204 or the just called "journalctl" from 208 should > show something in this case. > > If I can provide more information to investigate this issue, feel free > to ask. I'm though currently travelling (actually I noticed it because I > wanted to check for ppp messages in syslog) so I may lag a little bit > with regards to responses. >
Do you use persistent logging (i.e. do you have a /var/log/journal directory) or do you use volatile logging? What are the permissions of of the journal directory and the files therein (either /var/log/journal or /run/log/journal)? What is the output of systemctl status systemd-journald.service systemd-journald.socket Is the systemd-journald process still running? Can you strace it and trigger a log message via "logger". -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
