azlux
azlux
indeed, it's look like the journactl havn't closed the previous boot logs. So the database mess up the logs. Can you run a `journalctl --verify` if any errors ?
Sorry, I will check on it next week (holidays right now) I suppose journactl havn't finish writing logs when log2ram stop the mount point at restart. I will check if...
Is that possible to test with the command : ```journalctl --sync``` before the cp/rsync command here : https://github.com/azlux/log2ram/blob/master/log2ram#L76
You can PR a Dockerfile if you want. I will check on it and upload on my hub.