-
Bug
-
Resolution: Unresolved
-
Major
-
rhel-10.0.beta
-
sssd-2.10.0~beta2-2.el10
-
Yes
-
Low
-
rhel-sst-idm-sssd
-
ssg_idm
-
23
-
25
-
3
-
False
-
-
None
-
Red Hat Enterprise Linux
-
None
-
Pass
-
None
-
None
What were you trying to do that didn't work?
The logrotate.service fails to start:
Jul 28 00:39:55 mana10test107240539-vm1 logrotate[129426]: error: skipping "/var/log/sssd/*.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
Jul 28 00:39:55 mana10test107240539-vm1 systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE
- ll -d /var/log/sssd
drwxrwx---. 2 sssd sssd 6 Jun 25 20:00 /var/log/sssd
- In previous version(sssd-client-2.9.4-6.el10.x86_64) there's no such issue:
drwxr-x---. 2 sssd sssd 6 Feb 21 19:00 /var/log/sssd
Please provide the package NVR for which bug is seen:
sssd-client-2.10.0~beta2-1.el10.x86_64
How reproducible:
Always
Steps to reproduce
- Prepare a VM on Azure(or other platforms. it should be a general issue)
- systemctl status logrotate.service
Expected results
logrotate.service should be running
Actual results
logrotate.service failed to start.
- is duplicated by
-
RHEL-51877 logrotate fails due to world writable permissions in sssd logs
- Closed
- links to
-
RHBA-2024:135948 sssd bug fix and enhancement update