[systemd-bugs] [Bug 90268] New: (tmpfiles, journald) systemd 219-6 + linux 4.0.1-1 = journal failing to append on boot

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=90268

            Bug ID: 90268
           Summary: (tmpfiles,journald) systemd 219-6 + linux 4.0.1-1 =
                    journal failing to append on boot
           Product: systemd
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: general
          Assignee: systemd-bugs at lists.freedesktop.org
          Reporter: brent.saner at gmail.com
        QA Contact: systemd-bugs at lists.freedesktop.org

in some cases (i can't seem to narrow down which yet), systemd fails to create
/run/log/journal. This then causes further failure of journald to fail to both:

-append to the volatile journal
-append to the persistent journal (if one exists)- no flushes, as the volatile
journal is not appended

from what i understand, the volatile journal does not exist because it normally
is written to /run/log/journal. on boot, the entries of /run/log/journal are
copied over to the persistent journal in /var/log/journal/ (if persistence is
enabled) (is this correct?).

this is occurring on fully updated/patched Arch Linux, x86_64.
this behaviour does not exist on kernel 3.19.3.

of three machines with systemd, i note the following:

machineA (desktop): does not create /run/log/journal; no new journal entries
are created.

machineB (laptop): does not create /run/log/journal; HOWEVER, new journal
entries SEEM to be appended/created.

machineC (firewall box): /run/log/journal IS created; new journal entries are
added.

machineA and machineB share the exact same /etc/systemd/journald.conf (with no
syslog):
[bts at workhorse systemd]$ egrep -Ev '^[[:space:]]*(#|$)' journald.conf 
[Journal]
Storage=persistent
Compress=yes
SystemMaxUse=100M
SystemMaxFileSize=20M


machineC, however, uses no persistence and uses a purely volatile journal (with
syslog):
[root at comptroller systemd]# egrep -Ev '^[[:space:]]*(#|$)' journald.conf 
[Journal]
Storage=volatile
Seal=no
SystemMaxUse=50M
RuntimeMaxUse=50M
ForwardToSyslog=yes


as a temporary workaround, it seems that "systemctl restart systemd-journald"
on the affected machine (machineA) seems to allow new journal entries. however,
/run/log/journal is still not created during the restart.


let me know what logs/output/etc. you wish to see.


(cross-linking for reference: https://bugs.archlinux.org/task/44799 )

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20150501/966f814a/attachment.html>