Solaris 8 xntp time synchronisation

From: sunmanagers freehome.ch (sunmanagers@freehome.ch)
Date: Sun Mar 02 2003 - 18:12:28 EST


Hi Sunmanagers

Now I have a problem since 2 month and I could not solve the problem. I use
a Serial MouseClock which is connected to the serial port. As software I use
latest version of XNTP V4.1.1b: What I did was following:

- My Location is Switzerland and this is the reason why I used by the
Installtion Europe > Midle Europe as location for TimeZone (MET).

- OS is Solaris 8 Core with latest Cluster from 17.01.2003. Hardware
Sparcstation 5 170MHz sun4m.

- To install and compile the software I used following commands:
        Source download from > http://www.eecis.udel.edu/~ntp/

        # gzip -dc ntp-4.1.1b.tar.gz | tar xvf -
        # cd /ntp-4.1.1b
        # ./configure \
        --prefix=/opt/xntp-4.1.1b \
        --exec-prefix=/opt/xntp-4.1.1b \
        --enable-debugging \
        --enable-RAWDCF

        # make
        # make install

        # ln -s /dev/ttyb /dev/refclock-0
        # ls -la /dev/refclock-0
        lrwxrwxrwx 1 root other /dev/refclock-0 -> /dev/ttyb

        # mkdir /opt/xntp-4.1.1b/parseutil
        # cp -p /root/xntp/ntp-4.1.1b/parseutil/testdcf
/opt/xntp-4.1.1b/parseutil

        # /opt/xntp-4.1.1b/parseutil/testdcf /dev/refclock-0
          DCF77 monitor - Copyright (C) 1993-1996, Frank Kardel

          RADMLSMin....PHour..PMDay..DayMonthYear....P
          RADMLS1248124P124812P1248121241248112481248P
        - ............................................

        # mkdir /opt/xntp-4.1.1b/conf
        # vi /opt/xntp-4.1.1b/conf/xntp.conf

        -------------------- /opt/xntp/conf/xntp.conf --------------------

        server 127.127.8.0 prefer mode 16
        logfile /var/log/xntp/xntp.log
        driftfile /var/log/xntp/xntp.drift

        # The following peer host are client machines
        # for synchronize the time:
        peer xxxxxxx

        # This configuration will log all events:
        #logconfig =all

        # This would just list the synchronizations
        # state of ntpd and the major system events.
        # For a simple reference server, the following
        # minimum message configuration could be useful:
        logconfig =syncstatus +sysevents +peerevents

        # This configuration will list all clock information
        # and synchronization information. All other events
        # and messages about peers, system events and so on
        # is suppressed:
        #logconfig =syncall +clockall

        -------------------- /opt/xntp/conf/xntp.conf --------------------

        # mkdir /var/log/xntp/

        # vi /etc/init.d/xntp
        # chown root:sys /etc/init.d/xntp
        # chmod 744 /etc/init.d/xntp

        -------------------- /etc/init.d/xntp --------------------

        #!/bin/sh
        #
        # xntp This shell script takes care of starting and
stopping
        # xntp

        case "$1" in
        'start')
                echo "Starting xntp in udp port 123: "
                /opt/xntp-4.1.1b/bin/ntpd -d -g -c /opt/xntp/conf/xntp.conf
-p /var/run/xntp.pid
                echo "xntp was started in udp port 123: "
                ;;
        'stop')
                echo "Shutting down xntp in udp port 123: "
                kill `cat /var/run/xntp.pid`
                echo "xntp was terminating in udp port 123: "
                        ;;
          *)
                echo "Usage: $0 xntp { start | stop }"
                exit 1
                ;;
        esac
        exit 0

        -------------------- /etc/init.d/xntp --------------------

        # /etc/init.d/xntp start

        After about 1 or 2 hour the deamon will end without given a commad
