Journalctl does not find journal files

General system Newbie
21

The code block?

With markdown:

```
some code

```

22

thanks you so much :+1:

1 Like
23

Have you already tried to both remove files and restart service, and then reboot?

24

Yes. But it doesn’t help.

25

I’m out of ideas for now :sweat_smile:

Let’s see:

sudo dmesg --level=err,warn
26 
$ sudo dmesg --level=err,warn
[    0.204986]   #2
[    0.206011]   #3
[    0.207013]   #4
[    0.208010]   #5
[    0.210000]   #6
[    0.211035]   #7
[    0.212013]   #8
[    0.213010]   #9
[    0.215009]  #10
[    0.216013]  #11
[    0.534843]  PPR X2APIC NX GT IA GA PC GA_vAPIC
[    1.401728] ata2.00: NCQ Send/Recv Log not supported
[    1.485078] ata2.00: NCQ Send/Recv Log not supported
[    2.268905] ata4.00: supports DRM functions and may not be fully accessible
[    2.269471] ata4.00: NCQ Send/Recv Log not supported
[    2.270763] ata4.00: supports DRM functions and may not be fully accessible
[    2.271093] ata4.00: NCQ Send/Recv Log not supported
[    3.051699] ata6.00: supports DRM functions and may not be fully accessible
[    3.055037] ata6.00: supports DRM functions and may not be fully accessible
[    4.133244] sp5100-tco sp5100-tco: Watchdog hardware is disabled
[    4.137746] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)
[    5.370008] amdgpu 0000:2d:00.0: amdgpu: SMU driver if version not matched
[    5.430123] usb 3-1: 3:1: cannot get freq at ep 0x86
[    5.502914] usb 3-1: 3:2: cannot get freq at ep 0x86
[    5.582657] usb 3-1: 3:3: cannot get freq at ep 0x86
[    6.091512] usb 3-1: Warning! Unlikely big volume range (=3896), cval->res is probably wrong.
[    6.091516] usb 3-1: [7] FU [Mic Capture Volume] ch = 1, val = 200/4096/1
[    6.734045] kauditd_printk_skb: 226 callbacks suppressed
[   12.944355] kauditd_printk_skb: 13 callbacks suppressed
[   20.484823] kauditd_printk_skb: 16 callbacks suppressed
[   26.216765] kauditd_printk_skb: 1 callbacks suppressed
1 Like
27

Is there something you are leaving out like a power loss while system was running, a power loss while system was updating?

1 Like
28

Radiation interference during alien invasion? :flying_saucer:
:upside_down_face:

P.S. Wouldn’t hurt to try full update again, just in case

sudo pacman -Syu
29

I do have some other problems - I was hoping to be able to fix them by being able to access the journal…
For example, I have problems with bluetooth audio and my shutdown sometimes takes ages while displaying No irq handler for vector. I once did a reset while this message was showing, because I was in a bit of a hurry. After restarting the journal, I noticed, that I sometimes get the message, that /tmp can’t be unmounted.

30

I tried deleting the logs, then restart the service, and then do the update. No changes.

1 Like
31

I had the same problem, trying to remember what I did to fix, the journals are not persisting, if I remember I will post back…

1 Like
32

OK think it was… Edit /etc/systemd/journald.conf
Change (it may be hashed out) or add:

[Journal]
Storage=persistent

Around line 14 for me.

33

This also gives the same result, still no journal files found.

34

Did you restart the service or reboot?

35

Multiple times in multiple combinations.

36

If I set Storage to volatile, the log works after a reboot. However, this is not a real solution for me, since I don’t want the log to be volatile.

37

What filesystem are you using?

38

ext4

39 
sudo mv /var/log/journal /var/log/journal-old
sudo systemd-tmpfiles --create --prefix /var/log/journal

Change back to persistent. Reboot and see if that does it.

This was a while ago for me so the above is from my history file :smiley:

40

No, doesn’t work.