I was unable to reproduce a network time-out when testing from three different external locations; however, there are multiple possible reasons why this could occur. This could be either a temporary issue with the specific httpupdate/time server being connected to, a firewall configuration if one is used on the local system, or it could be localized to an upstream data center or network carrier.Server Time
rdate: timeout for rdate.cpanel.net
Down?
other sync URLs? where to config them?
# ping -vc10 rdate.cpanel.net
# traceroute -v rdate.cpanel.net
# dig rdate.cpanel.net +noall +answer
# man ntpd
# man ntp.conf
# ntpdate -v clock.isc.org
Do you have any firewall configurations in-place? It is possible that rdate may be unable to communicate via the required ports (e.g., destination port 37, for rdate, and destination port 123, for ntp).Hi
I am facing the similar error. However, I am able to ping and tracert your servers.
I don't have NTP installed. I don't have much technical expertise.
Can you tell me if I can manually change the time? Or how to solve this problem?
rdate: timeout for rdate.cpanel.net
# iptables -L -nv
# /etc/init.d/iptables save
# /etc/init.d/iptables stop
# /usr/sbin/csf -f
# rdate -s rdate.cpanel.net
# rdate -s -u rdate.cpanel.net
# ntpdate -v clock.isc.org
# /scripts/ensurerpm ntp
# /scripts/ensurepkg ntp
Via root SSH access, please let us know the output of the following command:
Code:# ping -vc10 rdate.cpanel.net # traceroute -v rdate.cpanel.net
[email protected] [~]# ping -vc10 rdate.cpanel.net
PING httpupdate.cpanel.net (208.74.121.37) 56(84) bytes of data.
64 bytes from httpupdate5.cpanel.net (208.74.121.37): icmp_seq=1 ttl=54 time=1.13 ms
64 bytes from httpupdate5.cpanel.net (208.74.121.37): icmp_seq=2 ttl=54 time=1.12 ms
64 bytes from httpupdate5.cpanel.net (208.74.121.37): icmp_seq=3 ttl=54 time=1.15 ms
64 bytes from httpupdate5.cpanel.net (208.74.121.37): icmp_seq=4 ttl=54 time=1.15 ms
64 bytes from httpupdate5.cpanel.net (208.74.121.37): icmp_seq=5 ttl=54 time=2.10 ms
64 bytes from httpupdate5.cpanel.net (208.74.121.37): icmp_seq=6 ttl=54 time=1.17 ms
64 bytes from httpupdate5.cpanel.net (208.74.121.37): icmp_seq=7 ttl=54 time=1.19 ms
64 bytes from httpupdate5.cpanel.net (208.74.121.37): icmp_seq=8 ttl=54 time=1.17 ms
64 bytes from httpupdate5.cpanel.net (208.74.121.37): icmp_seq=9 ttl=54 time=1.15 ms
64 bytes from httpupdate5.cpanel.net (208.74.121.37): icmp_seq=10 ttl=54 time=1.13 ms
--- httpupdate.cpanel.net ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 13044ms
rtt min/avg/max/mdev = 1.124/1.251/2.106/0.287 ms
Didn't try that as we want as few extra daemons running as possible.For potential alternatives (via IP addresses), the following command could be used:
I recommend using NTP via a customized NTP daemon ("ntpd") configuration so that a service will stay running to regulate the accuracy of the local system time. For details, I would suggest ensuring your system has the "ntp" package installed and then refer to official manual ("man") documentation pages using the following commands:Code:# dig rdate.cpanel.net +noall +answer
Code:# man ntpd # man ntp.conf
tried that, it DID update the system clock.. still we'd like the normal cPanel automated one to work again..If the software package "ntp" is installed here is an alternative to "rdate" that will work when the NTP daemon ("ntpd") is not yet enabled:
Code:# ntpdate -v clock.isc.org
[email protected] [~]# rdate -s -u rdate.cpanel.net
rdate: timeout for rdate.cpanel.net
[email protected] [~]# rdate -s -u 208.74.121.37
rdate: timeout for 208.74.121.37
NTPd should be very low on resource usage; I'm not aware of any significant load increase as a result of running ntpd to maintain accurate system time.Didn't try that as we want as few extra daemons running as possible.
The UDP option may not work as I first believed; however, the default TCP method should work without issue, as seen below:tried that, it DID update the system clock.. still we'd like the normal cPanel automated one to work again..
Code:[email protected] [~]# rdate -s -u rdate.cpanel.net rdate: timeout for rdate.cpanel.net [email protected] [~]# rdate -s -u 208.74.121.37 rdate: timeout for 208.74.121.37
# rdate -s rdate.cpanel.net
To further clarify, it is the TCP method that is used by cPanel, as seen in the following example entry in rc.local:For rdate, via TCP, destination port 37:
Code:# rdate -s rdate.cpanel.net
# grep rdate /etc/rc.d/rc.local
rdate -s rdate.cpanel.net&
Expanding upon the last message, when I tested the specific httpupdate mirror IP address I was able to display the retrieved date and time via the rdate option "-p" for print:NTPd should be very low on resource usage; I'm not aware of any significant load increase as a result of running ntpd to maintain accurate system time.
The UDP option may not work as I first believed; however, the default TCP method should work without issue, as seen below:
To further clarify, it is the TCP method that is used by cPanel, as seen in the following example entry in rc.local:Code:# rdate -s rdate.cpanel.net
Code:# grep rdate /etc/rc.d/rc.local rdate -s rdate.cpanel.net&
# rdate -p rdate.cpanel.net
rdate: [rdate.cpanel.net] Sat Mar 20 03:14:01 2010
# rdate -ps rdate.cpanel.net
rdate: [rdate.cpanel.net] Sat Mar 20 03:14:02 2010
# rdate -p 208.74.121.37
rdate: [208.74.121.37] Sat Mar 20 03:16:01 2010
# rdate -ps 208.74.121.37
rdate: [208.74.121.37] Sat Mar 20 03:16:03 2010
Thanks a lot, I had not added the INPUT rule! No it works great!>
iptables -A INPUT -p tcp --sport 37 -j ACCEPT
iptables -A OUTPUT -p tcp --dport 37 -j ACCEPT
[email protected] [~]# rdate -s rdate.cpanel.net
rdate: timeout for rdate.cpanel.net
[email protected] [~]# ping rdate.cpanel.net
PING httpupdate.cpanel.net (208.82.118.100) 56(84) bytes of data.
64 bytes from 208.82.118.100: icmp_seq=1 ttl=52 time=52.2 ms
64 bytes from 208.82.118.100: icmp_seq=2 ttl=52 time=52.5 ms
64 bytes from 208.82.118.100: icmp_seq=3 ttl=52 time=53.6 ms
64 bytes from 208.82.118.100: icmp_seq=4 ttl=52 time=52.9 ms
64 bytes from 208.82.118.100: icmp_seq=5 ttl=52 time=54.4 ms
64 bytes from 208.82.118.100: icmp_seq=6 ttl=52 time=52.4 ms
64 bytes from 208.82.118.100: icmp_seq=7 ttl=52 time=54.7 ms
64 bytes from 208.82.118.100: icmp_seq=8 ttl=52 time=52.5 ms
64 bytes from 208.82.118.100: icmp_seq=9 ttl=52 time=54.4 ms
64 bytes from 208.82.118.100: icmp_seq=10 ttl=52 time=53.0 ms
--- httpupdate.cpanel.net ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 13153ms
rtt min/avg/max/mdev = 52.275/53.307/54.771/0.890 ms