like
      /etc/init.d/xntp stop it end itself. The log will show following:

 2 Mar 21:03:21 ntpd[10130]: Un-parsable frequency in
/var/log/xntp/xntp.drift
 2 Mar 21:03:21 ntpd[10130]: signal_no_reset: signal 18 had flags 20000
 2 Mar 21:03:21 ntpd[10130]: system event 'event_restart' (0x01) status
'sync_alarm, sync_unspec, 1 event, event_unspec' (0xc010)
 2 Mar 21:04:21 ntpd[10130]: PARSE receiver #0: packet format "RAW DCF77
Timecode"
 2 Mar 21:04:21 ntpd[10130]: PARSE receiver #0: STATE CHANGE: -> TIME CODE;
(LEAP INDICATION; ANTENNA)
 2 Mar 21:04:21 ntpd[10130]: PARSE receiver #0: SYNCHRONIZED
 2 Mar 21:04:21 ntpd[10130]: clock GENERIC(0) event 'clk_okay' (0x00)
 2 Mar 21:04:21 ntpd[10130]: peer GENERIC(0) event 'event_peer_clock' (0x85)
status 'unreach, conf, 1 event, event_peer_clock' (0x8015)
 2 Mar 21:04:21 ntpd[10130]: system event 'event_clock_excptn' (0x07) status
'sync_alarm, sync_unspec, 2 events, event_restart' (0xc021)
 2 Mar 21:04:21 ntpd[10130]: peer GENERIC(0) event 'event_reach' (0x84)
status 'unreach, conf, 2 events, event_reach' (0x8024)
 2 Mar 21:06:50 ntpd[10130]: system event 'event_peer/strat_chg' (0x04)
status 'sync_alarm, sync_lf_clock, 3 events, event_clock_excptn' (0xc237)
 2 Mar 19:43:29 ntpd[10130]: time set -5001.122617 s
 2 Mar 19:43:29 ntpd[10130]: synchronisation lost
 2 Mar 19:43:29 ntpd[10130]: system event 'event_clock_reset' (0x05) status
'sync_alarm, sync_unspec, 4 events, event_peer/strat_chg' (0xc044)
 2 Mar 19:43:29 ntpd[10130]: system event 'event_sync_chg' (0x03) status
'sync_alarm, sync_unspec, 5 events, event_clock_reset' (0xc055)
 2 Mar 19:50:00 ntpd[10130]: PARSE receiver #0: conversion status
"CONVERSION FAILED; DATE ILLEGAL"
 2 Mar 19:50:00 ntpd[10130]: PARSE receiver #0: interval for following error
message class is at least 00:01:00
 2 Mar 19:50:00 ntpd[10130]: PARSE receiver #0: FAILED TIMECODE:
"------------------M-S----1-4p1--?1-P-2----12412---12------p" (check
receiver configuration / cableling)
 2 Mar 19:50:00 ntpd[10130]: clock GENERIC(0) event 'clk_baddate' (0x05)
 2 Mar 19:50:00 ntpd[10130]: peer GENERIC(0) event 'event_peer_clock' (0x85)
status 'unreach, conf, 3 events, event_peer_clock' (0x8035)
 2 Mar 19:50:00 ntpd[10130]: system event 'event_clock_excptn' (0x07) status
'sync_alarm, sync_unspec, 6 events, event_sync_chg' (0xc063)
 2 Mar 19:51:00 ntpd[10130]: PARSE receiver #0: SYNCHRONIZED
 2 Mar 19:51:00 ntpd[10130]: clock GENERIC(0) event 'clk_okay' (0x00)
 2 Mar 19:51:00 ntpd[10130]: peer GENERIC(0) event 'event_peer_clock' (0x85)
status 'unreach, conf, 4 events, event_peer_clock' (0x8045)
 2 Mar 19:55:00 ntpd[10130]: parse: convert_rawdcf: parity check FAILED for
