On May 12, 2014, at 9:58 AM, Chris Murphy li...@colorremedies.com wrote:
On May 12, 2014, at 7:06 AM, Kirill Elagin kirela...@gmail.com wrote:
Could it be that all the boot ids are actually the same for some reason?
I had this issue in a container when systemd was reading boot_id from
On Thu, 15.05.14 12:01, Chris Murphy (li...@colorremedies.com) wrote:
On May 12, 2014, at 9:58 AM, Chris Murphy li...@colorremedies.com wrote:
On May 12, 2014, at 7:06 AM, Kirill Elagin kirela...@gmail.com wrote:
Could it be that all the boot ids are actually the same for some
On May 15, 2014, at 3:55 PM, Lennart Poettering lenn...@poettering.net wrote:
On Thu, 15.05.14 12:01, Chris Murphy (li...@colorremedies.com) wrote:
On May 12, 2014, at 9:58 AM, Chris Murphy li...@colorremedies.com wrote:
On May 12, 2014, at 7:06 AM, Kirill Elagin kirela...@gmail.com
On Thu, May 15, 2014 at 05:19:28PM -0600, Chris Murphy wrote:
On May 15, 2014, at 3:55 PM, Lennart Poettering lenn...@poettering.net
wrote:
On Thu, 15.05.14 12:01, Chris Murphy (li...@colorremedies.com) wrote:
On May 12, 2014, at 9:58 AM, Chris Murphy li...@colorremedies.com
Could it be that all the boot ids are actually the same for some reason?
I had this issue in a container when systemd was reading boot_id from
`/proc/sys/kernel/random/boot_id` and since /proc was bind-mounted, boot_id
always was host's boot_id.
You can also run `journalctl -F _BOOT_ID` to see a
On 12.05.2014 15:06, Kirill Elagin wrote:
Could it be that all the boot ids are actually the same for some reason?
I had this issue in a container when systemd was reading boot_id from
`/proc/sys/kernel/random/boot_id` and since /proc was bind-mounted, boot_id
always was host's boot_id.
You
On May 12, 2014, at 7:06 AM, Kirill Elagin kirela...@gmail.com wrote:
Could it be that all the boot ids are actually the same for some reason?
I had this issue in a container when systemd was reading boot_id from
`/proc/sys/kernel/random/boot_id` and since /proc was bind-mounted, boot_id
It looks like --list-boots is broken. I have have the same problem on Rawhide
with systemd-212-4.fc21.x86_64, which is a completely different VM. Here are
the last three items with --list-boots
-2 95117f702e4d43619072f87b20b2f31b Sat 2014-05-03 20:38:22 MDT—Sat
2014-05-03 20:47:17 MDT
Fedora 20, systemd-208-16.fc20.x86_64
I no longer have persistent journals written to disk. I've done at least two
dozen reboots today, yet journalctl --list-boots always reports the last
three entries as:
-2 43ba57a4decd4e2fb69bfd04493455c0 Mon 2014-04-14 14:43:38 MDT—Tue
2014-04-15
