[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-talk] Error binding network socket: Address already in use



Hi,

I see a lot of scary warnings in the Tor logs on our high bandwidth
nodes (>400 Mbps): "Error binding network socket: Address already in use".

All servers are configured equally, running multiple Tor processes. I
also apply sysctl tweaks, see
http://www.torservers.net/misc/config/sysctl.conf

I would appreciate if someone could help diagnose the problem. Find me
on IRC (nickname gamambel/gamamb) or Jabber (same as email address).

DirPorts are bound to local ports and Lighttpd is used as a reverse
proxy to tunnel requests on all IPs to one DirPort.

Example torrc:

------ snip ------
Nickname chomsky
ORPort 443
DirPort 80
Address 77.247.181.162
OutboundBindAddress 77.247.181.162
ORListenAddress 77.247.181.162:443
DirListenAddress 127.0.0.1:9030

DataDirectory /var/lib/tor/0
PidFile /var/run/tor/tor0.pid
Log notice file /var/log/tor/notices0.log

RelayBandwidthRate 80 MBytes
RelayBandwidthBurst 125 MBytes
MyFamily [...]

NumCPUs 4
ContactInfo [...]

CellStatistics 1
DirReqStatistics 1
EntryStatistics 1
ExitPortStatistics 1
ExtraInfoStatistics 1

HidServDirectoryV2 1
SocksPort 0
SocksPolicy reject *
RunAsDaemon 1
RefuseUnknownExits 1

ExitPolicy reject *:25, accept *:*
------ snip ------

-- 
Moritz Bartl
https://www.torservers.net/
_______________________________________________
tor-talk mailing list
tor-talk@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk