It's not you, it's the TS2100. I have the same issue. Looks like this may be the end of life for this unit unless Datum/Symmetricom creates a patch. I saw the issue start around May 2 21:05 EDT.
The time shows 619315200 seconds behind: 619315200/60/60/24/7 = 1024 weeks. It did seem like the leap second issue was no longer a problem tho, the seconds were no longer mismatched. :-/ On Sun, May 03, 2015 at 04:31:01PM -0700, Bob Martin wrote: > My Tymserve 2100 gps unit (Rev 4.1) thinks it's 1995 -- September 17, 1995. > > But a restart (connect via telnet and give the commands util restart) brings > it back to the correct time and date -- for a while? I haven't caught it > dropping back, so i don't know if it's doing this on the hour, after an hour, > or what, but I noticed it last night, and I've restarted it a few times today. > > Any clues? > > I know about the off-by-a-second issue with the pending leap second. This one > is more interesting! > > So far I've just been issuing software restarts. The next time I'll power > cycle the sucker and see if that does any good. > > GPS signal isn't the issue; the 2100 shares an external GPS antenna with my > Thunderbolts through a Symmetricom 58536A GPS splitter, and the Thunderbolts > are as happy as a Thunderbolt can be. > > cheers > > bob k6rtm > > > _______________________________________________ > time-nuts mailing list -- [email protected] > To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. _______________________________________________ time-nuts mailing list -- [email protected] To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
