On Wednesday 30 November 2022, Bengt Gördén wrote:

On 2022-11-28 20:30, Fritz Hudnut wrote:

...

@Bengt:

I just ran that command in my Leap 15.5 install that is a month or more old and got one entry, because I have been lately booting from the Super Grub2 disk to get into it. Previously I log into each of my installs once a week, so there should have been more entries.

I think my problem needs to be reported to upstream of systemd/journalctl. After doing some more research, I've come to the conclusion that journalctl is a pretty crappy piece of software. How can a software that is so involved in debugging have so many bugs in it???

Anyway. If you have many files in /var/log/journal/*. Run journalctl --list-boots on all of them (individually). Ex. for i in `ls -1art system*`;do journalctl --file $i --list-boots;done

Also do this (beware that this can take some time) journalctl --verify

If you need alternate way to get an overview of past boots, I wrote a PyQt journal browser than can show a calendar view of past boots. The calendar is marked with a green dot for each boot, and a red dot for any shutdown that seems abnormal (where the journal seems truncated). See screenshots here: https://github.com/digitaltrails/jouno The calendar view takes about 30 seconds to initialise for about a 256 boots off an ssd (I shutdown my desktop each night and keep about a years worth of logs). I was actually looking for a way to watch/filter the journal and raise desktop alerts for things I was interested in (messages from things I'm working on, or from backups, or smartd, etc). But my curiosity grew a bit beyond that, so I added the Query->Calendar view. It's not widely used, it's stable enough on my desktop, but not sure how well it'd go on a busy server. Community build: https://software.opensuse.org/package/jouno Michael

I also found a bug that probably fits my problem. https://github.com/systemd/systemd/issues/6447