{"action":"opened","issue":{"url":"https://api.github.com/repos/systemd/systemd/issues/2009","labels_url":"https://api.github.com/repos/systemd/systemd/issues/2009/labels{/name}","comments_url":"https://api.github.com/repos/systemd/systemd/issues/2009/comments","events_url":"https://api.github.com/repos/systemd/systemd/issues/2009/events","html_url":"https://github.com/systemd/systemd/issues/2009","id":118485662,"number":2009,"title":"v218: journald default for Storage= causes strange behavior when /var/log/journal/ missing","user":{"login":"mpictor","id":671579,"avatar_url":"https://avatars.githubusercontent.com/u/671579?v=3","gravatar_id":"","url":"https://api.github.com/users/mpictor","html_url":"https://github.com/mpictor","followers_url":"https://api.github.com/users/mpictor/followers","following_url":"https://api.github.com/users/mpictor/following{/other_user}","gists_url":"https://api.github.com/users/mpictor/gists{/gist_id}","starred_url":"https://api.github.com/users/mpictor/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mpictor/subscriptions","organizations_url":"https://api.github.com/users/mpictor/orgs","repos_url":"https://api.github.com/users/mpictor/repos","events_url":"https://api.github.com/users/mpictor/events{/privacy}","received_events_url":"https://api.github.com/users/mpictor/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-11-23T22:16:36Z","updated_at":"2015-11-23T22:16:36Z","closed_at":null,"body":"Running Gentoo's systemd version 218.\r\n\r\nMy journald.conf has nothing uncommented, so it's using the defaults. I noticed strange behavior with various services; most noticeable was that systemd-networkd would _usually_ not bring up any interfaces.\r\n\r\nI suspected a race condition, as it\r\na) did work at some boots, and\r\nb) reliably worked if I ran `systemctl restart systemd-networkd` after logging in.\r\n\r\nEnabling debug output for systemd as a whole, or for systemd-networkd itself, provided me with no hints.\r\n\r\nFinally I noticed that `journalctl --list-boot` only showed the most recent boot. `/var/log/journal` didn't exist, so I created it. After rebooting, networkd worked. Repeated boots with and without `/var/log/journal` indicate that the absence of that directory seems to cause the behavior.\r\n\r\nIf a race condition is indeed involved, perhaps journald stops processing input until all filesystems have been mounted if it doesn't see /var/log/journal? If so, that could cause other services to hang because they couldn't write to stderr/stdout."}}