perfSONAR User Q&A and Other Discussion

[Zhi-Wei Lu <>]

I also saw these in the log file:

 

Dec 29 10:01:26 mammoth owampd[3227]: FILE=time.c, LINE=112, NTP: Status UNSYNC (clock offset issues likely)

Dec 29 10:01:26 mammoth owampd[3227]: FILE=time.c, LINE=118, NTP: STA_NANO should be set. Make sure ntpd is running, and your NTP configuration is good.

Dec 29 10:01:26 mammoth owampd[3228]: FILE=sapi.c, LINE=182, OWPServerSockCreate: Cannot assign requested address

Dec 29 10:01:26 mammoth owampd[3228]: FILE=owampd.c, LINE=1751, Unable to create server socket. Exiting...

Dec 29 10:14:26 mammoth owampd[4923]: FILE=time.c, LINE=112, NTP: Status UNSYNC (clock offset issues likely)

Dec 29 10:14:26 mammoth owampd[4923]: FILE=time.c, LINE=118, NTP: STA_NANO should be set. Make sure ntpd is running, and your NTP configuration is good.

Dec 29 10:14:26 mammoth owampd[4924]: FILE=sapi.c, LINE=182, OWPServerSockCreate: Cannot assign requested address

Dec 29 10:14:26 mammoth owampd[4924]: FILE=owampd.c, LINE=1751, Unable to create server socket. Exiting...

 

 

Zhi-Wei Lu

IET-CR-Network Operations Center

University of California, Davis

(530) 752-0155

 

From: Zhi-Wei Lu
Sent: Tuesday, December 29, 2015 10:31 AM
To:
Subject: owampd dies

 

Hi all,

 

On one of our perfsonar boxes, the owampd keeps dying.  I got error messages initially, when I try to start it:

 

owampd[4923]: FILE=time.c, LINE=112, NTP: Status UNSYNC (clock offset issues likely)

owampd[4923]: FILE=time.c, LINE=118, NTP: STA_NANO should be set. Make sure ntpd is running, and your NTP configuration is good.

/etc/init.d/owampd start: owampd started

 

Owampd would die right away.  The ntp is running on the server:

 

ntpq> pe

     remote           refid      st t when poll reach   delay   offset  jitter

==============================================================================

*tick.ucla.edu   .GPS.            1 u  113   64    2   11.428    1.643   0.040

+seiko.s.uw.edu  204.123.2.5      2 u   56   64    3   20.078    1.732   0.209

-ntp.ucdavis.edu 128.9.176.30     2 u   52   64    3    2.595    2.309   0.898

-nms-rlat.losa.n 192.12.19.20     2 u   53   64    3   27.413    7.349   0.198

+saturn.es.net   .CDMA.           1 u   50   64    3    4.683    1.631   0.211

 

Do I have to wait for bit until the ntp is “stable”?  I just rebooted the server a short while ago (actually, I swapped the identities of two perfsonar boxes this morning).

 

I would appreciate ideas to correct the issue here.  Thank you.

 

 

Zhi-Wei Lu

IET-CR-Network Operations Center

University of California, Davis

(530) 752-0155