On Sun, 2024-12-08 at 17:34 -0600, Roger Heflin wrote:
> So, full filesystem or read-only filesystem would seem to be the most likely.
Not full and not read-only, however it hasn't happened again in a few
weeks so I'm going to assume that some update has fixed whatever it
was.
Thanks.
poc
--
_
On Sun, 2024-12-08 at 23:20 +, Will McDonald wrote:
> On Sun, 8 Dec 2024 at 23:03, Patrick O'Callaghan
> wrote:
>
> > Dec 08 00:11:51 Bree logrotate[418079]: error: unable to open
> > /var/log/sssd/sssd_kcm.log-20241027 (read-only) for compression: Permission
> > denied
> >
>
>
> However:
logrotate as far I as I know runs as root, so selinux should not matter.
So, full filesystem or read-only filesystem would seem to be the most likely.
Corrupted filesystem/directory and/or directory that hit some odd fs
limitation (ext4 hashes files in a dir and when too many files hash
into a fu
On Sun, 8 Dec 2024 at 23:03, Patrick O'Callaghan
wrote:
> Dec 08 00:11:51 Bree logrotate[418079]: error: unable to open
> /var/log/sssd/sssd_kcm.log-20241027 (read-only) for compression: Permission
> denied
>
However:
>
> $ sudo ls -lZ /var/log/sssd/sssd_kcm.log-20241027
> -rw---. 1 root ro
$ systemctl status logrotate.service
× logrotate.service - Rotate log files
Loaded: loaded (/usr/lib/systemd/system/logrotate.service; static)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf, 50-keep-warm.conf
Active: failed (Result: exit-code) since Su
