Exit status 255 issue

[Samus1210]

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--

 

 

Edited July 22 by Samus1210

[Squid]

Can you go to Tools, PHP Settings, and instead of default, set the logging to be "All Categories"

 

After applying, after the next exit 255 upload a new set of diagnostics

[MAM59]

The 255 from the monitor script usually comes from unofficial patches, usually done in your go file. There once was a "fix" to move logfiles from dockers and vm via symlinks somewhere, but it does not work with current versions anymore.

Remove anything that does patch the monitor script from your go file, reboot and you are done.

[Samus1210]

21 hours ago, Squid said:

Can you go to Tools, PHP Settings, and instead of default, set the logging to be "All Categories"

 

After applying, after the next exit 255 upload a new set of diagnostics

Hello,

 

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

[Samus1210]

21 hours ago, MAM59 said:

The 255 from the monitor script usually comes from unofficial patches, usually done in your go file. There once was a "fix" to move logfiles from dockers and vm via symlinks somewhere, but it does not work with current versions anymore.

Remove anything that does patch the monitor script from your go file, reboot and you are done.

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.

[MAM59]

1 hour ago, Samus1210 said:

but I did review my scripts/patches etc from the past

What I've meant that you should look into your /boot/config/go file and look for lines with sed commands

for an example look at

This "backup docker advice" told you to add lines to the go files. These do not work anymore today. So take a look and if they are there, delete them.

 

[Squid]

1 hour ago, MAM59 said:

What I've meant that you should look into your /boot/config/go file and look for lines with sed commands

for an example look at

This "backup docker advice" told you to add lines to the go files. These do not work anymore today. So take a look and if they are there, delete them.

 

The previously posted diagnostics show no additional lines in the go file

[Samus1210]

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