low bandwidth utilization

[Ben Wilhelm]

Or perhaps you're running Tor under VMWare? It turns out VMWare is 
absolutely awful at keeping the system clock sane, and it can easily 
create weirdnesses like this.

-Ben

Florian Reitmeir wrote:
> Hi,
> 
>>>   /var/log/tor/log after the crash?
>> Nothing unusual as far as I can see:
>>
>> Jul 03 06:25:34.506 [notice] Tor 0.1.1.21 opening new log file.
>> Jul 03 14:32:13.626 [notice] hibernate_begin(): Interrupt: will shut down in 30 seconds. Interrupt again to exit now.
>> Jul 03 14:32:43.584 [notice] consider_hibernation(): Clean shutdown finished. Exiting.
>> Jul 03 14:32:49.316 [notice] Tor 0.1.1.21 opening log file.
>> Jul 03 14:32:49.527 [notice] Your Tor server's identity key fingerprint is 'redgene 3BB0 DC6E A321 256D DD11 5519 7DBD 3F1E 4862 3549'
>> Jul 03 14:32:50.523 [notice] We now have enough directory information to build circuits.
>> Jul 03 14:32:50.687 [notice] router_orport_found_reachable(): Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
>> Jul 03 14:32:51.383 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
>> Jul 02 06:25:22.809 [notice] Tor 0.1.1.21 opening new log file.
>> Jul 03 06:25:34.435 [notice] do_hup(): Received reload signal (hup). Reloading config.
>> Jul 01 06:25:31.956 [notice] Tor 0.1.1.21 opening new log file.
>> Jul 01 23:16:39.030 [notice] hibernate_begin(): Interrupt: will shut down in 30 seconds. Interrupt again to exit now.
>> Jul 01 23:17:09.703 [notice] consider_hibernation(): Clean shutdown finished. Exiting.
>> Jul 01 23:17:24.867 [notice] Tor 0.1.1.21 opening log file.
>> Jul 01 23:17:25.349 [notice] Your Tor server's identity key fingerprint is 'redgene 3BB0 DC6E A321 256D DD11 5519 7DBD 3F1E 4862 3549'
>> Jul 01 23:17:27.182 [notice] We now have enough directory information to build circuits.
>> Jul 01 23:17:27.746 [notice] router_orport_found_reachable(): Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
>> Jul 01 23:17:28.275 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
>> Jul 02 06:25:22.758 [notice] do_hup(): Received reload signal (hup). Reloading config.
>> Jun 30 06:25:31.988 [notice] Tor 0.1.1.21 opening new log file.
>> Jul 01 06:25:31.955 [notice] do_hup(): Received reload signal (hup). Reloading config.
>> Jun 29 06:25:03.123 [notice] Tor 0.1.1.21 opening new log file.
>> Jun 30 06:25:31.987 [notice] do_hup(): Received reload signal (hup). Reloading config.
>> Jun 28 06:25:32.537 [notice] Tor 0.1.1.21 opening new log file.
>> Jun 29 06:25:03.122 [notice] do_hup(): Received reload signal (hup). Reloading config.
> 
> is this your log file? the timestamps really make me shudder, normally log
> file entries are sorted in time...
> 
> do you use ntpdate with cron? or an ntpd on the system?
> 
>