Invalid uptime warning messages
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 * **
Re: Invalid uptime warning messages
I wrote: At 10:00 p.m. my tor server began issuing a warning message about a Apparently, my contact lens blurred and I misread the time. Obviously, I should have typed 10:08 p.m. 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 * **
Re: Invalid uptime warning messages
Scott Bennett wrote: At 10:00 p.m. my tor server began issuing a warning message about a negative uptime: yep, the same here on blutmagie. TZ is UTC+1 Feb 17 04:40:45.116 [warn] Invalid uptime -19907 btw: I just found that even with MAX_FILEDESCRIPTORS=32768 tor regularly complains about too many open files. On my box the number of file descriptors tends to be about 10.000. Feb 17 11:49:36.374 [warn] Error creating network socket: Too many open files regards Olaf signature.asc Description: OpenPGP digital signature
Re: Invalid uptime warning messages
On Sunday 17 February 2008 10:56:28 Olaf Selke wrote: Scott Bennett wrote: At 10:00 p.m. my tor server began issuing a warning message about a negative uptime: yep, the same here on blutmagie. TZ is UTC+1 Feb 17 04:40:45.116 [warn] Invalid uptime -19907 The affected router appears to be 'crobertp'. It has the invalid uptime value in it's router descriptor: signature.asc Description: This is a digitally signed message part.
Re: Invalid uptime warning messages
On Sunday 17 February 2008 12:10:40 Robert Hogan wrote: On Sunday 17 February 2008 10:56:28 Olaf Selke wrote: Scott Bennett wrote: At 10:00 p.m. my tor server began issuing a warning message about a negative uptime: yep, the same here on blutmagie. TZ is UTC+1 Feb 17 04:40:45.116 [warn] Invalid uptime -19907 The affected router appears to be 'crobertp'. It has the invalid uptime value in it's router descriptor: 250+desc/name/crobertp= router crobertp 201.51.22.53 563 0 9030 platform Tor 0.1.1.24 on Linux i686 published 2008-02-17 09:03:34 opt fingerprint 3D18 77CA 3BBD 97A5 9D38 0640 6696 E692 420B EF67 uptime -19907 bandwidth 20480 51200 0 I've bcc'd the owner of the router so he can upgrade his Tor (0.1.1.24 must be deprecated by now). signature.asc Description: This is a digitally signed message part.
Re: Invalid uptime warning messages
Scott Bennett schrieb: At 10:00 p.m. my tor server began issuing a warning message about a negative uptime: Yes, the same here on 2 nodes, one starting this night between 3 and 4 UTC, the other on startup this morning. I had a quick look at debug messages here, I think there is some router with a weird descriptor and Tor discards it upon download and tries to download it again at some later time (on non-directory-caches every 10min). After the last warning about the invalid uptime (2 hours ago) I got Feb 17 11:33:21.408 [debug] download_status_increment_failure(): 3AE4C8E5C4CA589CF51861F9294BC9B8020D3308 failed 5 time(s); Giving up for a while. So I assume this router to be the one with the invalid uptime in the descriptor. Dominik
Re: Invalid uptime warning messages
Scott Bennett schrieb: At 10:00 p.m. my tor server began issuing a warning message about a negative uptime: the same here on arachne TZ is UTC+1 Feb 17 04:26:58.192 [warn] Invalid uptime -19907 Feb 17 13:58:23.510 [debug] router_new_address_suggestion(): Got X-Your-Address-Is: 84.165.114.73. Feb 17 13:58:24.222 [debug] resolve_my_address(): Resolved Address to '84.165.114.73'. Feb 17 13:58:24.222 [debug] connection_dir_client_reached_eof(): Time on received directory is within tolerance; we are 0 seconds skewed. (That's okay.) Feb 17 13:58:24.222 [info] connection_dir_client_reached_eof(): Received server info (size 2425) from server '194.109.206.212:80' Feb 17 13:58:24.222 [warn] Invalid uptime -19907 Feb 17 13:58:24.222 [info] router_load_routers_from_string(): 0 elements to add Feb 17 13:58:24.258 [info] entry_guards_compute_status(): Summary: Entry 'elc2' is reachable, usable, and live. regards Ruediger
