Systemd-journald "failed to set ACL on..."

TrueNAS General
, ,
1

Hello

I found a thread on this issue on the old forum but it seemed to be unresolved, apologies if I’m duplicating an issue.

On my shiny new Dragonfish installation (not upgraded from CORE or previous version of SCALE) I get this sequence of messages my dmesg a fair amount:
[275432.770478] systemd-journald[793]: Data hash table of /var/log/journal/7a9e7726e8fe401ea6a0777582909d4f/system.journal has a fill level at 75.0 (8534 of 11377 items, 6553600 file size, 767 bytes per hash table item), suggesting rotation. [275432.774677] systemd-journald[793]: /var/log/journal/7a9e7726e8fe401ea6a0777582909d4f/system.journal: Journal header limits reached or header out-of-date, rotating. [275432.855557] systemd-journald[793]: Failed to set ACL on /var/log/journal/7a9e7726e8fe401ea6a0777582909d4f/user-3000.journal, ignoring: Operation not supported

It seems to be triggered whenever the system.journal is rotated

uid 3000 is the only user on the box and is used for time machine SMB connections.

The prior thread on the old forum indicated it was a cosmetic issue that started around the time Cobia was introduced and not to worry about it, but since it’s still there after Dragonfish, I figured I would check in.

The boot-pool has aclmode set to discard, which I understand is by design, I’m just curious if there’s a way to tell systemd-journald not to try to set the ACL at creation/rotation?

System info:
Zimacube i5-1235U, 256 GB SSD boot, 4x18TB X20 drives Raidz1 for data. Only one user configured other than root and admin.

2

This is addressed in the next update. It is a benign error message, but if you really must make it go away you can just set the acltype on the logs dataset to posixacl.

3

this issue was supposed to be fixed in 24.04.1 but it didn’t for me and i have 24.04.2 but still getting this

4

I was wrong about it getting into 24.04.2. It is in master and stable/dragonfish (e.g. next DF release). It’s fairly trivial to just set posixacl on the logs dataset.

zfs get name /var/log # get dataset name for logs path
zfs set acltype=posixacl <dataset name>
5

That seems to have done the job. thanks

The log is filled with the below. Does that seem right?

11377 items, 6553600 file size, 768 bytes per hash table item), suggesting rotation.
Aug 20 10:26:11 nas systemd-journald[647]: /var/log/journal/d7f7614ae8894a0e80dadfcb72bf2018/system.journal: Journal header limits reached or header out-of-date, rotating.
Aug 20 10:40:11 nas systemd-journald[647]: Data hash table of /var/log/journal/d7f7614ae8894a0e80dadfcb72bf2018/system.journal has a fill level at 75.0 (8534 of 11377 items, 6553600 file size, 767 bytes per hash table item), suggesting rotation.
Aug 20 10:40:11 nas systemd-journald[647]: /var/log/journal/d7f7614ae8894a0e80dadfcb72bf2018/system.journal: Journal header limits reached or header out-of-date, rotating.
Aug 20 10:44:55 nas systemd-journald[647]: Data hash table of /var/log/journal/d7f7614ae8894a0e80dadfcb72bf2018/system.journal has a fill level at 75.0 (8534 of 11377 items, 6553600 file size, 767 bytes per hash table item), suggesting rotation.
Aug 20 10:44:55 nas systemd-journald[647]: /var/log/journal/d7f7614ae8894a0e80dadfcb72bf2018/system.journal: Journal header limits reached or header out-of-date, rotating.