aMule Forum
English => aMule Help => Topic started by: seenxu on November 11, 2009, 11:30:10 PM
-
hey, guys.
I got a problem while launching amule daemon with "amuled -f" command, it always shows the following errors, then i can't connect to the daemon with amulecmd, it shows only "Creating client..." then freeze there. If I starts amule with gui in terminal, there is the same error message. only if I disable the upnp option, the error goes away.
CUPnPException: error(UpnpInit): Error code -203: UPNP_E_SOCKET_BIND.
sys spec:
* gentoo 2.6.31-gentoo-r5
* amule 2.2.6 built with USE flags "daemon geoip gtk nls remote stats unicode upnp"
* libupnp 1.6.6
-
UPNP_E_SOCKET_BIND [-203]
UPNP_E_SOCKET_BIND signifies that the SDK had a problem binding a socket to a network interface.
Usually socket bind error means that the port is already used by another application. Try changing the upnp port.
-
I had changed with several different ports, but it's still the same, only if I disable upnp the error goes away, and when I disabled the upnp the amulecmd still can't connect to amule daemon.
-
I take it you need UPNP for some specific reason.
I suggest you to use the "netstat" command to check if the port is used by any application. Do it like this (change 46000 to your port number!):
netstat -an|grep 46000
Is there any other error visible? Where do you set the port number? Could you give us a screenshot of it?
-
thx for your reply, next time when I have the same problem, I will try what you described here.