[ntp:questions] Re: Clock type 30 invalid?

Richard B. Gilbert rgilbert88 at comcast.net
Thu Jan 22 02:42:23 UTC 2004


John,

I thought I had replied to this last night but I don't see a reply so 
I'll try again.

sunblok_#  ntpcc
ntpdc> version
ntpdc 4.2.0 at 1.1161-r Wed Jan 21 19:00:16 EST 2004 (2)

sunblok_# ntpq -c version
ntpq 4.2.0 at 1.1161-r Wed Jan 21 19:00:17 EST 2004 (2)

and, cut and pasted from the output of dmesg:
Jan 21 19:10:32 sunblok ntpd[480]: [ID 702911 daemon.notice] ntpd 
exiting on signal 15
Jan 21 19:10:39 sunblok ntpdate[8509]: [ID 702911 daemon.notice] adjust 
time server 128.59.59.177 offset 0.000606 sec
Jan 21 19:10:42 sunblok ntpd[8511]: [ID 702911 daemon.notice] ntpd 
4.2.0 at 1.1161-r Wed Jan 21 19:00:07 EST 2004 (2)
Jan 21 19:10:42 sunblok ntpd[8511]: [ID 702911 daemon.error] 
refclock_newpeer: clock type 30 invalid
Jan 21 19:10:42 sunblok ntpd[8511]: [ID 702911 daemon.error] 
configuration of 127.127.30.0 failed
Jan 21 19:13:59 sunblok ntpd[8511]: [ID 702911 daemon.notice] kernel 
time sync disabled 0041
Jan 21 19:15:05 sunblok ntpd[8511]: [ID 702911 daemon.notice] kernel 
time sync enabled 0001

I think all this clearly shows that I'm running the NTP 4.2  version 
that I built.  The NTP version distributed with Solaris 8 is v3.x and 
the daemon is called "xntpd".


John Ackermann N8UR wrote:

> Dumb question, but is there another version of ntpd on your system 
> that might be running instead of your compiled version?  i.e., one 
> sitting in /usr/sbin vs. your version in /usr/local/bin?
>
> John
>
> --On Wednesday, January 21, 2004 19:18:36 -0500 "Richard B. Gilbert" 
> <rgilbert88 at comcast.net> wrote:
>
>> All right.   I did:
>>
>> ./configure --enable-ONCORE
>> make
>> make install
>>
>> I stopped ntpd and started it again.
>>
>> The following lines are cut and pasted from the output of dmesg!
>>
>>
>> Jan 21 19:10:32 sunblok ntpd[480]: [ID 702911 daemon.notice] ntpd 
>> exiting
>> on signal 15
>> Jan 21 19:10:39 sunblok ntpdate[8509]: [ID 702911 daemon.notice] adjust
>> time server 128.59.59.177 offset 0.000606 sec
>> Jan 21 19:10:42 sunblok ntpd[8511]: [ID 702911 daemon.notice] ntpd
>> 4.2.0 at 1.1161-r Wed Jan 21 19:00:07 EST 2004 (2)
>> Jan 21 19:10:42 sunblok ntpd[8511]: [ID 702911 daemon.error]
>> refclock_newpeer: clock type 30 invalid
>> Jan 21 19:10:42 sunblok ntpd[8511]: [ID 702911 daemon.error]
>> configuration of 127.127.30.0 failed
>>
>> What do I try now?  Does anyone have this particular configuration
>> working?  Solaris 8  on an Ultra 5 with the Oncore driver?
>>
>> TIA
>>
>>
>> Paul Croome wrote:
>>
>>> "Richard B. Gilbert" <rgilbert88 at comcast.net> wrote in message
>>> news:<Af2dnYwgPd26DpHdRVn-vA at comcast.com>...
>>>
>>>
>>>> I used the default build procedures.  ./configure, make, etc.
>>>>
>>>>
>>>
>>> Richard,
>>>
>>> To include support for the Motorola M12:
>>>
>>>   ./configure --enable-ONCORE
>>>   make
>>>
>>> If the M12 is the only reference clock in your system,
>>> you can generate a smaller object file with:
>>>
>>>   ./configure --disable-all-clocks --enable-ONCORE
>>>   make
>>>
>>> For more information:
>>>   ./configure --help
>>> and see also html/config.html.
>>> Caveat: There are two distinct configuration phases for NTP:
>>> compile-time (see above) and run-time (controlled by /etc/ntp.conf).
>>> The NTP doc doesn't always distinguish clearly what's which.
>>>
>>> BTW: You shouldn't fudge the GPS timeserver to stratum=0.
>>> Stratum 0 is notionally assigned to the Motorola hardware,
>>> in your case, and to reference clocks in general;
>>> strata 1 thru 15 are assigned to the NTP timeservers;
>>> stratum 16 usually means 'out of order'.
>>> Usually it's OK to let NTP figure out the stratum, i.e.
>>> just take the default.
>>>
>>> Regards,
>>> Paul
>>>
>>>
>>
>> _______________________________________________
>> questions mailing list
>> questions at ntp.org
>> http://mailman.ntp.org/mailman/listinfo/questions
>>
>>
>
>
>
>




More information about the questions mailing list