[SOLVED] Mediatomb: UPNP error 203 (Could not bind to socket)

[Jonathan_DS]

When trying to startup my application for streaming media to my network, I get the following output in my mediatomb logging:

2009-04-14 21:54:37 INFO: Loading configuration from: /etc/mediatomb/config.xml
2009-04-14 21:54:37 INFO: Checking configuration...
2009-04-14 21:54:37 INFO: Setting filesystem import charset to ANSI_X3.4-1968
2009-04-14 21:54:37 INFO: Setting metadata import charset to ANSI_X3.4-1968
2009-04-14 21:54:37 INFO: Setting playlist charset to ANSI_X3.4-1968
2009-04-14 21:54:37 INFO: Configuration check succeeded.
2009-04-14 21:54:37 ERROR: main: upnp error -203
2009-04-14 21:54:37 ERROR: Could not bind to socket.
2009-04-14 21:54:37 INFO: Please check if another instance of MediaTomb or
2009-04-14 21:54:37 INFO: another application is running on the same port.
2009-04-14 21:54:37 ERROR: upnp_cleanup: UpnpUnRegisterRootDevice failed

The configuration worked fine up until last week and I haven't changed anything that could have messed things up.

I have tried different things to solve the problem.

• Port forwarding on my router
• Changing the port that mediatomb uses
• Reinstalling mediatomb

I don't have any other applications running that could use the same port. I've checked with netstat which ports are active, but nothing that could point out the problem.

Any help would be appreciated!

I'm working on an AMD64 bit Gentoo-system.

[Touchtecservers]

Are you running it as root, and if not - is the port below above 1000?

I know very little about MediaTomb, and even less about uPNP, but I know that ports below 1000 or so are protected and only bindable by root.

[Jonathan_DS]

I'm sure I'm running this as root. Manual startup as root or sudo doesn't work either.

The port I use is 49152 (standard with media server applications like Mediatomb).

[angeloneacsu]

i had the same -203 problem about binding.
2009-10-08 14:28:25 INFO: Loading configuration from: /root/.mediatomb/config.xml
2009-10-08 14:28:25 INFO: Checking configuration...
2009-10-08 14:28:25 INFO: Setting filesystem import charset to UTF-8
2009-10-08 14:28:25 INFO: Setting metadata import charset to UTF-8
2009-10-08 14:28:25 INFO: Setting playlist charset to UTF-8
2009-10-08 14:28:25 INFO: Configuration check succeeded.
2009-10-08 14:28:25 ERROR: main: upnp error -203
2009-10-08 14:28:25 ERROR: Could not bind to socket.
2009-10-08 14:28:25 INFO: Please check if another instance of MediaTomb or
2009-10-08 14:28:25 INFO: another application is running on the same port.
2009-10-08 14:28:25 ERROR: upnp_cleanup: UpnpUnRegisterRootDevice failed

it seams like mediatomb needs itself a loopback network to be up in order to startup:


socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 4
bind(4, {sa_family=AF_INET, sin_port=htons(49152), sin_addr=inet_addr("0.0.0.0")}, 16) = 0
listen(4, 12 = 0
getsockname(4, {sa_family=AF_INET, sin_port=htons(49152), sin_addr=inet_addr("0.0.0.0")}, [16]) = 0
socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 5
bind(5, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("127.0.0.1")}, 16) = -1 EADDRNOTAVAIL (Cannot assign requested address)
shutdown(4, 2 /* send and receive */) = 0
close(4) = 0
shutdown(5, 2 /* send and receive */) = -1 ENOTCONN (Transport endpoint is not connected)


before running mediatomb i was playing with my network and somehow i disable the loopback interface (lo). after bringing it up everythings goes fine.

ifconfig lo up

2009-10-08 14:29:13 INFO: Loading configuration from: /root/.mediatomb/config.xml
2009-10-08 14:29:13 INFO: Checking configuration...
2009-10-08 14:29:13 INFO: Setting filesystem import charset to UTF-8
2009-10-08 14:29:13 INFO: Setting metadata import charset to UTF-8
2009-10-08 14:29:13 INFO: Setting playlist charset to UTF-8
2009-10-08 14:29:13 INFO: Configuration check succeeded.
2009-10-08 14:29:13 INFO: Initialized port: 49152
2009-10-08 14:29:13 INFO: Server bound to: 192.168.1.100

[Jonathan_DS]

Your reply made everything work again.
Thank you very much!

Due to lack of time I was unable to look into this more, and I gave up of finding the solution myself.