09 November, 2007

To quote Star Trek

"There is the theory of the moebius, a twist in the fabric of space, where time becomes a loop."

Just found one of our DNS boxes (running Solaris 9/Sparc) doing this:


bash-2.05$ date
Thu Nov 8 17:24:25 EST 2007
bash-2.05$ date
Thu Nov 8 17:24:26 EST 2007
bash-2.05$ date
Thu Nov 8 17:24:27 EST 2007
bash-2.05$ date
Thu Nov 8 17:24:27 EST 2007
bash-2.05$ date
Thu Nov 8 17:24:25 EST 2007
bash-2.05$ date
Thu Nov 8 17:24:25 EST 2007
bash-2.05$ date
Thu Nov 8 17:24:26 EST 2007
bash-2.05$ date
Thu Nov 8 17:24:27 EST 2007
bash-2.05$ date
Thu Nov 8 17:24:27 EST 2007
bash-2.05$


That's just me hitting 'date' repeatedly. Its the results which are rather strange.

Guess its time for a reboot, and hope that the machine comes back.

Update:

Reboot was successful. Pulled a copy of syslog off the machine before doing so, just in case Really Bad Things ™ were about to happen. Found the following interesting bits right before the time loop began:


Dec 30 19:00:00 xyz named[3721]: [ID 873579 daemon.crit] timer.c:447: fatal error:
Dec 30 19:00:00 xyz named[3721]: [ID 873579 daemon.crit] RUNTIME_CHECK(isc_time_now((&now)) == 0) failed
Dec 30 19:00:00 xyz named[3721]: [ID 873579 daemon.crit] exiting (due to fatal error in library)


Note the odd timestamp. The epoch, maybe, corrected for GMT-5?

Don't really know what is going on, and Google was, surprisingly, no help with the error message.

No comments:

Post a Comment