Re: how to set correct time?
I installed ntpdate and can get the time when I query, but any time I
try to set the time I get the error
20 Apr 10:45:07 ntpdate[13883]: no server suitable for synchronization
found
Does anyone have any suggestions how to get this to work? Possibly
relevant facts: Debian woody, 2.4.2 kernel, iptables firewalling, my
system clock is set to local time (I dual boot with other OSs), and
I'm pretty sure my startup and shutdown routines sync with the
hardware clock. I was running as root, using a dialup connection.
Here's some terminal dialog:
wheat:/usr/local/rootlog# date ; ntpdate -q ntp.to.themasses.org
Fri Apr 20 10:25:48 PDT 2001
server 198.68.212.30, stratum 2, offset -322.386485, delay 0.19553
20 Apr 10:25:49 ntpdate[13744]: step time server 198.68.212.30 offset -322.386485 sec
wheat:/usr/local/rootlog# ntpdate -q ntp.ucsd.edu
server 132.239.254.5, stratum 2, offset -322.375984, delay 0.20555
20 Apr 10:26:30 ntpdate[13750]: step time server 132.239.254.5 offset -322.375984 sec
wheat:/usr/local/rootlog# ntpdate ntp.ucsd.edu ntp.to.themasses.org
20 Apr 10:29:32 ntpdate[13771]: no server suitable for synchronization found
wheat:/usr/local/rootlog# ntpdate -v
20 Apr 10:39:13 ntpdate[13840]: ntpdate 4.0.99g Wed Apr 4 18:01:13 MDT 2001 (1)
20 Apr 10:39:13 ntpdate[13840]: no servers can be used, exiting
wheat:/usr/local/rootlog# nslookup ntp.ucsd.edu
Server: dialcache110.ns.uu.net
Address: 198.6.1.70
Non-authoritative answer:
Name: bigmama.ucsd.edu
Addresses: 132.239.254.5, 132.239.254.205
Aliases: ntp.ucsd.edu
wheat:/usr/local/rootlog# ntpdate 132.239.254.5
20 Apr 10:41:44 ntpdate[13854]: no server suitable for synchronization found
wheat:/usr/local/rootlog# ntpdate 132.239.254.205
20 Apr 10:41:55 ntpdate[13868]: no server suitable for synchronization found
wheat:/usr/local/rootlog# ntpdate -d 132.239.254.205
20 Apr 10:42:02 ntpdate[13874]: ntpdate 4.0.99g Wed Apr 4 18:01:13 MDT 2001 (1)
transmit(132.239.254.205)
receive(132.239.254.205)
transmit(132.239.254.205)
receive(132.239.254.205)
transmit(132.239.254.205)
receive(132.239.254.205)
transmit(132.239.254.205)
receive(132.239.254.205)
transmit(132.239.254.205)
server 132.239.254.205, port 123
stratum 2, precision -24, leap 00, trust 000
refid [164.67.62.194], delay 0.20541, dispersion 0.00224
transmitted 4, in filter 4
reference time: be8aee2c.29608da5 Fri, Apr 20 2001 10:19:40.161
originate timestamp: be8af228.e1da69b1 Fri, Apr 20 2001 10:36:40.882
transmit timestamp: be8af36b.480639d5 Fri, Apr 20 2001 10:42:03.281
filter delay: 0.20935 0.20541 0.20549 0.21547
0.00000 0.00000 0.00000 0.00000
filter offset: -322.489 -322.487 -322.489 -322.494
0.000000 0.000000 0.000000 0.000000
delay 0.20541, dispersion 0.00224
offset -322.487437
20 Apr 10:42:03 ntpdate[13874]: step time server 132.239.254.205 offset -322.487437 sec
wheat:/usr/local/rootlog# ntpdate -t 10 132.239.254.205
20 Apr 10:45:07 ntpdate[13883]: no server suitable for synchronization found
wheat:/usr/local/rootlog# type ntpdate
ntpdate is hashed (/usr/sbin/ntpdate)
wheat:/usr/local/rootlog# whoami
root
On Thu, Apr 19, 2001 at 03:36:06PM -0800, Ethan Benson wrote:
> On Thu, Apr 19, 2001 at 11:58:02PM +0100, Rory Campbell-Lange wrote:
> > I foolishly don't know how to set the correct time for my system clock.
> > The timezone is correctly set to London/England, but the time is about 6
> > hours out (date reports the time in 'BST' - I presume this is "British
> > Standard Time").
> >
> > I tried using the date command but nothing happened.
>
> apt-get install ntpdate if you have network connectivity. you can
> have cron run it regularly if you leave your machine running for long
> periods, its not as precise as running full fledged ntpd but its
> sufficient for most purposes.
>
> if you don't have network connectivity you need to run as root:
>
> date 041902002001
>
> that would set the date to 4/19/2001 at 2:00. (time is in 24hr
> format). date --help shows the syntax.
>
> --
> Ethan Benson
> http://www.alaska.net/~erbenson/
Reply to: