February 20, 20215 yr Hi all, I got the error in the topic's title from Fix Common Errors. Can you help me figure out how to fix it, please? Please find attached the diagnostics. tower-diagnostics-20210220-1947.zip
February 20, 20215 yr 1. Reboot 2. Make a change, any change under Settings - Scheduler - Parity Tuning and apply it. That'll clean up the logs quite a bit 3. Wait to see if it fills up again nginx decided to stop (possibly out of memory?) Hard to tell why...
February 20, 20215 yr Author Will do, thanks. I think I should remove Parity tuner since I don't have a parity disk anymore. What do you think?
February 20, 20215 yr 13 minutes ago, FabrizioMaurizio said: Will do, thanks. I think I should remove Parity tuner since I don't have a parity disk anymore. What do you think? Probably not much point in having it installed if you do not have a parity disk (although it can still be active if you ever run read checks).
February 20, 20215 yr Author 9 minutes ago, itimpi said: Probably not much point in having it installed if you do not have a parity disk (although it can still be active if you ever run read checks). I do run read checks once a month. The pause and resume feature is quite useful to me, not sure if that's a parity tuner feature or unraid's.
February 20, 20215 yr 6 minutes ago, FabrizioMaurizio said: I do run read checks once a month. The pause and resume feature is quite useful to me, not sure if that's a parity tuner feature or unraid's. Automated pause/resume is the plugin. Standard unRaid only supports manual pause/resume.
Archived
This topic is now archived and is closed to further replies.