I'm noticing that if i attempt to restart tor AFTER AccountingMax has been reached (meaning it's currently hibernating), tor itself fails to start. if i increase AccountingMax in torrc, then it restarts just fine.
normal?
--
Thanks,
Fabian S.
OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC
On 21 Dec 2017, at 03:07, Fabian A. Santiago fsantiago@garbage-juice.com wrote:
I'm noticing that if i attempt to restart tor AFTER AccountingMax has been reached (meaning it's currently hibernating), tor itself fails to start.
What do you mean by "fails to start"? What are the log messages?
if i increase AccountingMax in torrc, then it restarts just fine.
normal?
It's hard to say, without any log messages.
T
December 20, 2017 3:32 PM, "teor" teor2345@gmail.com wrote:
On 21 Dec 2017, at 03:07, Fabian A. Santiago fsantiago@garbage-juice.com wrote:
I'm noticing that if i attempt to restart tor AFTER AccountingMax has been reached (meaning it's currently hibernating), tor itself fails to start.
What do you mean by "fails to start"? What are the log messages?
if i increase AccountingMax in torrc, then it restarts just fine.
normal?
It's hard to say, without any log messages.
T _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Teor,
the logs look normal. maybe I've misinterpreted not opening the listening ports as not starting. I didn't check the actual systemd service status (silly me, I know). it's running now so next time I encounter this, I'll double check.
I also noticed in journalctl that it (Tor) wanted me to add 'ExitRelay 1' in my torrc to disable the exit relay warning and for future config requirements (it said). so i did that as well. all seems well as of now.
--
Thanks,
Fabian S.
OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC
On 21 Dec 2017, at 08:10, Fabian A. Santiago fsantiago@garbage-juice.com wrote:
December 20, 2017 3:32 PM, "teor" teor2345@gmail.com wrote:
On 21 Dec 2017, at 03:07, Fabian A. Santiago fsantiago@garbage-juice.com wrote:
I'm noticing that if i attempt to restart tor AFTER AccountingMax has been reached (meaning it's currently hibernating), tor itself fails to start.
What do you mean by "fails to start"? What are the log messages?
if i increase AccountingMax in torrc, then it restarts just fine.
normal?
It's hard to say, without any log messages.
Teor,
the logs look normal. maybe I've misinterpreted not opening the listening ports as not starting. I didn't check the actual systemd service status (silly me, I know). it's running now so next time I encounter this, I'll double check.
It is normal for Tor to close its listening ports when hibernating. It is normal for hibernation to persist across a restart.
If you check the logs, it probably says something about this on startup, and when it starts hibernating.
(When Tor doesn't have the right permissions to re-open these ports, the process will exit when it resumes from hibernation. That's a config issue, not a bug.)
I also noticed in journalctl that it (Tor) wanted me to add 'ExitRelay 1' in my torrc to disable the exit relay warning and for future config requirements (it said). so i did that as well. all seems well as of now.
T
-- Tim / teor
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n ------------------------------------------------------------------------
December 20, 2017 4:32 PM, "teor" teor2345@gmail.com wrote:
On 21 Dec 2017, at 08:10, Fabian A. Santiago fsantiago@garbage-juice.com wrote:
December 20, 2017 3:32 PM, "teor" teor2345@gmail.com wrote:
On 21 Dec 2017, at 03:07, Fabian A. Santiago fsantiago@garbage-juice.com wrote:
I'm noticing that if i attempt to restart tor AFTER AccountingMax has been reached (meaning it's currently hibernating), tor itself fails to start.
What do you mean by "fails to start"? What are the log messages?
if i increase AccountingMax in torrc, then it restarts just fine.
normal?
It's hard to say, without any log messages.
Teor,
the logs look normal. maybe I've misinterpreted not opening the listening ports as not starting. I didn't check the actual systemd service status (silly me, I know). it's running now so next time I encounter this, I'll double check.
It is normal for Tor to close its listening ports when hibernating. It is normal for hibernation to persist across a restart.
If you check the logs, it probably says something about this on startup, and when it starts hibernating.
(When Tor doesn't have the right permissions to re-open these ports, the process will exit when it resumes from hibernation. That's a config issue, not a bug.)
I also noticed in journalctl that it (Tor) wanted me to add 'ExitRelay 1' in my torrc to disable the exit relay warning and for future config requirements (it said). so i did that as well. all seems well as of now.
T
-- Tim / teor
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
so how i first noticed was when i couldn't browse to my dirport readme html page after a tor restart. are you saying when it normally hibernates, that page goes down too?
--
Thanks,
Fabian S.
OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC
On 21 Dec 2017, at 08:39, Fabian A. Santiago fsantiago@garbage-juice.com wrote:
December 20, 2017 4:32 PM, "teor" teor2345@gmail.com wrote:
On 21 Dec 2017, at 08:10, Fabian A. Santiago fsantiago@garbage-juice.com wrote:
December 20, 2017 3:32 PM, "teor" teor2345@gmail.com wrote:
On 21 Dec 2017, at 03:07, Fabian A. Santiago fsantiago@garbage-juice.com wrote:
I'm noticing that if i attempt to restart tor AFTER AccountingMax has been reached (meaning it's currently hibernating), tor itself fails to start.
What do you mean by "fails to start"? What are the log messages?
if i increase AccountingMax in torrc, then it restarts just fine.
normal?
It's hard to say, without any log messages.
Teor,
the logs look normal. maybe I've misinterpreted not opening the listening ports as not starting. I didn't check the actual systemd service status (silly me, I know). it's running now so next time I encounter this, I'll double check.
It is normal for Tor to close its listening ports when hibernating. It is normal for hibernation to persist across a restart.
If you check the logs, it probably says something about this on startup, and when it starts hibernating.
(When Tor doesn't have the right permissions to re-open these ports, the process will exit when it resumes from hibernation. That's a config issue, not a bug.)
I also noticed in journalctl that it (Tor) wanted me to add 'ExitRelay 1' in my torrc to disable the exit relay warning and for future config requirements (it said). so i did that as well. all seems well as of now.
so how i first noticed was when i couldn't browse to my dirport readme html page after a tor restart. are you saying when it normally hibernates, that page goes down too?
Yes.
When Tor hibernates, it doesn't send or receive any data. That includes ORPort and DirPort requests.
T
-- Tim / teor
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n ------------------------------------------------------------------------
December 20, 2017 4:44 PM, "teor" teor2345@gmail.com wrote:
On 21 Dec 2017, at 08:39, Fabian A. Santiago fsantiago@garbage-juice.com wrote:
December 20, 2017 4:32 PM, "teor" teor2345@gmail.com wrote:
On 21 Dec 2017, at 08:10, Fabian A. Santiago fsantiago@garbage-juice.com wrote:
December 20, 2017 3:32 PM, "teor" teor2345@gmail.com wrote:
On 21 Dec 2017, at 03:07, Fabian A. Santiago fsantiago@garbage-juice.com wrote:
I'm noticing that if i attempt to restart tor AFTER AccountingMax has been reached (meaning it's currently hibernating), tor itself fails to start. What do you mean by "fails to start"? What are the log messages?
if i increase AccountingMax in torrc, then it restarts just fine.
normal? It's hard to say, without any log messages.
Teor,
the logs look normal. maybe I've misinterpreted not opening the listening ports as not starting. I didn't check the actual systemd service status (silly me, I know). it's running now so next time I encounter this, I'll double check.
It is normal for Tor to close its listening ports when hibernating. It is normal for hibernation to persist across a restart.
If you check the logs, it probably says something about this on startup, and when it starts hibernating.
(When Tor doesn't have the right permissions to re-open these ports, the process will exit when it resumes from hibernation. That's a config issue, not a bug.)
I also noticed in journalctl that it (Tor) wanted me to add 'ExitRelay 1' in my torrc to disable the exit relay warning and for future config requirements (it said). so i did that as well. all seems well as of now.
so how i first noticed was when i couldn't browse to my dirport readme html page after a tor restart. are you saying when it normally hibernates, that page goes down too?
Yes.
When Tor hibernates, it doesn't send or receive any data. That includes ORPort and DirPort requests.
T
-- Tim / teor
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
That makes me sad, :-( ;-)
Many thanks.
--
Thanks,
Fabian S.
OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC
On 20. Dec 2017, at 22:46, Fabian A. Santiago fsantiago@garbage-juice.com wrote:
so how i first noticed was when i couldn't browse to my dirport readme html page after a tor restart. are you saying when it normally hibernates, that page goes down too?
Yes.
When Tor hibernates, it doesn't send or receive any data. That includes ORPort and DirPort requests.
That makes me sad, :-( ;-)
It's the only sensible way Tor can try and limit the bandwidth usage. Someone repeatedly fetching the page could make you waste tons of bandwidth otherwise.
Cheers Sebastian
On December 21, 2017 4:26:11 AM EST, Sebastian Hahn mail@sebastianhahn.net wrote:
On 20. Dec 2017, at 22:46, Fabian A. Santiago
fsantiago@garbage-juice.com wrote:
so how i first noticed was when i couldn't browse to my dirport
readme html page after a tor
restart. are you saying when it normally hibernates, that page goes
down too?
Yes.
When Tor hibernates, it doesn't send or receive any data. That includes ORPort and DirPort requests.
That makes me sad, :-( ;-)
It's the only sensible way Tor can try and limit the bandwidth usage. Someone repeatedly fetching the page could make you waste tons of bandwidth otherwise.
Cheers Sebastian _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
I gotcha. That makes sense. No worries here. Thanks. --
Thanks,
Fabian S.
OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC
tor-relays@lists.torproject.org
-
Fabian A. Santiago -
Sebastian Hahn -
teor