MediaTomb enters endless loop of crashing if permission to directory denied

Bug #1327553 reported by Filiprino on 2014-06-07
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mediatomb (Ubuntu)
Undecided
Unassigned

Bug Description

I installed mediatomb and configured it with the file I've attached to this bug report. Mediatomb fills the log file with permission denied messges, it can take gigabytes because if I don't stop the service it won't stop doing that.

The apport.log file shows the following text:
ERROR: apport (pid 1899) Sat Jun 7 15:05:53 2014: called for pid 1811, signal 11, core limit 0
ERROR: apport (pid 1899) Sat Jun 7 15:05:53 2014: executable: /usr/bin/mediatomb (command line "mediatomb -c /etc/mediatomb/config.xml -u mediatomb
 -g mediatomb -l /var/log/mediatomb.log")
ERROR: apport (pid 1899) Sat Jun 7 15:05:53 2014: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 1899) Sat Jun 7 15:05:54 2014: this executable already crashed 2 times, ignoring
ERROR: apport (pid 1916) Sat Jun 7 15:05:55 2014: called for pid 1901, signal 11, core limit 0
ERROR: apport (pid 1916) Sat Jun 7 15:05:55 2014: executable: /usr/bin/mediatomb (command line "mediatomb -c /etc/mediatomb/config.xml -u mediatomb
 -g mediatomb -l /var/log/mediatomb.log")
ERROR: apport (pid 1916) Sat Jun 7 15:05:55 2014: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 1916) Sat Jun 7 15:05:55 2014: this executable already crashed 2 times, ignoring
ERROR: apport (pid 1930) Sat Jun 7 15:05:56 2014: called for pid 1918, signal 11, core limit 0
ERROR: apport (pid 1930) Sat Jun 7 15:05:56 2014: executable: /usr/bin/mediatomb (command line "mediatomb -c /etc/mediatomb/config.xml -u mediatomb
 -g mediatomb -l /var/log/mediatomb.log")
ERROR: apport (pid 1930) Sat Jun 7 15:05:56 2014: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 1930) Sat Jun 7 15:05:56 2014: this executable already crashed 2 times, ignoring
ERROR: apport (pid 1944) Sat Jun 7 15:05:58 2014: called for pid 1932, signal 11, core limit 0
ERROR: apport (pid 1944) Sat Jun 7 15:05:58 2014: executable: /usr/bin/mediatomb (command line "mediatomb -c /etc/mediatomb/config.xml -u mediatomb
 -g mediatomb -l /var/log/mediatomb.log")
ERROR: apport (pid 1944) Sat Jun 7 15:05:58 2014: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 1944) Sat Jun 7 15:05:58 2014: this executable already crashed 2 times, ignoring
ERROR: apport (pid 1962) Sat Jun 7 15:05:59 2014: called for pid 1946, signal 11, core limit 0
ERROR: apport (pid 1962) Sat Jun 7 15:05:59 2014: executable: /usr/bin/mediatomb (command line "mediatomb -c /etc/mediatomb/config.xml -u mediatomb
 -g mediatomb -l /var/log/mediatomb.log")

The MediaTomb log file shows the following messages:

2014-06-07 15:05:52 INFO: Loading configuration from: /etc/mediatomb/config.xml
2014-06-07 15:05:52 INFO: Checking configuration...
2014-06-07 15:05:52 INFO: Setting filesystem import charset to UTF-8
2014-06-07 15:05:52 INFO: Setting metadata import charset to UTF-8
2014-06-07 15:05:52 INFO: Setting playlist charset to ANSI_X3.4-1968
2014-06-07 15:05:52 WARNING: You enabled the YouTube feature, which allows you
                             to watch YouTube videos on your UPnP device!
                             Please check http://www.youtube.com/t/terms
                             By using this feature you may be violating YouTube
                             service terms and conditions!

2014-06-07 15:05:52 INFO: Configuration check succeeded.
2014-06-07 15:05:52 INFO: Initialized port: 49152
2014-06-07 15:05:52 INFO: Server bound to: 192.168.1.3
2014-06-07 15:05:53 INFO: MediaTomb Web UI can be reached by following this link:
2014-06-07 15:05:53 INFO: http://192.168.1.3:49152/
2014-06-07 15:05:53 WARNING: Cannot add inotify watch for /home/filiprino/Vídeos/: Permission denied
2014-06-07 15:05:53 WARNING: Cannot add inotify watch for /home/filiprino/Vídeos//: Permission denied
2014-06-07 15:05:53 WARNING: Cannot add inotify watch for /home/filiprino/Vídeos//: Permission denied
2014-06-07 15:05:53 WARNING: Cannot add inotify watch for /home/filiprino/Vídeos//: Permission denied

I was using MediaTomb on Ubuntu 13.10 with the same config file and I had no problems. A pair of messages with the permission denied WARNING and that's all. But with the version included in Ubuntu 14.04 MediaTomb enters a loop of crashes printing that message instead of warning you and continue running.

I made a Ubuntu 14.04 fresh install and only restored my /home (partially, no "." directories except .local, .mozilla and .thunderbird) and the /etc/group, /etc/shadow files along with some .desktop.
I checked group and shadow numbers and corrected them to match the files in the Ubuntu live image.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: mediatomb 0.12.1-5ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Jun 7 15:10:36 2014
InstallationDate: Installed on 2014-06-05 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
SourcePackage: mediatomb
UpgradeStatus: No upgrade log present (probably fresh install)

Filiprino (filiprino) wrote :
Filiprino (filiprino) wrote :

I ran the program interactively and redirected the error output to a file. I'm attaching that output to this comment.

Mediatomb ends closing itself without further information.

Filiprino (filiprino) wrote :

I commented those directories out of the config files and mediatomb is working well now.

As the version number is the same on both Ubuntu 13.10 and 14.04 maybe the problem is related to the Linux kernel and the inotify system.

Tim Ritberg (xpert-reactos) wrote :

I discoverd a problem with upstart/init scripts.
The stop part is not working because it can not find this "job":
service mediatomb stop

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers