What’s the issue here?
❯ systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● logrotate.service loaded failed failed Rotate log files
Legend: LOAD → Reflects whether the unit definition was properly loaded.
ACTIVE → The high-level unit activation state, i.e. generalization of SUB.
SUB → The low-level unit activation state, values depend on unit type.
1 loaded units listed.
~
❯ systemctl status logrotate.service
× logrotate.service - Rotate log files
Loaded: loaded (/usr/lib/systemd/system/logrotate.service; static)
Active: failed (Result: exit-code) since Fri 2024-11-29 12:24:13 CET; 3h 40min ago
Invocation: 720d52193b554360826f6298c5b6a88a
TriggeredBy: ● logrotate.timer
Docs: man:logrotate(8)
man:logrotate.conf(5)
Process: 5149 ExecStart=/usr/sbin/logrotate /etc/logrotate.conf (code=exited, status=1/FAILURE)
Main PID: 5149 (code=exited, status=1/FAILURE)
Mem peak: 1.9M
CPU: 38ms
lis 29 12:24:13 CachyOS systemd[1]: Starting Rotate log files...
lis 29 12:24:13 CachyOS logrotate[5149]: error: stat of /var/log/wtmp failed: Nie ma takiego pliku ani katalogu
lis 29 12:24:13 CachyOS systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE
lis 29 12:24:13 CachyOS systemd[1]: logrotate.service: Failed with result 'exit-code'.
lis 29 12:24:13 CachyOS systemd[1]: Failed to start Rotate log files.
~
❯ sudo systemctl restart logrotate.service
Job for logrotate.service failed because the control process exited with error code.
See "systemctl status logrotate.service" and "journalctl -xeu logrotate.service" for details.