Description of problem: mediatomb is not listening on configured port, and on the 49152 port is not accepting user login. Version-Release number of selected component (if applicable): Name : mediatomb Version : 0.12.1 Release : 23.fc17 Architecture: x86_64 How reproducible: always Steps to Reproduce: 1. yum install mediatomb 2. edit /etc/mediatomb to set MT_INTERFACE (wlan0 for me) 3. service mediatomb start Actual results: Although the cmdline (as seen by /proc/<pid>/cmdline) is /usr/bin/mediatomb-d-umediatomb-gmediatomb-P/run/mediatomb.pid-l/var/log/mediatomb-m/etc-fmediatomb-p50500-ewlan0 no one is listening on 50500 (as "netstat -nap | grep 50500" shows, so it's not an iptables issue), and according to the /var/log/mediatomb.log file: 2013-03-03 13:08:21 INFO: Configuration check succeeded. 2013-03-03 13:08:21 INFO: Initialized port: 49152 2013-03-03 13:08:21 INFO: Server bound to: 192.168.1.117 2013-03-03 13:08:21 INFO: MediaTomb Web UI can be reached by following this link: 2013-03-03 13:08:21 INFO: http://192.168.1.117:49152/ Worse, accessing the provided URL on 49152 port shows a login, which does not accept mediatomb/mediatomb (which are encoded in the /etc/mediatomb/config.xml file) Even changing "accounts-enabled="no"" to "yes" in the config.xml does not allow for login. The web interface (on :49152) silenty does nothing after mediatomb/mediatomb is entered. Expected results: Previously, it worked like a charm, and by accessing the :50500 port I was able to add shares to the DLNA server.
I've downgraded to: Name : mediatomb Version : 0.12.1 Release : 16.fc17 Architecture: x86_64 Then, by looking at /usr/lib/systemd/system/mediatomb.service, I've noticed that "eth0" is hardcoded in the ExecStartPre script. It should use the same value as the MT_INTERFACE in the /etc/mediatomb.conf file.
Yeah I downgraded to mediatomb-0.12.1-16.fc17.x86_64 as well - fixes ignoring port (from both commandline option and config file)
Currently awaiting bunding exception for libupnp from FPC.
mediatomb-0.12.1-25.fc19.20120403gitb66dc1 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/mediatomb-0.12.1-25.fc19.20120403gitb66dc1
mediatomb-0.12.1-25.fc18.20120403gitb66dc1 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/mediatomb-0.12.1-25.fc18.20120403gitb66dc1
mediatomb-0.12.1-25.fc17.20120403gitb66dc1 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/mediatomb-0.12.1-25.fc17.20120403gitb66dc1
Package mediatomb-0.12.1-25.fc19.20120403gitb66dc1: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mediatomb-0.12.1-25.fc19.20120403gitb66dc1' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-4901/mediatomb-0.12.1-25.fc19.20120403gitb66dc1 then log in and leave karma (feedback).
mediatomb-0.12.1-25.fc18.20120403gitb66dc1 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
mediatomb-0.12.1-25.fc17.20120403gitb66dc1 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
mediatomb-0.12.1-25.fc19.20120403gitb66dc1 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.