February 9, 20251 yr Recently my system has started producing errors from cron, warning: Potentially dangerous mode on unraid-api: 0666 error: Ignoring unraid-api because it is writable by group or others. error: found error in file unraid-api, skipping warning: Potentially dangerous mode on unraid-api.patch: 0666 error: Ignoring unraid-api.patch because it is writable by group or others. error: found error in file unraid-api.patch, skipping Looking in logrotate.d I can see that the permissions are set to world writable on unraid-api and unraid-api.patch ls -l /etc/logrotate.d/unraid-api* -rw-rw-rw- 1 root root 165 Feb 10 09:31 /etc/logrotate.d/unraid-api -rw-rw-rw- 1 root root 408 Feb 10 09:31 /etc/logrotate.d/unraid-api.patch If I correct the permissions of the files it still produces errors because unraid.api.patch is a patch file, not a logrotate config file. Removing the app, manually cleaning up and reinstalling does not make any difference. For now I have removed the patch file and fixed the permissions on '/etc/logrotate.d/unraid-api' and my system is running fine, at least as far as I can tell.
February 9, 20251 yr Author Of interest, this is the first day I saw an error from cron.daily occur and my system spontaneously rebooted last night. Coincidence? maybe. Just of interest.
February 10, 20251 yr Just came here looking for the same info. I used the Unraid Patch tool yesterday and it downloaded a patch 1.0.0 ( I am on 7.0.0) and, this morning, I get that error. Everything seems to be running and my server didn't reboot though.
February 12, 20251 yr +1 - Have this error since the 9th Feb, after an upgrade to 7.0 on the 8th. Interestingly, I initially upgraded from 6.1X to 7 and ran it for about a week without any issues. However, after I encountered a corrupted bz file, manually replaced it using the zipped release file, and then completed the upgrade again through the normal process, I’m now experiencing this error. It might be related or just a coincidence, but it’s certainly interesting.
February 19, 20251 yr I'm having the same issue since updating to 7.0. Every day at 4:40am I get the cron email due to the log rate failing: logrotate: ALERT - exited abnormally. Is there a fix for that?
February 20, 20251 yr Solution hey guys, the connect plugin's next release will fix this. sorry to keep yall hanging on such an annoying issue. we'll try to get it out for ya this week or early next week. Edit: just shipped the release. 🤞 Edited February 20, 20251 yr by pujitm
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.