LateNight

The E3C246D4U has a dedicated LAN port in addition to the two Intel ports. I've also added a 10G card.

Yes, I've had it that way since installing it.

Going in and saving again, without making changes, fixed the issue. No log entries overnight. Thank you.

Just went into settings again and saved (no changes). New parity.check.tuning.cron: # Generated schedules for parity.check.tuning 0 23 * * * /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null 0 7 * * * /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null */7 * * * * /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "monitor" &>/dev/null I'm guessing that fixed the issue - will check in the morning.

Log: Feb 8 23:04:02 DeathStar crond[2219]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null Feb 8 23:04:02 DeathStar crond[2219]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null Feb 8 23:19:01 DeathStar crond[2219]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null Feb 8 23:19:01 DeathStar crond[2219]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null Feb 8 23:34:01 DeathStar crond[2219]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null Feb 8 23:34:01 DeathStar crond[2219]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null Feb 8 23:48:02 DeathStar crond[2219]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null Feb 8 23:48:02 DeathStar crond[2219]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null Feb 9 00:03:02 DeathStar crond[2219]: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null parity.check.tuning.cron # Generated schedules for parity.check.tuning /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null */7 * * * * /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "monitor" &>/dev/null parity.tuning.cfg parityTuningIncrements="yes" parityTuningFrequency="daily" parityTuningResumeCustom="" parityTuningResumeHour="23" parityTuningResumeMinute="0" parityTuningPauseCustom="" parityTuningPauseHour="7" parityTuningPauseMinute="0" parityTuningUnscheduled="yes" parityTuningRecon="no" parityTuningClear="no" parityTuningNotify="no" parityTuningHeat="yes" parityTuningHeatHigh="2" parityTuningHeatLow="10" parityTuningHeatNotify="yes" parityTuningDebug="no" parityTuningHeatShutdown="yes" parityTuningHeatCritical="1" parity-checks.log parity.check.tuning.progress.save

Now showing every 15 minutes in my log: failed parsing crontab for user root: /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null Unraid Version: 6.8.3

Repeated messages in log, every seven minutes: crond[2212]: exit status 126 from user root /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "monitor" &>/dev/null

I've had Turbo disabled but decided to re-enable it again last night. Server crashed overnight. I wasn't running anything that should stress the server. ¯\_(ツ)_/¯

I have the following debug messages every five minutes in my log: I did verify that I have logging disabled. This started after the most recent update - 2020.10.23

Sorry, should have linked to the second response and not the thread. I was also having permission issues until I enabled the Set Permissions option. I did change the chown User to 99, and chown Group to 100 but it appears either works.

@unRAIDuser7 @TexasUnraid have you tried the "Set Permissions" option in Sonarr, as explained at:

Had this error occur overnight. I had added a headphones docker. Unfortunately, I turned off my syslog server and the logs weren't saved after reboot.

This is listed in the manual: Clear CMOS - 1 (short pin), but I don't see it in their diagram. Pulling the battery should work.

@JM2005 - he asked some clarifying questions, mostly about my BIOS settings, but no word today.