To not duplicate with bug, I'm attaching my problem related to mediatomb 
startup.
My 'interface' file is:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

in /etc/defaults/mediatomb I have line:
MT_INTERFACE="eth0"

After boot I'm checking status of mediatomb, because it doesn't start:

root@alfa-nas:~# systemctl status mediatomb
● mediatomb.service - UPnP MediaServer
   Loaded: loaded (/lib/systemd/system/mediatomb.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: resources) since czw 2015-06-18 13:54:13 CEST; 1min 
17s ago
  Process: 757 ExecStart=/usr/bin/mediatomb -d -u $MT_USER -g $MT_GROUP -P 
/run/mediatomb.pid -l $MT_LOGFILE -m $MT_HOME -f $MT_CFGDIR -p $MT_PORT -e 
$MT_INTERFACE (code=exited, status=0/SUCCESS)
  Process: 731 ExecStartPre=/sbin/ifconfig $MT_INTERFACE allmulti (code=exited, 
status=0/SUCCESS)
  Process: 626 ExecStartPre=/sbin/route add -net 239.0.0.0 netmask 255.0.0.0 
$MT_INTERFACE (code=exited, status=7)
  Process: 587 ExecStartPre=/bin/grep -q MT_USER /etc/default/mediatomb 
(code=exited, status=0/SUCCESS)

cze 18 13:54:09 alfa-nas systemd[1]: Starting UPnP MediaServer...
cze 18 13:54:09 alfa-nas route[626]: SIOCADDRT: Network is down
cze 18 13:54:13 alfa-nas systemd[1]: PID 1171 read from file /run/mediatomb.pid 
does not exist or is a zombie.
cze 18 13:54:13 alfa-nas systemd[1]: Failed to start UPnP MediaServer.
cze 18 13:54:13 alfa-nas systemd[1]: Unit mediatomb.service entered failed 
state.
cze 18 13:54:13 alfa-nas systemd[1]: mediatomb.service failed.

Then I'm restarting mediatomb:

root@alfa-nas:~# systemctl restart mediatomb

No errors, so time to check status:

root@alfa-nas:~# systemctl status mediatomb
● mediatomb.service - UPnP MediaServer
   Loaded: loaded (/lib/systemd/system/mediatomb.service; enabled; vendor 
preset: enabled)
   Active: active (running) since czw 2015-06-18 13:55:55 CEST; 2s ago
  Process: 1738 ExecStart=/usr/bin/mediatomb -d -u $MT_USER -g $MT_GROUP -P 
/run/mediatomb.pid -l $MT_LOGFILE -m $MT_HOME -f $MT_CFGDIR -p $MT_PORT -e 
$MT_INTERFACE (code=exited, status=0/SUCCESS)
  Process: 1735 ExecStartPre=/sbin/ifconfig $MT_INTERFACE allmulti 
(code=exited, status=0/SUCCESS)
  Process: 1731 ExecStartPre=/sbin/route add -net 239.0.0.0 netmask 255.0.0.0 
$MT_INTERFACE (code=exited, status=0/SUCCESS)
  Process: 1730 ExecStartPre=/bin/grep -q MT_USER /etc/default/mediatomb 
(code=exited, status=0/SUCCESS)
 Main PID: 1741 (mediatomb)
   CGroup: /system.slice/mediatomb.service
           └─1741 /usr/bin/mediatomb -d -u mediatomb -g mediatomb -P 
/run/mediatomb.pid -l /var/log/mediatomb -m /etc -f mediatomb -p 60000 -e...

cze 18 13:55:55 alfa-nas systemd[1]: Starting UPnP MediaServer...
cze 18 13:55:55 alfa-nas systemd[1]: Started UPnP MediaServer.

Regards


Tom

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1453602

Title:
  mediatomb starts before network comes online

Status in mediatomb package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  New

Bug description:
  mediatomb fails to start at boot because the network is not yet up.
  It's unit file lists After: network-online.target, but this target
  comes up before NetworkManager has brought the network up.  I'm
  guessing it only counts networks configured in /etc/interfaces.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mediatomb/+bug/1453602/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to