There is a problem with recent updates to openmediavault-scripts and logrotate service.
Scripts plugin creates directory /var/log/omv-scripts-exec-tracker with permissions 777 and logrotate doesn't like it 
On my system logrotate would then exit with error status.
Simple chmod like 640 on the directory fixes the problem
Also is it ok that logs of scripts plugin are in 2 places?
- in a file /var/log/omv-scripts-exec-tracker.log
- every execution as separate file in mentioned directory /var/log/omv-scripts-exec-tracker
I guess Web UI reads from the folder?
Code
/var/log/
drwxrwxrwx 2 root root 540 lip 1 07:04 omv-scripts-exec-tracker
-rw-rw-rw- 1 root root 584 lip 1 07:04 omv-scripts-exec-tracker.log
-rw-rw-rw- 1 root root 393 svi 31 10:45 omv-scripts-exec-tracker.log.1.gz
-rw-rw-rw- 1 root root 224 svi 30 10:25 omv-scripts-exec-tracker.log.2.gz
-rw-rw-rw- 1 root root 205 svi 30 08:42 omv-scripts-exec-tracker.log.3.gz
-rw-rw-rw- 1 root root 651 svi 29 20:52 omv-scripts-exec-tracker.log.4.gz
-rw-rw-rw- 1 root root 231 svi 26 13:56 omv-scripts-exec-tracker.log.5.gz
logrotate[125988]: error: skipping "/var/log/omv-scripts-exec-tracker/rsync_old_server.sh.20250527-141435.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.
svi 27 00:00:06 OMV systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE
svi 27 00:00:06 OMV systemd[1]: logrotate.service: Failed with result 'exit-code'.
svi 27 00:00:06 OMV systemd[1]: Failed to start logrotate.service - Rotate log files.