Description of problem: "journalctl --list-boots" does not list all boot IDs, including the current boot ID. "journalctl -b" correctly shows the current boot log: -- Logs begin at Thu 2013-07-04 21:17:09 PDT, end at Thu 2014-05-08 15:43:07 PDT. -- May 07 21:39:09 XXX systemd-journal[94]: Runtime journal is using 8.0M (max allowed 196.7M, trying to leave 295.0M free of 1.9 # cat /proc/sys/kernel/random/boot_id 56736d55-cc9f-4783-9678-b3ff6f838aa3 However, "journalctl --list-boots" shows only 5 old logs, excluding the current one: -4 4f8ea7eaf576422abeabbcf6bd01a482 Sat 2013-12-14 19:31:36 PST—Fri 2013-12-27 15:18:41 PST -3 8b3e482a56c04128902b3bc627221865 Fri 2013-12-27 15:19:19 PST—Fri 2013-12-27 15:19:57 PST -2 a39ac4caa1a84de9be632afe48d79021 Fri 2013-12-27 16:31:39 PST—Fri 2013-12-27 18:12:15 PST -1 42672184a2d7485ea7288c250f6d2dee Fri 2013-12-27 18:12:52 PST—Tue 2013-12-31 11:52:54 PST 0 f01d1296bf2340ea82a7ee6e84225940 Tue 2013-12-31 12:06:28 PST—Tue 2013-12-31 12:10:07 PST "journalctl -F __BOOT_ID" lists 41 different boot IDs (including the current one). The missing boot IDs are still accessible using "journalctl _BOOT_ID=<id>". Version-Release number of selected component (if applicable): systemd-208-16.fc20.x86_64 How reproducible: This always happens on only 1 out of 6 systems running F20. Steps to Reproduce: 1. Run "journalctl --list-boots" 2. 3. Actual results: List all available boot logs Expected results: List only a few boot logs Additional info: # ls -l /var/log/journal/*/system* -rw-r-----+ 1 root systemd-journal 100663296 May 7 20:37 /var/log/journal/885e1d53804041c6a2e8a59e6f4b197c/system~ -rw-r-----+ 1 root systemd-journal 58720256 Dec 31 12:07 /var/log/journal/885e1d53804041c6a2e8a59e6f4b197c/system -rw-r-----+ 1 root systemd-journal 16777216 May 8 16:03 /var/log/journal/885e1d53804041c6a2e8a59e6f4b197c/system.journal # journalctl --verify 30f8858: unused data (entry_offset==0)█████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 47% PASS: /var/log/journal/885e1d53804041c6a2e8a59e6f4b197c/system PASS: /var/log/journal/885e1d53804041c6a2e8a59e6f4b197c/system.journal [...] 38fce0: unused data (entry_offset==0)░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 1% PASS: /var/log/journal/885e1d53804041c6a2e8a59e6f4b197c/system~
I'm having the same issue with systemd-208-21.fc20.x86_64. `journalctl --list-boots` gives 47 items: ... -2 5c4812a78758497b828100b3ef2672e2 Sat 2014-07-19 09:04:07 EEST—Sat 2014-07-19 19:13:26 EEST -1 0afd12dc0e164d25992306c7da580ce8 Sat 2014-07-19 19:13:43 EEST—Fri 2014-07-25 17:16:08 EEST 0 369759cb1e234ebe8f2da06634a5fca4 Fri 2014-07-25 17:16:25 EEST—Wed 2014-07-30 21:29:08 EEST while `journalctl -F _BOOT_ID` gives 91 items and as you can notice, there are no boots recorded for August even if I rebooted a couple of times.
initscripts-9.56.1-1.fc21, systemd-216-3.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/initscripts-9.56.1-1.fc21,systemd-216-3.fc21
Package initscripts-9.56.1-1.fc21, systemd-216-3.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing initscripts-9.56.1-1.fc21 systemd-216-3.fc21' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-12688/initscripts-9.56.1-1.fc21,systemd-216-3.fc21 then log in and leave karma (feedback).
Package systemd-216-4.fc21, initscripts-9.56.1-2.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-216-4.fc21 initscripts-9.56.1-2.fc21' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-12688/initscripts-9.56.1-2.fc21,systemd-216-4.fc21 then log in and leave karma (feedback).
Package initscripts-9.56.1-2.fc21, systemd-216-5.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing initscripts-9.56.1-2.fc21 systemd-216-5.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-12688/initscripts-9.56.1-2.fc21,systemd-216-5.fc21 then log in and leave karma (feedback).
systemd-208-25.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/systemd-208-25.fc20
initscripts-9.56.1-2.fc21, systemd-216-5.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
systemd-208-26.fc20,kmod-15-2.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/systemd-208-26.fc20,kmod-15-2.fc20
systemd-208-25.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
systemd-208-26.fc20, kmod-15-2.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
This problem appears to have been reintroduced in F22. Should this BZ be reopened or a new one created? On my F22 system, recently upgraded from F21. -4 69ffd60eab5d4724a2f80c66ad6e6ff5 Thu 2015-03-26 08:26:10 CST—Thu 2015-04-02 0 -3 fc2edbbbf1194af3b710f654a5f94618 Thu 2015-04-02 08:27:06 CST—Sun 2015-04-05 1 -2 d23797f203454dcabb6513fd62142477 Fri 2015-05-15 09:44:40 CST—Mon 2015-05-18 1 -1 6720637454a64a4b9374a6a359d3e51d Mon 2015-05-18 10:34:52 CST—Tue 2015-05-19 0 0 029735aa965b4f82aa77b89e9cefa1da Tue 2015-05-19 07:47:16 CST—Wed 2015-05-20 0 But I have booted many times since 2015-05-19 and yet I do find previous boots like so.... [root@meimei ~]# journalctl -b -3 | more -- Logs begin at Sun 2013-08-18 10:45:50 CST, end at Thu 2015-06-18 17:16:31 CST. Jun 16 09:46:48 meimei systemd-journal[124]: Runtime journal is using 8.0M (max allowed 398.6M, trying to leave 598.0M free of 3.8G available → current limit 398.6M). Jun 16 09:46:48 meimei systemd-journal[124]: Runtime journal is using 8.0M (max allowed 398.6M, trying to leave 598.0M free of 3.8G available → current limit 398.6M). Jun 16 09:46:48 meimei kernel: CPU0 microcode updated early to revision 0x7, date