Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

[TCPware V5.8-2 w/ ECOs] NTP doesn't work on my Itanic

16 views
Skip to first unread message

Peter 'EPLAN' LANGSTOeGER

unread,
Apr 27, 2009, 6:26:56 PM4/27/09
to
Recently I found time to play with my Itanic and noticed, that NTP is not
working (and TIMED was synching the time).

The NTP config is very simple (I had an identical version running on my
Alpha, but switched it later - to use the Alpha as a server for the Itanic)
but NTP doesn't start to synch (TIMED was supposed to run a FIXED_MASTER,
but was acting as a client - I had the TIMED running as FIXED_MASTER on
my Alpha as well - and so I switched TIMED totally off on the Itanic) and
without time synching my ZX6000 is running much faster (gaining seconds
in minutes!!) and I'm getting frustrated already...


In NTPSERVER.LOG is nothing of interest (NTP tells that it started and
uses the NTP.CONF)

Does anyone have also problems with TCPware NTP (on OpenVMS I64 V8.3-1H1)?

How to debug such a problem?

Many TIA

--
Peter "EPLAN" LANGST�GER
Network and OpenVMS system specialist
E-mail Pe...@LANGSTOeGER.at
A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist

Peter 'EPLAN' LANGSTOeGER

unread,
Apr 28, 2009, 11:32:57 AM4/28/09
to
In article <49f64d50$1...@news.langstoeger.at>, pe...@langstoeger.at (Peter 'EPLAN' LANGSTOeGER) writes:
>Recently I found time to play with my Itanic and noticed, that NTP is not
>working (and TIMED was synching the time).

(Until I stopped it) TIMED did set the time about 48sec back every 4min!!
It is very frustrating, that my zx6000 (hardware?)clock is that way off...

>The NTP config is very simple

$ ty tcpware:ntp.conf
server 62.116.5.124 prefer
server 193.81.13.2
peer 192.168.1.4

but changing/simplifying it did also not help

$ ty tcpware:ntp.conf
server 192.168.1.4

>In NTPSERVER.LOG is nothing of interest (NTP tells that it started and
>uses the NTP.CONF)

TCPWARE:NTPSERVER.LOG
...
$ NTPD :== $TCPWARE_COMMON:[TCPWARE]NTPD.EXE
$!
$! Start the Server
$!
$ NTPD
28-APR-2009 17:03:48.23 NTP release v4.2 (rev 1.0).
28-APR-2009 17:03:48.26 Sanity value (WAYTOOBIG/PANIC) defaulted to 4000
28-APR-2009 17:03:48.29 precision = 1200.000 usec
28-APR-2009 17:03:48.35 Listening on interface wildcard, 0.0.0.0#123
28-APR-2009 17:03:48.37 Listening on interface LL0, 192.168.1.5#123
28-APR-2009 17:03:48.39 Listening on interface LO0, 127.0.0.1#123
28-APR-2009 17:03:48.42 Using NTP configuration file: TCPWARE:ntp.conf.

and nothing else

Only hint I got, is that sometimes "precision = 1200.000 usec"
and sometimes "precision = 1000.000 usec"...

>Does anyone have also problems with TCPware NTP (on OpenVMS I64 V8.3-1H1)?
>
>How to debug such a problem?

I'm already stuck

$ ntptrace
localhost: stratum 16, offset 0.000600, synch distance 0.00110
73.78.73.84: *Timeout*

ntpdc> debug more
debug level set to 1

(but this doesn't seem to make any difference)

ntpdc> monlist
remote address port local address count m ver code avgint lstint
===============================================================================
localhost 1094 127.0.0.1 2 7 2 0 5 0
endjinn.austria.eu.net 123 192.168.1.5 2 4 4 0 65 12
ns1.langstoeger.at 123 192.168.1.5 2 2 4 0 64 12
intranet.kapper.net 123 192.168.1.5 2 4 4 0 64 14

ntpdc> sysinfo
system peer: 0.0.0.0
system peer mode: unspec
leap indicator: 11
stratum: 16
precision: -10
root distance: 0.00000 s
root dispersion: 0.00168 s
reference ID: [73.78.73.84]
reference time: 00000000.00000000 Thu, Feb 7 2036 6:28:16.000
system flags: auth monitor ntp kernel stats
jitter: 0.000977 s
stability: 0.000 ppm
broadcastdelay: 0.003998 s
authdelay: 0.000000 s

ntpdc> showpeer ns1
remote 192.168.1.4, local 192.168.1.5
hmode sym_active, pmode unspec, stratum 3, precision -10
leap 00, refid [62.116.5.124], rootdistance 0.08446, rootdispersion 0.08749
ppoll 6, hpoll 6, keyid 0, version 4, association 9910
reach 007, unreach 0, flash 0x0000, boffset 0.00400, ttl/mode 0
timer 64s, flags config, bclient
reference time: cda1971b.2e05d7a7 Tue, Apr 28 2009 14:54:19.179
originate timestamp: cda199c5.60af5aea Tue, Apr 28 2009 15:05:41.377
receive timestamp: cda199d6.8538ef34 Tue, Apr 28 2009 15:05:58.520
transmit timestamp: cda199d6.8538ef34 Tue, Apr 28 2009 15:05:58.520
filter delay: 0.00098 0.00098 0.00098 0.00000
0.00000 0.00000 0.00000 0.00000
filter offset: -17.1427 -46.7118 -36.0310 0.000000
0.000000 0.000000 0.000000 0.000000
filter order: 0 1 2 3
4 5 6 7
offset -17.142724, delay 0.00098, error bound 1.39272, filter error 4.98099

ntpdc> listpeers
client intranet.kapper.net
client endjinn.austria.eu.net
sym_active ns1.langstoeger.at

ntpdc> peers
remote local st poll reach delay offset disp
=======================================================================
=intranet.kapper 192.168.1.5 2 64 377 0.02753 -151.1946 0.05504
=relay2.austria. 192.168.1.5 3 64 376 0.02631 -88.42472 0.07394
+ns1.langstoeger 192.168.1.5 3 64 377 0.00098 -162.5557 0.05354

Any ideas (I have no [TCPware] support contract, and I hate to see
me switching to TCPIP - or perhaps only TIMED - cause of this)

0 new messages