Bug#803173: [mediatomb] Cannot start
jcowgill at debian.org
Sun May 1 15:03:55 UTC 2016
On Sat, 2016-04-30 at 22:12 +0100, Antonio Marcos López Alonso wrote:
> 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:
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".
> 2016-03-19 14:58:06 INFO: Configuration check succeeded.
> 2016-03-19 14:58:06 INFO: Initialized port: 50500
> 2016-03-19 14:58:06 INFO: Server bound to: 192.168.1.36
> 2016-03-19 14:58:07 INFO: MediaTomb Web UI can be reached by following this link:
> 2016-03-19 14:58:07 INFO: http://192.168.1.36:50500/
> 2016-03-20 08:12:54 ERROR: Exception caught: Failed to stat /usr/local/share/datos/tmp/Incoming/tmp/001.part.met.backup , No existe el fichero o el directorio
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?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: This is a digitally signed message part
More information about the pkg-multimedia-maintainers