Forgot to add more logs, here is what I see: Sep 18 19:09:38.000 [notice] No circuits are opened. Relaxed timeout for circuit 768451 (a Measuring circuit timeout 3-hop circuit in state doing hand shakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. 32 guards are live. [21 similar message(s) suppresse d in last 3600 seconds] Sep 19 04:59:17.000 [warn] connection_edge_process_relay_cell (at origin) failed. Sep 19 05:18:42.000 [warn] connection_edge_process_relay_cell (at origin) failed. Sep 19 05:18:49.000 [warn] connection_edge_process_relay_cell (at origin) failed. Sep 19 05:30:21.000 [warn] connection_edge_process_relay_cell (at origin) failed. Sep 19 05:48:32.000 [warn] connection_edge_process_relay_cell (at origin) failed. Sep 19 05:56:41.000 [warn] connection_edge_process_relay_cell (at origin) failed. Sep 19 06:28:10.000 [warn] connection_edge_process_relay_cell (at origin) failed. Sep 19 06:33:31.000 [warn] connection_edge_process_relay_cell (at origin) failed. Sep 19 06:39:32.000 [warn] connection_edge_process_relay_cell (at origin) failed. Sep 19 06:41:06.000 [warn] connection_edge_process_relay_cell (at origin) failed. Sep 19 06:56:06.000 [warn] connection_edge_process_relay_cell (at origin) failed. Sep 19 09:28:43.000 [notice] Heartbeat: Tor's uptime is 13 days 23:59 hours, Sep 19 10:58:22.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 603s after 18 timeouts and 190 buildtimes.
> Hello, > > This place seems very quite, not sure if this is the right place to ask. > > I'm encountering a weird behavior from my tor daemon that's running a > hidden service, after a week or two, it stops accepting any connections. > And the only thing that makes it work again is a restart. > > I'm using Tor 0.2.8.7 > Sep 19 23:12:17.607 [notice] Tor v0.2.8.7 (git-cc2f02ef17899f86) running > on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.1k and Zlib 1.2.8. > > I also see a warning like, could this be the cause ? > [warn] OpenSSL version from headers does not match the version we're > running with. If you get weird crashes, that might be why. (Compiled with > 1000114f: OpenSSL 1.0.1t 3 May 2016; running with 100010bf: OpenSSL > 1.0.1k 8 Jan 2015). > > Sep 19 23:12:17.607 [notice] Tor can't help you if you use it wrong! Learn > how to be safe at https://www.torproject.org/download/download#warning > > Also found somebody complaining about the same behavior, but without any > answers > > http://serverfault.com/questions/745572/ubuntu-14-04-tor-doesnt-restore-circuits-after-disabling-due-to-traffic-inact > > Cheers, > Md Rot > _______________________________________________ tor-onions mailing list [email protected] https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-onions