"------------------M-S1-4-1-4p1--81-P-2----12412---124-----"
 2 Mar 19:55:00 ntpd[10130]: PARSE receiver #0: conversion status
"CONVERSION FAILED; DATE ILLEGAL"
 2 Mar 19:55:00 ntpd[10130]: PARSE receiver #0: interval for following error
message class is at least 00:01:00
 2 Mar 19:55:00 ntpd[10130]: PARSE receiver #0: FAILED TIMECODE:
"------------------M-S1-4-1-4p1--81-P-2----12412---124-----p" (check
receiver configuration / cableling)
 2 Mar 19:55:00 ntpd[10130]: clock GENERIC(0) event 'clk_baddate' (0x05)
 2 Mar 19:55:00 ntpd[10130]: peer GENERIC(0) event 'event_peer_clock' (0x85)
status 'unreach, conf, 5 events, event_peer_clock' (0x8055)
 2 Mar 19:56:00 ntpd[10130]: PARSE receiver #0: SYNCHRONIZED
 2 Mar 19:56:00 ntpd[10130]: clock GENERIC(0) event 'clk_okay' (0x00)
 2 Mar 19:56:00 ntpd[10130]: peer GENERIC(0) event 'event_peer_clock' (0x85)
status 'unreach, conf, 6 events, event_peer_clock' (0x8065)
 2 Mar 20:31:00 ntpd[10130]: parse: convert_rawdcf: parity check FAILED for
"------------------M-S1---12-P-----2P-2----12412-8-12------"
 2 Mar 20:31:00 ntpd[10130]: PARSE receiver #0: conversion status
"CONVERSION FAILED; DATE ILLEGAL"
 2 Mar 20:31:00 ntpd[10130]: PARSE receiver #0: interval for following error
message class is at least 00:01:00
 2 Mar 20:31:00 ntpd[10130]: PARSE receiver #0: FAILED TIMECODE:
"------------------M-S1---12-P-----2P-2----12412-8-12------p" (check
receiver configuration / cableling)
 2 Mar 20:31:00 ntpd[10130]: clock GENERIC(0) event 'clk_baddate' (0x05)
 2 Mar 20:31:00 ntpd[10130]: peer GENERIC(0) event 'event_peer_clock' (0x85)
status 'unreach, conf, 7 events, event_peer_clock' (0x8075)
 2 Mar 20:32:00 ntpd[10130]: PARSE receiver #0: SYNCHRONIZED
 2 Mar 20:32:00 ntpd[10130]: clock GENERIC(0) event 'clk_okay' (0x00)
 2 Mar 20:32:00 ntpd[10130]: peer GENERIC(0) event 'event_peer_clock' (0x85)
status 'unreach, conf, 8 events, event_peer_clock' (0x8085)
 2 Mar 20:33:36 ntpd[10130]: parse: convert_rawdcf: INCOMPLETE DATA - time
code only has 36 bits
 2 Mar 20:33:36 ntpd[10130]: PARSE receiver #0: conversion status
"CONVERSION FAILED; DATE ILLEGAL"
 2 Mar 20:33:36 ntpd[10130]: PARSE receiver #0: interval for following error
message class is at least 00:01:00
 2 Mar 20:33:36 ntpd[10130]: PARSE receiver #0: FAILED TIMECODE:
"------------------M-S---8-24p1----2" (check receiver configuration /
cableling)
 2 Mar 20:33:36 ntpd[10130]: clock GENERIC(0) event 'clk_baddate' (0x05)
 2 Mar 20:33:36 ntpd[10130]: peer GENERIC(0) event 'event_peer_clock' (0x85)
status 'unreach, conf, 9 events, event_peer_clock' (0x8095)
 2 Mar 20:34:00 ntpd[10130]: parse: convert_rawdcf: INCOMPLETE DATA - time
code only has 24 bits
 2 Mar 20:34:00 ntpd[10130]: PARSE receiver #0: conversion status
