Description of problem: Version-Release number of selected component (if applicable): systemd-197-1.fc18.1.x86_64 dracut-024-23.git20130118.fc18.x86_64 How reproducible: So far 100%. Steps to Reproduce: 1. dracut doesn't know the machine id (when a non-host-only dracut initramfs is used) 2. dracut uses a temporary machine id Feb 01 01:55:43 localhost systemd[1]: systemd 197 running in system mode. (+PAM +LIBWRAP +A Feb 01 01:55:43 localhost systemd[1]: Running in initial RAM disk. Feb 01 01:55:43 localhost systemd[1]: No hostname configured. Feb 01 01:55:43 localhost systemd[1]: Set hostname to <localhost>. Feb 01 01:55:43 localhost systemd[1]: Initializing machine ID from random generator. 3. journald logs using this temporary machine ID 4. normal filesystem is mounted and journald is restarted Feb 01 01:57:10 bupkis systemd-journal[615]: Allowing runtime journal files to grow to 1.5G Feb 01 01:57:10 bupkis systemd-journald[149]: Received SIGTERM 5. new journald uses the normal machine ID 6. I end up with two journals: /run/log/journal/542b6b5b49aa4f2e9c5a1fbd1b7d7b3c/system.journal /run/log/journal/5557a6a3376545109a6ef12d3bf073d1/system.journal 7. journalctl -b only shows the second one It is possible to see the early messages with 'journalctl -D...', but this is non-obvious. I'm putting this under systemd, since I don't think that there's much that dracut can do about this.
I suggest to use by default: # journalctl -mb and spread the word about it.
Fixed in git, by Zbigniew.
systemd-201-2.fc18.1 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/systemd-201-2.fc18.1
Package systemd-201-2.fc18.2: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.2' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.2 then log in and leave karma (feedback).
Package systemd-201-2.fc18.4: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.4' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.4 then log in and leave karma (feedback).
Package systemd-201-2.fc18.5: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.5' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.5 then log in and leave karma (feedback).
systemd-201-2.fc18.6 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.6
Package systemd-201-2.fc18.6: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.6 then log in and leave karma (feedback).
systemd-201-2.fc18.6 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.