--- Please enter the report below this line. --- Since one of the latest system upgrades, mediatomb has ceased to work, not even with "service mediatomb restart" as some previous report stated. Output of "service mediatomb status" follows: ● mediatomb.service - UPnP MediaServer Loaded: loaded (/lib/systemd/system/mediatomb.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since mar 2015-10-27 16:30:21 WET; 11min ago Process: 15963 ExecStopPost=/sbin/ifconfig $MT_INTERFACE -allmulti (code=exited, status=0/SUCCESS) Process: 15960 ExecStopPost=/sbin/route del -net 239.0.0.0 netmask 255.0.0.0 (code=exited, status=0/SUCCESS) Process: 15951 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: 15948 ExecStartPre=/sbin/ifconfig $MT_INTERFACE allmulti (code=exited, status=0/SUCCESS) Process: 15945 ExecStartPre=/sbin/route add -net 239.0.0.0 netmask 255.0.0.0 $MT_INTERFACE (code=exited, status=0/SUCCESS) Process: 15942 ExecStartPre=/bin/grep -q MT_USER /etc/default/mediatomb (code=exited, status=0/SUCCESS) Main PID: 15952 (code=exited, status=1/FAILURE) oct 27 16:30:21 ... systemd[1]: Starting UPnP MediaServer... oct 27 16:30:21 ... systemd[1]: Started UPnP MediaServer. oct 27 16:30:21 ... systemd[1]: mediatomb.service: Main process exited, code=exited, status=1/FAILURE oct 27 16:30:21 ... systemd[1]: mediatomb.service: Unit entered failed state. oct 27 16:30:21 ... systemd[1]: mediatomb.service: Failed with result 'exit- code'. Debian Release: stretch/sid 900 testing security.debian.org 900 testing ftp.es.debian.org 500 wily ppa.launchpad.net 500 unstable ftp.es.debian.org 500 trusty ppa.launchpad.net 500 stable update.devolo.com 500 stable kxstudio.linuxaudio.org 500 stable dl.google.com 500 sid linux.dropbox.com 500 lucid ppa.launchpad.net 500 gcc5 kxstudio.linuxaudio.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty.
severity 803173 important Yesterday, I built mediatomb/unstable for Jessie and tested it on my system, which I had just upgraded from Wheezy. It started up successfully, and seems to work as well as the Wheezy version did. It seems safe to assume that the original reporter assigned a severity of grave based on the wording[1] that the bug "makes the package in question unusable or mostly so". However, given that the package has worked for me on a vanilla installation of Debian Jessie (no external sources defined), the bug no longer meets that criterion. I think the most appropriate severity would be "important". Simon [1] https://www.debian.org/Bugs/Developer#severities
Hi Antonio, as a fellow Debian user and mediatomb user, I backported the current version of the mediatomb package from unstable to Jessie and tried it on a system I'd recently upgraded to Jessie. It seemed to work fine for me without any problems, so I've changed the severity of this bug to 'important'. In the unlikely case that it's still available, can you include the contents of your /var/log/mediatomb log file in the report? It may explain why it's failing to start up.
Oops, my mistake, I accidentally sent the first message to the bug's email instead of to control, let me try again.
Hi Antonio, I'm forwarding Simon's email to you concerning this bugreport. I've just installed mediatomb on a machine running unstable, and it seems to work OK there. Providing both /var/log/mediatomb and /etc/default/mediatom would be a great help in finding out what's gone wrong on your machine. Thanks, James
Hi James, First of all I must apologize for having unadvertently overlooked your response for so long. Sometime in the middle the issue has dissappeared and I can now start the service. However it never autostarts after system reboot/poweroff. service mediatomb status: Loaded: loaded (/lib/systemd/system/mediatomb.service; disabled; vendor preset: enabled) I always have to manually start the service and log spits: 2016-03-19 14:58:06 INFO: Configuration check succeeded. Lots of... Any idea? Regards, Antonio El Miércoles, 23 de marzo de 2016 00:36:01 James Cowgill escribió:
I think having to start the service manually is a separate bug which I've filed as #823153. As a workaround you can run "systemctl enable mediatomb". [...] I don't know what's wrong there I'm afraid (and I don't use mediatomb that much). Have you checked the config files to see why mediatomb is reading those files (/usr/local/share/datos is a strange directory name) and does the file actually exist? Thanks, James
Nice. It works! No, that file does not exist but that directory does as it is a custom path of my own. I think it could be some kind of a leftover temp file so I guess mediatomb somehow has kept it recorded in its database and didn't wiped it out. I should look for some option to flush the DB. Thanks again for your help, Antonio
Dear Customer, Your item has arrived at the USPS Post Office at January 03, but the courier was unable to deliver parcel to you. Please review delivery label in attachment! Thank you for your consideration, Freddie Stephenson, USPS Parcels Delivery Clerk.