Invalid uptime warning messages

[Scott Bennett]

     At 10:00 p.m. my tor server began issuing a warning message about a
negative uptime:

Feb 16 16:30:26.059 [notice] Your IP address seems to have changed to 66.225.36.43. Updating.
Feb 16 16:30:31.007 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Feb 16 16:30:49.556 [notice] Performing bandwidth self-test...done.
Feb 16 16:33:46.139 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent.
Feb 16 22:08:02.031 [warn] Invalid uptime "-19907"
Feb 16 22:09:01.581 [warn] Invalid uptime "-19907"
Feb 16 22:10:02.879 [warn] Invalid uptime "-19907"
Feb 16 22:11:04.153 [warn] Invalid uptime "-19907"
Feb 16 22:12:04.540 [warn] Invalid uptime "-19907"
Feb 16 22:13:05.834 [warn] Invalid uptime "-19907"
Feb 16 22:14:07.146 [warn] Invalid uptime "-19907"
Feb 16 22:15:07.441 [warn] Invalid uptime "-19907"
Feb 16 22:16:10.859 [warn] Invalid uptime "-19907"
Feb 16 22:17:09.581 [warn] Invalid uptime "-19907"

It has continued to issue these messages about every minute all through the
night so far.  What exactly is it complaining about?  An error in its own
uptime?  The system uptime looks valid to me.  What causes this to happen?
Is there a way to fix it while it's running?  Or does it just have to be
restarted?


                                  Scott Bennett, Comm. ASMELG, CFIAG
**********************************************************************
* Internet:       bennett at cs.niu.edu                              *
*--------------------------------------------------------------------*
* "A well regulated and disciplined militia, is at all times a good  *
* objection to the introduction of that bane of all free governments *
* -- a standing army."                                               *
*    -- Gov. John Hancock, New York Journal, 28 January 1790         *
**********************************************************************