Am Fr., 30. Apr. 2021 um 20:27 Uhr schrieb Rick Winscot <rick.winscot@xxxxxxxxx>: > 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.
Attachment:
fstab
Description: Binary data
Attachment:
journal.txt.gz
Description: application/gzip
Attachment:
systemd-analyze.dump.txt.gz
Description: application/gzip
_______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel
