Well I think I finally discovered it today. I'd have to reboot the server to fix it and force it to rip in the correct location. I couldn't figure this out for the longest time. After plugging the drive back in and starting the docker again I noticed that sometimes the output files in /out are not being placed there as the root folder but in another folder called "," and inside that folder is another folder that is the drive name "DRV:0,2,999,12,"BD-RE ASUS BW-12D1S-U E401"" and in that folder is where the output is being placed during the RIP. Unplugging the optical drive would allow the docker to stop (its an external USB3 bluray drive). Showing the log from WebUI fails and you cannot access the terminal either. I just know that attempting to kill/stop the docker would result in the docker just being hard locked and refusing to stop. I couldn't really figure out what was going on. Well sometimes after ripping a few discs, the docker will just peg once CPU core and has a hard time progressing.
I've been noticing sometimes the docker will lockup (its rare overall, but I have it running 24/7 whether its in use or not, I mean why not?). MSG:4040,0,1,"Unable to execute external program 'ccextractor' as its path is not set in preferences","Unable to execute external program '%1' as its path is not set in preferences","ccextractor" MSG:5015,131072,4,"Saving 1 titles into directory file:///out/DVD/ADDAMSFAMILY using profile 'Default' from file '/config/'","Saving %1 titles into directory %2 using profile '%3' from file '%4'","1","file:///out/DVD/ADDAMSFAMILY","Default","/config/" Its been installed in /usr/local/bin/ccextractor. ccextractor wasn't installed in /usr/bin/ccextractor. The ccextractor thing is still an issue as the location settings do not match. Jlesage's image includes a line in the nf that guides to the binary. Let me know if something needs to be changed.
0 kommentar(er)
