On Fri, 30 Apr 2021 at 22:15, Michael Biebl <mbi...@gmail.com> wrote: > > Am Fr., 30. Apr. 2021 um 20:27 Uhr schrieb Rick Winscot > <rick.wins...@gmail.com>: > > > At this point, flush is attempting to re-route /run/log/journal to /var/log/journal ... and the /var partition is not yet mounted. Units generated for fstab in /run/systemd/generator that manage the mount have an After=local-fs-pre.target which is too late. > > > > Other dependency errors appear in the log; all with the same root cause. By the time [ a specified service ] that uses /var is ready, the partition has not yet been mounted. My solution resolves the /var mount as soon as the block device is seen by udev - which made all the dependency errors go away. > > Fwiw, I can't reproduce the problem. systemd-journal-flush.service is > correctly started after /var has been mounted. > In case you are interested, I attached a journalctl dump, /etc/fstab > and systemd-analyze dump as well. > As you can see, systemd-journal-flush.service has a proper > After=var.mount ordering. > > I wonder if you have a dependency loop somewhere and systemd resolves > this by removing that ordering.
As mentioned earlier, I strongly suspect systemd-tmpfiles-setup.service - I had the same issue, because my /var/log partition is also not mounted in the initramfs for $reasons, so it appears late at boot. I'd suggest again to try and override it.
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel