SOLVED Maintenance ended; however, it did not exit cleanly (256). ...“scripts/mainipcheck”

[jeffschips]

Another one of those errors that crop up now and again.

Ran /scripts/upcp but the error persists:

Processing: Checking for main IP changes
[2023-11-18 22:42:44 -0500] 39% complete
[2023-11-18 22:42:44 -0500] - Processing command `/usr/local/cpanel/scripts/mainipcheck`
[2023-11-18 22:43:14 -0500] E [/usr/local/cpanel/scripts/mainipcheck] Encountered an error while determining the main IP from the myip server (https://myip.cpanel.net/v1.0/):
[2023-11-18 22:43:14 -0500] E [/usr/local/cpanel/scripts/mainipcheck] 599 Internal Exception
[2023-11-18 22:43:14 -0500] E [/usr/local/cpanel/scripts/mainipcheck] The “/usr/local/cpanel/scripts/mainipcheck” command (process 2769766) reported error number 11 when it ended.
[2023-11-18 22:43:14 -0500] The Administrator will be notified to review this output when this script completes


/scripts/mainipcheck

Encountered an error while determining the main IP from the myip server (https://myip.cpanel.net/v1.0/):
599 Internal Exception

 

[jeffschips]

SOVLED:
some ip address in my cc_deny list was blocking something to do with /scripts/mainipcheck.

All of the ip ranges in my cc_deny are only from hacking attempts and other malicious activity so wonder why the inclusion of those deny entities would stop /scripts/mainipcheck from running successfully. . .?

 

[kodeslogic]

Glad you have it resolved

 

[pkiff]

I got this same error reported in the update log from 2023-11-19, but I don't have an y cc_deny entries in my CSF. I got the same "error number 11" and the same "599 Internal Exception" line in the log. I assume this is an issue with the cPanel myip.cpanel service, not with my config. Anyone know for sure?

 

[quietFinn]

Got that error in 2 servers, ran /scripts/upcp, no problems, so it was a temporary issue.

 

[pkiff]

Thanks @quietFinn. Re-ran /scripts/upcp on the server manually just now, and there were no errors in the mainipcheck this time. So I think you are right, it was a temporary issue.

 

[cPRex]

Good job collaborating! While I'm not seeing anything odd in our internal tracking from that time, it does seem like this was a temporary issue for everyone, so I'm glad things are working well now!

 

[jimlongo]

Confirmed: re-running this morning the error did not repeat itself.

 

[cPRex]

@jimlongo - glad to hear!