Re: Logrotate failing

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 full bucket this happens--not sure what other fses have for
similar issues).

I would check dmesg as there should be something in dmesg if something
of this sort happened.

On Sun, Dec 8, 2024 at 5:20 PM Will McDonald <wmcdonald@xxxxxxxxx> wrote:
>
> On Sun, 8 Dec 2024 at 23:03, Patrick O'Callaghan <pocallaghan@xxxxxxxxx> 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 root system_u:object_r:sssd_var_log_t:s0 2441 Oct 27 00:00 /var/log/sssd/sssd_kcm.log-20241027
>
>
> Is this logrotate trying to compress the pre-existing /var/log/sssd/sssd_kcm.log-20241027
>
> Or logrotate trying to copytruncate (or whatever) /var/log/sssd/sssd_kcm.log to /var/log/sssd/sssd_kcm.log-20241027?
>
> Things I'd probably check:
> 1. The permissions, selinux context, and extended attributes (lsattr) of the intervening directories to the file /var/log/sssd/, /var/log/, /var/
> 2. df -k /var, /var/log (and maybe even /var/log/sssd, although it's wildly unlikely that's a separate mount point?)
>
> "(read-only) for compression: Permission denied" definitely looks permission-y but that could equally be a filled filesystem or something else along the path?
>
> Can you do a manual logrotate and reproduce? If so, can you strace that to see where it's failing?
>
> --
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
-- 
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux