On Fri, 11 Nov 2005, Jari Aalto wrote:
> Nov 10 10:34:08.189 [notice] Tor 0.1.0.15 opening log file.
> Nov 10 10:34:08.190 [notice] Initialized libevent version 1.1a using
> method epoll
> Nov 10 10:34:08.192 [warn] connection_create_listener(): Could not bind
> to port 9050: Cannot assign requested address
> Nov 10 10:34:08.193 [err] options_act(): Failed to bind one of the
> listener ports.
> Nov 10 10:34:08.193 [err] init_from_config(): Acting on config options
> left us in a broken state. Dying.
>
> However it was not obvious what was wrong so I ran strace, which
> showed:
>
> 19377 bind(8, {sa_family=AF_INET, sin_port=htons(9050),
> sin_addr=inet_addr("192.168.1.3")}, 16) = -1 EADDRNOTAVAIL (Cannot assign
> requested address)
>
> I had put
>
> SocksBindAddress 192.168.1.3
>
> In there by mistake. The "HOST" is known by 192.168.1.2 and 127.0.0.1,
> so this was the reason for EADDRNOTAVAIL.
>
> SUGGESTION:
>
> could the error bessage display the IP it tries to bind along with a
> hint. Something like: "I can only bind local addresses, does this ip
> belog to this host?"
"Cannot assign requested address" is what strerror says, it's not like
the Tor developers picked it.
In 0.1.1.x the error message also includes the IP address, so I guess
that's good enough too.
./src/or/connection.c: warn(LD_NET, "Could not bind to %s:%u: %s", address,
usePort,
--
PGP signed and encrypted | .''`. ** Debian GNU/Linux **
messages preferred. | : :' : The universal
| `. `' Operating System
http://www.palfrader.org/ | `- http://www.debian.org/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
