Samus1210

This issue is still happening, and continuously only happens after the parity check ends

I am very rudimentary when it comes to my server and do not believe I attempted the mentioned patch but I did review my scripts/patches etc from the past and didn't uncover anything erroneous.

Hello, I applied the update and waited until it happened again. I have uploaded the new diagnostics

Hello, I have been receiving the following 2 error messages after I fixed a few other issues on my server. They are as follows: 1) crond[1480]: exit status 255 from user root php /usr/local/emhttp/plugins/community.applications/scripts/notices.php > /dev/null > 2 81 2)exit status 255 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null I have been getting the second one consistently. I saw a similar issue in the following topic: I followed some of the tips mentioned there like checking pending plugins, reviewing the go script, and running phpdbg. I didnt seem to have the same problem. I dont see the if ( ! ((date("i") * date("H") * 60 + date("i")) line in my monitor script. I dont believe I have changed any code on the default scripts but the previous forums suggest that is the main cause. Looking for some assistance to see how to proceed forward and fix this issue. --updated diagnostics--

Thank you for the information! I plan to upgrade to a better setup soon but this has helped for now.

I have been wracking my brain for weeks trying to figure out what to do. My server constantly shut down/ freezes or restarts after a parity check is completed. There were other issues that I resolved based on solutions from other posts. This seems to be the last thing that is causing issues. Based on the logs it looks like the parity check finished around 5:10am or 5:11 and the restart happened around 5:12. It's crazy to me to think the parity check is the only thing keep my server in an "awake" or constant up state. ---removed logs due to receiving solution--