Maintenance ended; however, it did not exit cleanly (256)
I received an email from cPanel update noting that maintenance ended with errors. This is the second morning in a row that I've received this email.
In the update log preview, these errors were highlighted:
[2024-07-28 04:50:46 -0700] E [/usr/local/cpanel/scripts/rdate] Failed to run due to the 10 second timeout being exceeded.
[2024-07-28 04:50:46 -0700] E [/usr/local/cpanel/scripts/rdate] The “/usr/local/cpanel/scripts/rdate” command (process 81759) reported error number 4 when it ended.
...
[2024-07-28 04:52:51 -0700] E [/usr/local/cpanel/scripts/update-packages] The “/usr/local/cpanel/scripts/update-packages” command (process 81797) reported error number 1 when it ended.
I did review this post thoroughly
https://support.cpanel.net/hc/en-us/community/posts/22830191793943-The-usr-local-cpanel-scripts-rdate-command-reported-error-number-4-when-it-ended
After adding Google nameservers to my /etc/resolv.conf file, I saw the /usr/local/cpanel/scripts/rdate -p command complete successfully once, but I can't make the magic happen again.
I ran /scripts/upcp from the Terminal. The script reported that all updates had completed, but the email I received after running that has the same errors as I posted at the beginning.
My csf.conf file has the following ports listed
# Allow incoming TCP ports
TCP_IN = "20,21,22,25,37,53,80,110,143,443,465,587,993,995,2077,2078,2082,2083,2086,2087,2095,2096,7822"
# Allow outgoing TCP ports
TCP_OUT = "20,21,22,25,37,43,53,80,110,113,443,587,873,993,995,2086,2087,2089,2703,7822"
# Allow incoming UDP ports
UDP_IN = "20,21,53"
# Allow outgoing UDP ports
# To allow outgoing traceroute add 33434:33523 to this list
UDP_OUT = "20,21,53,113,123,873,6277"
# Allow incoming PING
ICMP_IN = "1"
In other words, port 37 is open, but its behavior is unreliable when it comes to processing this script. I'm really hoping to get help in resolving this issue. I've tried everything I can think of, and I am not a grizzled veteran when it comes to VPS server management.
Thank you in advance for any help that is offered.
-
Hey there! We maintain a time server, so as a test can you try this command?
telnet rdate.cpanel.net 37
The connection won't stay open for long, but as long as you get the "connected to rdate.cpanel.net - escape character" line, you're good.
Note: If you don't have telnet installed, you may need to run "yum install telnet" on the system first.
If that all works properly, that at least confirms outbound port 37 is open and you can use it.
0 -
Hello cPRex
No joy.
Using username "root".
root@[myip]'s password:
Access denied
root@[myip]'s password:
Last failed login: Mon Jul 29 15:09:04 PDT 2024 from 38.22.55.176 on ssh:notty
There was 1 failed login attempt since the last successful login.
Last login: Mon Jul 29 10:42:45 2024 from 38.22.55.176
[root@server1 ~]# telnet rdate.cpanel.net 37
Trying 208.74.121.36...
telnet: connect to address 208.74.121.36: Connection timed out
Trying 208.74.121.43...
^C
[root@server1 ~]# /usr/local/cpanel/scripts/rdate -p
Failed to run due to the 10 second timeout being exceeded.
[root@server1 ~]#0 -
Thanks for sharing that - that output indicates something outside of your server has changed as you aren't able to connect to our system over port 37. You'll have to speak with your hosting provider or datacenter to have them check things on their end since your server's firewall is already properly configured.
0
Please sign in to leave a comment.
Comments
3 comments