Either mediatomb-daemon.mediatomb.default or mediatomb-daemon.mediatomb.logrotate should be updated so they both call the logfile with the same filename! Take your pick how the logfile should be named but make it consistent across the startup and logrotate configuration files :-)
Please fix asap now that the fix is finally identified, the bug has been open for too many years.
There is a simple configuration bug, seeing it in 16.04 and 17.10 so it's everywhere.
The fix is VERY SIMPLE TOO.
The logrotate config script wants to rotate logfile: /var/log/ mediatomb. log
But mediatomb is run with -l /var/log/mediatomb
The package maintainer should make them consistent. I downloaded the source and see this:
mediatomb- 0.12.1- 47-g7ab7616$ grep -r log/mediatomb . mediatomb- conf-fedora: MT_LOGFILE= "/var/log/ mediatomb" mediatomb- conf-optware: MT_LOGFILE= "/opt/var/ log/mediatomb" mediatomb- daemon. mediatomb. default: MT_LOGFILE= "/var/log/ mediatomb" mediatomb- daemon. mediatomb. upstart: env LOGFILE= /var/log/ mediatomb. log mediatomb- daemon. mediatomb. logrotate: "/var/log/ mediatomb. log" { mediatomb- daemon. postrm: rm -rf /var/log/mediatomb /var/log/mediatomb* \ spec.in: /var/log/ mediatomb {
./config/
./config/
./debian/
./debian/
./debian/
./debian/
./mediatomb.
Either mediatomb- daemon. mediatomb. default or mediatomb- daemon. mediatomb. logrotate should be updated so they both call the logfile with the same filename! Take your pick how the logfile should be named but make it consistent across the startup and logrotate configuration files :-)
Please fix asap now that the fix is finally identified, the bug has been open for too many years.