Bug#803173: [mediatomb] Cannot start
Antonio Marcos López Alonso
amlopezalonso at gmail.com
Sun May 1 17:56:36 UTC 2016
>
> > 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".
>
Nice. It works!
> > 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?
>
> Thanks,
> James
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
More information about the pkg-multimedia-maintainers
mailing list