"CONVERSION FAILED; DATE ILLEGAL"

And so on and so on.....after a while!!!

 2 Mar 21:20:00 ntpd[10130]: PARSE receiver #0: SYNCHRONIZED
 2 Mar 21:20:00 ntpd[10130]: clock GENERIC(0) event 'clk_okay' (0x00)
 2 Mar 21:20:00 ntpd[10130]: peer GENERIC(0) event 'event_peer_clock' (0x85)
status 'reach, conf, sel_sys.peer, 15 events, event_peer_clock' (0x96f5)
 2 Mar 21:21:51 ntpd[10130]: time reset -0.330192 s
 2 Mar 21:21:51 ntpd[10130]: synchronisation lost
 2 Mar 21:21:51 ntpd[10130]: system event 'event_clock_reset' (0x05) status
'leap_none, sync_unspec, 15 events, event_clock_excptn' (0xf7)
 2 Mar 21:21:51 ntpd[10130]: system event 'event_peer/strat_chg' (0x04)
status 'leap_none, sync_unspec, 15 events, event_clock_reset' (0xf5)
 2 Mar 21:21:53 ntpd[10130]: peer GENERIC(0) event 'event_reach' (0x84)
status 'unreach, conf, 15 events, event_reach' (0x80f4)
 2 Mar 21:25:00 ntpd[10130]: parse: convert_rawdcf: parity check FAILED for
"------------------M-S1-4--2-P1----2p-2----12412---12-8----"
 2 Mar 21:25:00 ntpd[10130]: PARSE receiver #0: conversion status
"CONVERSION FAILED; DATE ILLEGAL"
 2 Mar 21:25:00 ntpd[10130]: PARSE receiver #0: interval for following error
message class is at least 00:01:00
 2 Mar 21:25:00 ntpd[10130]: PARSE receiver #0: FAILED TIMECODE:
"------------------M-S1-4--2-P1----2p-2----12412---12-8----p" (check
receiver configuration / cableling)
 2 Mar 21:25:00 ntpd[10130]: clock GENERIC(0) event 'clk_baddate' (0x05)
 2 Mar 21:25:00 ntpd[10130]: peer GENERIC(0) event 'event_peer_clock' (0x85)
status 'reach, conf, 15 events, event_peer_clock' (0x90f5)
 2 Mar 21:25:00 ntpd[10130]: system event 'event_clock_excptn' (0x07) status
'leap_none, sync_unspec, 15 events, event_peer/strat_chg' (0xf4)
 2 Mar 21:26:00 ntpd[10130]: PARSE receiver #0: SYNCHRONIZED
 2 Mar 21:26:00 ntpd[10130]: clock GENERIC(0) event 'clk_okay' (0x00)
 2 Mar 21:26:00 ntpd[10130]: peer GENERIC(0) event 'event_peer_clock' (0x85)
status 'reach, conf, 15 events, event_peer_clock' (0x90f5)
 2 Mar 21:26:00 ntpd[10130]: system event 'event_peer/strat_chg' (0x04)
status 'leap_none, sync_lf_clock, 15 events, event_clock_excptn' (0x2f7)
 2 Mar 21:53:26 ntpd[10130]: parse: convert_rawdcf: INCOMPLETE DATA - time
code only has 26 bits
 2 Mar 21:53:26 ntpd[10130]: PARSE receiver #0: conversion status
"CONVERSION FAILED; DATE ILLEGAL"
 2 Mar 21:53:26 ntpd[10130]: PARSE receiver #0: interval for following error
message class is at least 00:01:00
 2 Mar 21:53:26 ntpd[10130]: PARSE receiver #0: FAILED TIMECODE:
"------------------M-S--48" (check receiver configuration / cableling)
 2 Mar 21:53:26 ntpd[10130]: clock GENERIC(0) event 'clk_baddate' (0x05)
 2 Mar 21:53:26 ntpd[10130]: peer GENERIC(0) event 'event_peer_clock' (0x85)
