Mediatomb dissapearing

  • rama00

    rama00 - 2012-01-07

    Hi All,

    I am running Mediatomb on Ubuntu. My setup works fine for several hours/days and then for no reason Mediatomb seems to stop working. When the problem occurs MediaTomb Service is running, but my renderer devices (Samsung TV, Windows PC, Ipad, …) does not show it anymore. At the same time webinterface stops working anymore.

    Info about system and version:
    $ mediatomb -version
    MediaTomb UPnP Server version 0.12.1 -
    $ uname -a
    Linux M350 3.0.0-12-generic-pae #20-Ubuntu SMP Fri Oct 7 16:37:17 UTC 2011 i686 i686 i386 GNU/Linux

    When the problem occurs Mediatomb is still running - I run service in debugmode and bind to eth0
    ps -efl | grep mediatomb
    4 S 105       4714     1  0  80   0 - 39476 futex_ 09:20 ?        00:00:57 mediatomb -c /etc/mediatomb/config.xml -u mediatomb -g mediatomb -l /var/log/mediatomb.log -e eth0 -D

    Debuglogging shows nothing special when Mediatomb hangs - it just seems sleeping - last lines of the log below;
    2012-01-06 11:38:58   DEBUG:  addTimerSubscriber(): adding subscriber…
    2012-01-06 11:38:58   DEBUG:  triggerWait(): triggerWait. -  3 subscriber(s)
    2012-01-06 11:38:58   DEBUG:  triggerWait(): sleeping..

    When the problem occurs mediatomb process is listening on correct ports:
    $ sudo netstat -nlp | grep 49152
    password for bdauwe:
    tcp        0      0 *               LISTEN      4714/mediatomb
    $ sudo netstat -nlp | grep 1900
    udp   114624      0  *                           4714/mediatomb

    First I thought this might be a problem that is reported sometimes where Mediatomb does not respond to M-SEARCH requests from the renderer. Thats why I added "allmulti" to my eth0.

    $ ifconfig
    eth0      Link encap:Ethernet  HWaddr 00:27:0e:02:81:c3
              inet addr:  Bcast:  Mask:
              inet6 addr: fe80::227:eff:fe02:81c3/64 Scope:Link
              RX packets:106943389 errors:0 dropped:0 overruns:0 frame:0
              TX packets:165656970 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:3274624943 (3.2 GB)  TX bytes:2385737013 (2.3 GB)
              Interrupt:44 Base address:0x6000

    Added also "route add -net netmask eth0"
    $ route
    Kernel IP routing table
    Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
    default         UG    100    0        0 eth0
    localnet        *        U     0      0        0 eth0       *            U     0      0        0 eth0

    The problem does occur even when I bring down my firewall (ufw). As the service and the webui are working fine I suppose this can not be a config problem or firewall or… I have no idea what triggers the problem.

    When I sniff my eth0 with wireshark - on the machine that is running Mediatomb ofcourse - I can see M-SEARCH packets arrive:
    490 37.505686 SSDP 188 M-SEARCH * HTTP/1.1
    but Mediatomb does not respond.

    When I do the same test when Mediatomb is working fine I normal receive an answer on the M-SEARCH * HTTP/1.1 packet - something like;
    491 37.506672 UDP 551 Source port: 35873  Destination port: blackjack.

    When I restart the mediatomb service the problem is resolved - webui is reachable again and renderer devices show mediatomb again for a few hours/days.

    Any help is appreciated. I am willing to do more debugging but will need guidance or a direction.

    PS: I also run another UpnP server, Logitech Media Server, formely Squeezebox Server on the same machine, but even when I bring down this service Mediatomb does not respond.

    • amikolajczyk

      amikolajczyk - 2013-08-22

      I know this is an older thread, but I was really hoping you might be able to share what you discovered about this. I'm having the exact same issue here. Debug logging shows nothing, the process is running, the port is listening, but the service is essentially dead. This seems to happen on the order of 8-12 hours. Restarting the service doesn't immediately fix it, as it comes back up in a maintenance state, which I then have to send a "clear" command to resume normal function.

      Thanks For anything you might be able to share!

  • Anonymous - 2012-09-21


    I've the exact same problem. Did you have any luck solving it?


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks