I thought it might be nice to run a relay only node with ORPort 80 because it might make tor more available to some users where blocking occurs. And to limit unexpected expenses I calculated 220GB a week would be good. Now I have found out why running ORPort 80 with AccountingMax is a problem... Can I work around this issue of after hibernation the node won't bind to port 80? Or do I need to set it to something above port 1024, for example the default port 9001? Initial setup includes the following: ORPort 80 AccountingMax 220 GB AccountingStart week 7 00:00 After a few weeks running the node, day 7 of the week's AccountingMax Tor Weather reports Node Down! Date: Sat, 15 Nov 2014 15:52:45 -0000 Subject: [Tor Weather] Node Down! Nov 15 14:15:09.000 [notice] Bandwidth soft limit reached; commencing hibernation. No new connections will be accepted Nov 15 15:37:55.000 [notice] Heartbeat: Tor's uptime is 10 days 12:00 hours, with 68 circuits open. I've sent 315.47 GB and received 315.06 GB. We are currently hibernating. ... Nov 16 00:00:00.000 [notice] Hibernation period ended. Resuming normal activity. Nov 16 00:00:00.000 [notice] Opening Socks listener on 127.0.0.1:9050 Nov 16 00:00:00.000 [notice] Opening OR listener on 0.0.0.0:80 Nov 16 00:00:00.000 [warn] Could not bind to 0.0.0.0:80: Permission denied I restart the server, after a bit of downtime. [1]. Following week on day 5 of the AccountingStart week I am approaching the limit again and decide to try a daily AccountingMax, and then perhaps I could restart the server with cron at 5:01, but that isn't going work well with random hibernation. ORPort 198.211.99.146:80 IPv4Only AccountingMax 32 GB AccountingStart day 05:00 Then Node Down again, this time it happens right after the AccountingStart resets. Date: Fri, 21 Nov 2014 07:13:07 -0000 Subject: [Tor Weather] Node Down! Nov 21 05:00:00.000 [notice] Configured hibernation. This interval began at 2014-11-21 05:00:00; the scheduled wake-up time is 2014-11-21 06:20:24; we expect to exhaust our quota for this interval around 2014-11-22 04:16:24; the next interval begins at 2014-11-22 05:00:00 (all times local) Nov 21 05:00:01.000 [notice] Commencing hibernation. We will wake up at 2014-11-21 06:20:24 local time. Nov 21 05:00:01.000 [notice] Going dormant. Blowing away remaining connections. Nov 21 06:20:24.000 [notice] Hibernation period ended. Resuming normal activity. Nov 21 06:20:24.000 [notice] Opening Socks listener on 127.0.0.1:9050 Nov 21 06:20:24.000 [notice] Opening OR listener on 198.211.99.146:80 Nov 21 06:20:24.000 [warn] Could not bind to 198.211.99.146:80: Permission denied ... after logrotate runs Nov 21 07:46:25.000 [warn] Could not bind to 198.211.99.146:80: Permission denied Nov 21 07:46:25.000 [warn] Failed to parse/validate config: Failed to bind one of the listener ports. Nov 21 07:46:25.000 [err] Reading config failed--see warnings above. For usage, try -h. Nov 21 07:46:25.000 [warn] Restart failed (config error?). Exiting. I would like to run an exit node, but the advise seems to be try a relay only node for 6 months to a year first... It seems it might be more of an issue with expenses that might prevent me from running an exit node, or multiple nodes. I'l upgrade the VPS to the 2TB transfer, but that might be after the holidays. However I suspect that it will only be a matter of days or weeks before I run into the AccountingMax limits and that may preclude changing the configuration to be an exit node. 1. Downtime starting the 15th. eth0 08:59 ^ t | rt rt | rt rt rt | rt rt rt | t rt rt rt rt | rt rt rt rt rt rt | rt rt rt rt rt rt rt rt rt | rt rt rt rt rt rt rt rt rt rt rt | rt rt rt rt rt rt rt rt rt rt rt rt | rt rt rt rt rt rt rt rt rt rt rt rt -+---------------------------------------------------------------------------> | 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 00 01 02 03 04 05 06 07 08 h rx (KiB) tx (KiB) h rx (KiB) tx (KiB) h rx (KiB) tx (KiB) 09 1,380,268 1,409,649 17 1,244 2,753 01 3,117 6,815 10 1,383,154 1,407,057 18 1,100 1,720 02 161,632 164,035 11 1,143,056 1,163,393 19 706 228 03 1,564,910 1,578,327 12 1,920,541 1,953,502 20 127 201 04 1,036,805 1,054,792 13 2,719,316 2,742,037 21 675 222 05 1,630,340 1,644,128 14 854,474 869,997 22 124 150 06 3,189,069 3,215,147 15 81,036 82,419 23 732 324 07 2,952,173 2,999,409 16 52,548 52,515 00 6,367 2,718 08 2,115,794 2,150,727 ------------------------------------------------------------------------------- And some other stats that seem to follow the expected life cycle. day rx | tx | total | avg. rate ------------------------+-------------+-------------+--------------- 10/06/2014 28.32 MiB | 13.31 MiB | 41.63 MiB | 0.49 KiB/s 10/07/2014 37.10 MiB | 30.33 MiB | 67.43 MiB | 0.80 KiB/s 10/08/2014 200.13 MiB | 170.99 MiB | 371.12 MiB | 4.40 KiB/s 10/09/2014 194.58 MiB | 188.91 MiB | 383.49 MiB | 4.55 KiB/s 10/10/2014 578.48 MiB | 588.95 MiB | 1.14 GiB | 13.84 KiB/s 10/11/2014 1.09 GiB | 1.10 GiB | 2.19 GiB | 26.62 KiB/s 10/12/2014 1.34 GiB | 1.34 GiB | 2.68 GiB | 32.57 KiB/s 10/13/2014 977.57 MiB | 984.14 MiB | 1.92 GiB | 23.25 KiB/s 10/14/2014 1.68 GiB | 1.67 GiB | 3.34 GiB | 40.56 KiB/s 10/15/2014 1.35 GiB | 1.36 GiB | 2.71 GiB | 32.91 KiB/s 10/16/2014 8.49 GiB | 8.58 GiB | 17.07 GiB | 207.20 KiB/s 10/17/2014 11.88 GiB | 12.02 GiB | 23.91 GiB | 290.15 KiB/s 10/18/2014 13.33 GiB | 13.55 GiB | 26.88 GiB | 326.25 KiB/s 10/19/2014 15.95 GiB | 16.19 GiB | 32.15 GiB | 390.12 KiB/s 10/20/2014 12.34 GiB | 12.53 GiB | 24.87 GiB | 301.83 KiB/s 10/21/2014 17.41 GiB | 17.68 GiB | 35.10 GiB | 425.94 KiB/s 10/22/2014 23.84 GiB | 24.21 GiB | 48.04 GiB | 583.08 KiB/s 10/23/2014 26.52 GiB | 26.93 GiB | 53.46 GiB | 648.77 KiB/s 10/24/2014 26.19 GiB | 26.60 GiB | 52.79 GiB | 640.64 KiB/s 10/25/2014 24.77 GiB | 25.13 GiB | 49.89 GiB | 605.53 KiB/s 10/26/2014 32.19 GiB | 32.66 GiB | 64.86 GiB | 787.13 KiB/s 10/27/2014 28.44 GiB | 28.84 GiB | 57.28 GiB | 695.12 KiB/s 10/28/2014 24.39 GiB | 24.80 GiB | 49.19 GiB | 596.97 KiB/s 10/29/2014 23.66 GiB | 24.04 GiB | 47.70 GiB | 578.94 KiB/s 10/30/2014 26.16 GiB | 26.64 GiB | 52.80 GiB | 640.83 KiB/s 10/31/2014 24.48 GiB | 24.94 GiB | 49.42 GiB | 599.75 KiB/s 11/01/2014 26.62 GiB | 27.02 GiB | 53.64 GiB | 650.94 KiB/s 11/02/2014 26.65 GiB | 27.02 GiB | 53.67 GiB | 651.32 KiB/s 11/03/2014 25.09 GiB | 25.51 GiB | 50.60 GiB | 614.08 KiB/s 11/04/2014 25.06 GiB | 25.43 GiB | 50.49 GiB | 612.75 KiB/s 11/05/2014 27.74 GiB | 28.17 GiB | 55.91 GiB | 678.50 KiB/s 11/06/2014 23.62 GiB | 23.98 GiB | 47.61 GiB | 577.79 KiB/s 11/07/2014 26.63 GiB | 27.06 GiB | 53.69 GiB | 651.61 KiB/s 11/08/2014 30.29 GiB | 30.73 GiB | 61.02 GiB | 740.58 KiB/s 11/09/2014 30.93 GiB | 31.38 GiB | 62.32 GiB | 756.31 KiB/s 11/10/2014 37.56 GiB | 38.16 GiB | 75.72 GiB | 918.98 KiB/s 11/11/2014 33.97 GiB | 34.46 GiB | 68.43 GiB | 830.48 KiB/s 11/12/2014 37.92 GiB | 38.52 GiB | 76.45 GiB | 927.78 KiB/s 11/13/2014 32.15 GiB | 32.65 GiB | 64.80 GiB | 786.41 KiB/s 11/14/2014 36.32 GiB | 36.81 GiB | 73.14 GiB | 887.61 KiB/s 11/15/2014 25.40 GiB | 25.75 GiB | 51.15 GiB | 812.74 KiB/s 11/16/2014 44.23 GiB | 44.88 GiB | 89.11 GiB | 1.06 MiB/s 11/17/2014 44.96 GiB | 45.64 GiB | 90.60 GiB | 1.07 MiB/s 11/18/2014 48.38 GiB | 49.16 GiB | 97.53 GiB | 1.16 MiB/s 11/19/2014 51.38 GiB | 52.33 GiB | 103.71 GiB | 1.23 MiB/s 11/20/2014 43.68 GiB | 44.43 GiB | 88.11 GiB | 1.04 MiB/s 11/21/2014 5.52 GiB | 5.62 GiB | 11.14 GiB | 398.39 KiB/s Chuck