EPICS Home

Experimental Physics and Industrial Control System


 
1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Windows IOC time error messages
From: Mark Rivers <[email protected]>
To: "'[email protected] Talk'" <[email protected]>
Date: Thu, 2 Jun 2016 22:25:42 +0000

My Windows IOCs just started printing the following messages at a high rate:

 

currentTime::getCurrentTime(): 0.000003 sec time discontinuity detected

currentTime::getCurrentTime(): 0.000003 sec time discontinuity detected

currentTime::getCurrentTime(): 0.000004 sec time discontinuity detected

currentTime::getCurrentTime(): 0.000004 sec time discontinuity detected

currentTime::getCurrentTime(): 0.000002 sec time discontinuity detected

currentTime::getCurrentTime(): 0.000004 sec time discontinuity detected

currentTime::getCurrentTime(): 0.000004 sec time discontinuity detected

currentTime::getCurrentTime(): 0.000003 sec time discontinuity detected

currentTime::getCurrentTime(): 0.000003 sec time discontinuity detected

currentTime::getCurrentTime(): 0.000004 sec time discontinuity detected

currentTime::getCurrentTime(): 0.000004 sec time discontinuity detected

currentTime::getCurrentTime(): 0.000003 sec time discontinuity detected

currentTime::getCurrentTime(): 0.000004 sec time discontinuity detected

currentTime::getCurrentTime(): 0.000004 sec time discontinuity detected

currentTime::getCurrentTime(): 0.000004 sec time discontinuity detected

errlog: 3 messages were discarded

currentTime::getCurrentTime(): 0.000004 sec time discontinuity detected

currentTime::getCurrentTime(): 0.000003 sec time discontinuity detected

currentTime::getCurrentTime(): 0.000002 sec time discontinuity detected

currentTime::getCurrentTime(): 0.000004 sec time discontinuity detected

currentTime::getCurrentTime(): 0.000003 sec time discontinuity detected

currentTime::getCurrentTime(): 0.000003 sec time discontinuity detected

currentTime::getCurrentTime(): 0.000004 sec time discontinuity detected

currentTime::getCurrentTime(): 0.000004 sec time discontinuity detected

currentTime::getCurrentTime(): 0.000004 sec time discontinuity detected

currentTime::getCurrentTime(): 0.000004 sec time discontinuity detected

currentTime::getCurrentTime(): 0.000004 sec time discontinuity detected

currentTime::getCurrentTime(): 0.000004 sec time discontinuity detected

currentTime::getCurrentTime(): 0.000004 sec time discontinuity detected

errlog: 12 messages were discarded

currentTime::getCurrentTime(): 0.000003 sec time discontinuity detected

currentTime::getCurrentTime(): 0.000002 sec time discontinuity detected

currentTime::getCurrentTime(): 0.000004 sec time discontinuity detected

 

This is base 3.14.12.5.

 

What can cause this?  The time on the Windows machine appears to agree within 1 second to that on a Linux server.

 

Thanks,

Mark

 


Replies:
Re: Windows IOC time error messages Andrew Johnson

Navigate by Date:
Prev: RE: Unable to initialize parameter with setStringParam() Mark Rivers
Next: Re: Windows IOC time error messages Andrew Johnson
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: Unable to initialize parameter with setStringParam() Mark Rivers
Next: Re: Windows IOC time error messages Andrew Johnson
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024