int-rnd
commented
1 year ago So I dug into the auto ripper code and I think I found the problem.
When you run the below command as pulled from the autoripper, the output is the same regardless of the container being on the internet or not. The difference is that when the container is on the Internet, the command returns(exits). When there is no internet, the command hangs even though the output is identical. Seems there is some required connectivity and indicates the problem is not in the autoripper but rather makemkvcon. It feels like it is trying to call home and can't.
I wonder if setting app_UpdateEnable = "0" in ~/.MakeMKV/settings.conf would prevent it from attempting to call home and hanging. Not sure how I would test this as there appears to be some caching.
/tmp # env HOME=/config LD_PRELOAD=/opt/makemkv/lib/libwrapper.so /opt/makemkv/bin/makemkvcon -r --cache=1 info disc:9999 MSG:1005,0,1,"MakeMKV v1.17.4 linux(x64-release) started","%1 started","MakeMKV v1.17.4 linux(x64-release)" DRV:0,2,999,28,"BD-ROM hp BD CMB UJ160 1.00 HN32 003368","SOMETITLEHERE","/dev/sr0" DRV:1,256,999,0,"","","" DRV:2,256,999,0,"","","" DRV:3,256,999,0,"","","" DRV:4,256,999,0,"","","" DRV:5,256,999,0,"","","" DRV:6,256,999,0,"","","" DRV:7,256,999,0,"","","" DRV:8,256,999,0,"","","" DRV:9,256,999,0,"","","" DRV:10,256,999,0,"","","" DRV:11,256,999,0,"","","" DRV:12,256,999,0,"","","" DRV:13,256,999,0,"","","" DRV:14,256,999,0,"","","" DRV:15,256,999,0,"","","" MSG:5010,0,0,"Failed to open disc","Failed to open disc" TCOUNT:0
Either way, it appears that this would only impact people trying to rip without an active internet connection. Hope the helps.
Feel free to either dig into this or close. Either way, I hope this helps anyone that has similar issues where their jlesage makemkv containers are not able to get to the internet.
Also thanks for an awesome project!
Current Behavior
Have been using the container with much success. This started today - I noticed that it now takes 8-10 minutes to detect a disc. Took seconds before. Rebuilt the container, swapped drives, rebooted, adjusting AUTO_DISC_RIPPER_INTERVAL - all seems to have no affect. The funny thing is that the disc is immediately detected in the GUI but the auto ripper won't see it for up to 10 minutes. In that time I can rip most of a DVD manually in the GUI.
Also a funny thing, this happened right as a new MakeMKV license was made available. Wondering if the underlying commands that the autoripper is using have changed/broke/froze and are impacting it. It's just odd that it started minutes after UTC time went to Aug 1. Not sure if that is related.
Expected Behavior
It should detect the disc as as defined by AUTO_DISC_RIPPER_INTERVAL and be on its way.
Steps To Reproduce
Pull the image from docker. Map the srX and sgY, settings The container Insert a disc See the disc in the GUI - read a ready to go NOTHING HAPPENS Wait 8-10 min and then it finally sees it via the Auto Ripper
Environment
Container creation
makemkv0: image: jlesage/makemkv volumes:
Container log
Container inspect
No response
Anything else?
No response