February 20, 20251 yr Hello this morning I was unable to access the UI, I had to manually shut down the server. So the diag is from after the reboot but I did get the messeges below via email. At 4:40am I received this msg /etc/cron.daily/fix.common.problems.sh: line 2: 2598178 Bus error /usr/local/emhttp/plugins/fix.common.problems/scripts/scan.php 2> /dev/null 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 /etc/cron.daily/tailscale-daily: line 3: 2598220 Bus error /usr/local/emhttp/plugins/tailscale/daily.php > /dev/null 2>&1 /etc/cron.daily/user.script.start.daily.sh: line 2: 2598240 Bus error /usr/local/emhttp/plugins/user.scripts/startSchedule.php daily At 4:47am I received this msg /etc/cron.hourly/user.script.start.hourly.sh: line 2: 2605358 Bus error /usr/local/emhttp/plugins/user.scripts/startSchedule.php hourly At 5:47am I received this msg /etc/cron.hourly/user.script.start.hourly.sh: line 2: 2666712 Bus error /usr/local/emhttp/plugins/user.scripts/startSchedule.php hourly plexserver-diagnostics-20250220-0614.zip Edited February 20, 20251 yr by fespinoza831 correction
February 20, 20251 yr Community Expert Solution 1 hour ago, fespinoza831 said: 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 For this see here: https://forums.unraid.net/bug-reports/stable-releases/potentially-dangerous-mode-on-unraid-api-r3625/#findComment-32621 But it's harmless, if the server continues crashing, enable the syslog server and post that after a crash.
February 20, 20251 yr Author I had already ran those commands in the comment but had not rebooted. I have enabled the Syslog Server.
February 23, 20251 yr Community Expert 18 hours ago, fespinoza831 said: any issues leaving Syslog Server enabled?. Assuming it's logging to a share it's fine, if it's logging to the flash, avoid leaving it running for too long.
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.