You are not logged in.
Hi,
It took some time for me to write the first version of this post since English is not my main language – long enough, apparently, that I got logged out before I finished, resulting in the post to vanish completely instead of being posted. So I'm sorry if this version here is not that well elaborated …
Basically, the issue I'm currently having is that I changed the journal storage type to "volatile" and later to "persistent" in /etc/systemd/journald.conf. Now no new entries are added to the journal until I manually execute "systemctl restart systemd-journald". After I do this, the journal seems to work normal until I shutdown the machine – then, the last entry of the journal is that the journal stops and afterwards, I'm back in the state where no entries at all are added. Yet, it is the case that systemd-journald appears as an entry in the output of "systemctl list-units", even directly after reboot.
Can anyone help me with this issue. I would like to have a persistent journal again, but one which starts logging automatically on startup.
Thanks in advance,
x432ph
Offline
Im shooting in the dark here, but maybe
sudo systemctl enable systemd-journaldworks?
As far as I know, the worlds most northern "Archer" @ 69.67 N, Kirkenes, Norway. Can you beat me? Please notify me and upload your coordinates at ArchMap
Offline
Im shooting in the dark here, but maybe
sudo systemctl enable systemd-journaldworks?
I tried this before, it says that systemd-journald isn't meant to be enabled via systemctl.
Offline
Hi x432ph and welcome to the forum,
Maybe you could try this: https://bbs.archlinux.org/viewtopic.php … 0#p1219870
Offline
I'm having the exact same problem and I've asked here, on reddit twice and finally opened an issue on the systemd Github. Here's my post: https://bbs.archlinux.org/viewtopic.php?id=200550. See if it's similar to my problem.
At first I thought it was a race condition, but for some reason both sending the journal process SIGUSR1 and manually running the journalctl --flush command do not cause it to flush, even though everything *should* by now be able to flush properly. Keep an eye on the github issue, hopefully we'll be able to figure out the issue there: https://github.com/systemd/systemd/issues/832
Offline