status 'reach, conf, sel_sys.peer, 15 events, event_peer_clock' (0x96f5)
 2 Mar 21:53:26 ntpd[10130]: system event 'event_clock_excptn' (0x07) status
'leap_none, sync_lf_clock, 15 events, event_peer/strat_chg' (0x2f4)
 2 Mar 21:54:00 ntpd[10130]: parse: convert_rawdcf: INCOMPLETE DATA - time
code only has 34 bits
 2 Mar 21:54:00 ntpd[10130]: PARSE receiver #0: conversion status
"CONVERSION FAILED; DATE ILLEGAL"
 2 Mar 21:55:00 ntpd[10130]: PARSE receiver #0: SYNCHRONIZED
 2 Mar 21:55:00 ntpd[10130]: clock GENERIC(0) event 'clk_okay' (0x00)
 2 Mar 21:55:00 ntpd[10130]: peer GENERIC(0) event 'event_peer_clock' (0x85)
status 'reach, conf, sel_sys.peer, 15 events, event_peer_clock' (0x96f5)
 2 Mar 21:55:04 ntpd[10130]: synchronisation lost
 2 Mar 21:55:04 ntpd[10130]: system event 'event_peer/strat_chg' (0x04)
status 'leap_none, sync_unspec, 15 events, event_clock_excptn' (0xf7)
 2 Mar 21:56:08 ntpd[10130]: time correction of 105337800 seconds exceeds
sanity limit (1000); set clock manually to the correct UTC time.
 2 Mar 21:56:08 ntpd[10130]: system event 'event_fault' (0x02) status
'leap_none, sync_lf_clock, 15 events, event_peer/strat_chg' (0x2f4
)

        If I controll the time and date of the machine it is all OK:

        # date
        Sun Mar 2 23:30:17 MET 2003

        # date -u
        Sun Mar 2 22:30:28 GMT 2003

To look if something is wrong I used the following information:

        # /opt/xntp-4.1.1b/bin/ntpdc -c kerninfo

pll offset: 0 s
pll frequency: -236.006 ppm
maximum error: 0.001552 s
estimated error: 1.6e-05 s
status: 0040 unsync
pll time constant: 0
precision: 1e-06 s
frequency tolerance: 512 ppm
pps frequency: 0.000 ppm
pps stability: 512.000 ppm
pps jitter: 0.0002 s
calibration interval: 4 s
calibration cycles: 0
jitter exceeded: 0
stability exceeded: 0
calibration errors: 0

        # /opt/xntp-4.1.1b/bin/ntptime -r

ntp_gettime() returns code 5 (ERROR)
  time c20d0b44.59a3b000 Sun, Mar 2 2003 23:59:16.350, (.350154),
  maximum error 42512 us, estimated error 16 us ntptime=c20d0b44.59a3b000
unixtime=3e628cc4.350154 Sun Mar 2 23:59:16 2003

ntp_adjtime() returns code 5 (ERROR)
  modes 0x0 (),
  offset 0.000 us, frequency -236.006 ppm, interval 4 s,
  maximum error 42512 us, estimated error 16 us,
  status 0x40 (UNSYNC),
  time constant 0, precision 1.000 us, tolerance 512 ppm,
  pps frequency 0.000 ppm, stability 512.000 ppm, jitter 200.000 us,
  intervals 0, jitter exceeded 0, stability exceeded 0, errors 0.

Trying also the following variable in /etc/system:

set dosynctodr=0

The same symptome......! I think something is wrong with the OS but I don't
know what!?

What is going wrong...! If I try to synchronize with clients this will
function but as I said after a while the master deamon stops itself....any
idea...should really solve the problem after working on this problem for two
months....? Any suggestions...PLEASE HELP.

Thanks in advanced for your help

Andrea
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers



This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:25:55 EDT