search

rix1337 / docker-ripper

The best way to automatically rip optical disks using docker!
MIT License
247 stars 50 forks source link

"Unexpected makemkvcon output:" in docker logs #113

Closed a113speederbot closed 8 months ago

a113speederbot commented 8 months ago

Have you read and understood this part of the readme?

[X ] YES

[] NO

Issue description:

Hello all,

I'm running ripper using docker on Debian (OpenMediaVault). It worked flawlessly when I first used it a couple of months ago but has suddenly stopped working today. It spins the disc up then is quiet for a matter of minutes, then ejects without ripping.

The container logs show this:

switches:
  -r --robot        - turn on "robot" mode, see http://www.makemkv.com/developers
*** Running /etc/my_init.d/web.sh...
Starting web ui
*** Booting runit daemon...
*** Runit started as PID 38
22.02.2024 13:02:25 : Starting Ripper. Optical Discs will be detected and ripped within 60 seconds.
Feb 22 13:02:26 d6d5b8fc9b40 cron[46]: (CRON) INFO (pidfile fd = 3)
Feb 22 13:02:26 d6d5b8fc9b40 cron[46]: (CRON) INFO (Skipping @reboot jobs -- not system startup)
22.02.2024 13:03:27 : Unexpected makemkvcon output: 
22.02.2024 13:04:28 : Unexpected makemkvcon output: 

END OF LINE

Any guidance for the noob would be very much appreciated.

a113speederbot commented 8 months ago

I fixed it by deleting the container and the image and then running docker compose up Just delighted to have this working again, hopefully this may help somebody else. Thank you @rix1337 for such an awesome container!!

Marking as closed.