PDA

View Full Version : rdate problem

nenad
14th March 2006, 01:16
Hi,

I have following problem:

rdate: couldn't connect to host 128.2.136.71: Connection refused
nenad
14th March 2006, 04:55
solution:

rdate -s 192.43.244.18

(192.43.244.18 is time.nist.gov)

If anyone need this, hardware clock can be synchronised using:

# Log in as root
# /sbin/hwclock -r
# /sbin/hwclock --adjust
# /sbin/hwclock --systohc

(source: http://www.troubleshooters.com/linux/settime.htm )
falko
14th March 2006, 10:35
128.2.136.71 seems to have stopped last week...:(
edge
15th March 2006, 09:44
here is an other one: 207.46.232.189
(time.windows.com) :D
till
15th March 2006, 09:52
here is an other one: 207.46.232.189
(time.windows.com) :D

One of the few compatible things :)

Windows time = Linux Time ;)
nenad
15th March 2006, 09:54
....
:) :) :)
todvard
16th March 2006, 10:52
use pool.ntp.org, its a pool of time servers, you will get forwarded to different time server on every query
benjami
12th April 2006, 20:15
Where I can change the rdate IP server configuration?

I receceive daily logchek errors: "rdate: couldn't connect", is rdate in some cron job?

Thanks :)
benjami
12th April 2006, 21:07
Where I can change the rdate IP server configuration?

I receceive daily logchek errors: "rdate: couldn't connect", is rdate in some cron job?

Yes, is a cron job but I've searched in php scripts and not in cron because I don't have seen the first line :eek:

$ sudo crontab -e

and edit the first line :rolleyes:

Sorry!
nenad
28th July 2006, 08:04
Debian Sarge 3.1

This is not working:

# servers to check. (Separate multiple servers with spaces.)
NTPSERVERS="pool.ntp.org"
#
# additional options for ntpdate
#NTPOPTIONS="-v"
#NTPOPTIONS="-u"


but this from command line is working:

server201:~# ntpdate -v pool.ntp.org
28 Jul 07:04:39 ntpdate[27216]: ntpdate 4.2.0a@1:4.2.0a+stable-2-r Fri Aug 26 10:30:13 UTC 2005 (1)
28 Jul 07:04:40 ntpdate[27216]: adjust time server 209.151.236.226 offset 0.015092 sec
server201:~#


Any help appreciated
falko
29th July 2006, 12:49
Did you try
/etc/init.d/ntpdate restart? This checks and corrects the time, if necessary.
nenad
29th July 2006, 12:55
Last login: Sat Jul 29 00:28:08 2006 from 192.168.123.100
server201:~# /etc/init.d/ntpdate restart
Running ntpdate to synchronize clock.
server201:~# ntpdate
29 Jul 11:54:42 ntpdate[16487]: no servers can be used, exiting
server201:~#
falko
30th July 2006, 14:55
You don't need to run ntpdate after /etc/init.d/ntpdate restart
/etc/init.d/ntpdate restart is sufficient. If it doesn't show an error, it's ok. You can check your time afterwards with date