Init script not working because network interfaces are not ready

Bug #366866 reported by Juan Orti on 2009-04-25
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
mediatomb (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: mediatomb

I'm using Ubuntu Jaunty on AMD64, mediatomb 0.11.0-3ubuntu2

The problem is that mediatomb doesn't work for me by default. When I boot the computer I see this error in /var/log/mediatomb.log and mediatomb isn't running

2009-04-25 18:36:29 INFO: Loading configuration from: /etc/mediatomb/config.xml
2009-04-25 18:36:29 INFO: Checking configuration...
2009-04-25 18:36:29 INFO: Setting filesystem import charset to ANSI_X3.4-1968
2009-04-25 18:36:29 INFO: Setting metadata import charset to ANSI_X3.4-1968
2009-04-25 18:36:29 INFO: Setting playlist charset to ANSI_X3.4-1968
2009-04-25 18:36:29 INFO: Configuration check succeeded.
2009-04-25 18:36:29 ERROR: Could not determine interface address
2009-04-25 18:36:29 ERROR: Could not find interface: eth0

It seems that mediatomb starts too early, before the network is up. What I did is:

$ sudo update-rc.d -f mediatomb remove
$ sudo update-rc.d mediatomb defaults 99

Koen Beek (koen-beek) wrote :

I tried your suggested changes but I still get an error message (ERROR: main: upnp error -117) linked to the fact the network is not up yet

following workaround worked for me, but now the mediatomb server runs under my user which does not bother me but may not be what other people want

https://bugs.launchpad.net/ubuntu/+source/mediatomb/+bug/212441/comments/5

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in mediatomb (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers