For some reason the first time systemd-journald-flush is executed during boot, it logs a warning about files with insufficient privileges. However as soon as the system is booted to where I can login I'm able to run the service manually and it runs fine, flushing everything to disk and all journals, and user level journals are accessible. /var/log/journal is on the primary partition so it seems odd there would be some sort of race condition. I didn't see a way to output which files specifically had insufficient privileges. On Fri, 2024-07-26 at 09:59 -0400, Gregory Gincley wrote: > > To whom it may concern: > > I'm receiving the below error on every systemd-journald service > startup. > > While systemd-journald starts, it refuses to log to persistent > storage > (/var/log/journal) despite this path existing. Additionally --user > shows no journal information. > > I've tried deleting/recreating /var/log/journal > > I've tried setting /etc/systemd/journald.conf 'Storage' setting to > both > 'auto' and 'peristent' with the same result. > > https://github.com/systemd/systemd/blob/eef4cd51f94d837bd0e71512c831634a2902522d/src/journal/journald-server.c#L2764 > > FWIW I'm on Arch Linux. > > Any thoughts on what is preventing my logging from flushing to disk? > > Let me know if any additional information would be helpful. > > Thanks, > Greg