docker-makemkv
docker-makemkv copied to clipboard
Rip will hang, can't stop container.
I've had this happen a couple times now.
Progress will get stuck at some point. Nothing in the logs showing any error.
I try to stop the container and it sends the the various stop commands, but then I still see the container running.
Then I tried to kill the container, and it still won't stop. Still shows as running. Can't remove either.
Last time this happened I stopped docker and removed the individual container, but when I restarted docker all my containers were gone and had to re-run all my composes (fine). Not sure what better process there is for fixing an errant container.
I'm going to just let it stay in this state until you get back to me so I can pull any logs/data for you. Get back to me asap if you can.
` [services.d] stopping services
[services.d] stopping app...
[services.d] stopping logmonitor...
[services.d] stopping x11vnc...
caught signal: 15
04/10/2021 10:22:27 deleted 40 tile_row polling images.
04/10/2021 10:22:27 Restored X server key autorepeat to: 1
[services.d] stopping statusmonitor...
[services.d] stopping openbox...
[services.d] stopping xvfb...
yad: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
[services.d] stopping certsmonitor...
[services.d] stopping autodiscripper...
[services.d] stopping nginx...
[services.d] stopping s6-fdholderd...
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.`
Does it eventually recover ? It may take a while for MakeMKV to stop.
Is your drive connected through USB or SATA ?
You can also try to enable debug log messages from MakeMKV preferences to see if we can get more details.
It did not recover. USB.
I had it happen a few more times, and each time I couldn't figure out a way to stop the container that didn't involve restarting my machine. Restarting the docker daemon wouldn't work.
It did not recover. USB.
I had it happen a few more times, and each time I couldn't figure out a way to stop the container that didn't involve restarting my machine. Restarting the docker daemon wouldn't work.
Force stop the container from the same menu you start it from
It did not recover. USB. I had it happen a few more times, and each time I couldn't figure out a way to stop the container that didn't involve restarting my machine. Restarting the docker daemon wouldn't work.
Force stop the container from the same menu you start it from
Stop didn't work. Kill didn't work. And force remove ended up causing docker to get messed up and need reinstalled. (this was the first time). All subsequent times I just restarted the machine.
Stop and force stop are 2 different things
Also discussed here: #89