shidraconis
-
Posts
10 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by shidraconis
-
-
No problem, glad I could help.
-
I updated the ripper.sh file, restarted the docker, and waited a few minutes to see if tmp files started to be created. Only 1 did, so I waited a little longer to see if any more appeared. Still the 1 there. I think that modification worked.
-
3 minutes ago, rix said:
This looks expected..
I have added this command, that should delete all the .tmp files in the folder:
find /tmp/ -name "*.tmp" -type f -delete
Could you please enter that one in the container shell and post the results.. might be an error displayed or it working perfectly.. either would help me get to the core of this
I ran the command you provided and it doesn't delete anything. I personally to clear the tmp files out ran a "rm -r *.tmp" but I don't know if this is applicable here.
-
Thanks for trying, I'll see if I can get a script to run in the userscripts plugin to delete them. Either way here's the output of an ls in the tmp folder.
-
10 hours ago, rix said:
Yes, because once you started the image it places the ripper.sh on your disk and will not overwrite it. Delete your ripper.sh then check again.
I deleted the ripper.sh and rebooted the docker afterwards which did create the new ripper.sh file like you said, and .tmp files are being created still and not deleting.
-
I did update and it doesn't appear to be deleting the files, the temp files are being created even when the system isn't ripping anything just sitting idle.
-
I know it was mentioned before that the docker size for Ripper was growing large without doing anything. Mine is consistently filling the /tmp directory with a bunch of "MakeMKV-0x78a1-2.tmp, MakeMKV-0x78a2-2.tmp, and so on every minute or so, could be less. Each one is 532kb in size, I have to almost every day go in and run a "rm -r *.tmp" to clear them out otherwise the docker image fills up which it has already done to me once. I have implemented the --log-opt max-size=50m but I don't think that is what this is about.
-
Worked like a charm, thanks.
-
So I have been using the Ripper docker and it is very shortly ejecting the disc after it's inserted saying done in the logs for it. Now the Ripper.txt file in the app data is saying this:
MSG:1005,0,1,"MakeMKV v1.14.4 linux(x64-release) started","%1 started","MakeMKV v1.14.4 linux(x64-release)"
MSG:5074,0,0,"Automatic checking for updates is enabled, you may disable it in preferences if you don't want MakeMKV to contact web server.","Automatic checking for updates is enabled, you may disable it in preferences if you don't want MakeMKV to contact web server."
MSG:3338,0,2,"Downloading latest SDF to /tmp/MakeMKV-0x17d-2.tmp ...","Downloading latest %1 to %2 ...","SDF","/tmp/MakeMKV-0x17d-2.tmp"
MSG:2003,0,3,"Error 'Scsi error - ILLEGAL REQUEST:READ OF SCRAMBLED SECTOR WITHOUT AUTHENTICATION' occurred while reading 'BD-ROM TSSTcorp DVDWBD SH-B123L SB04' at offset '1048576'","Error '%1' occurred while reading '%2' at offset '%3'","Scsi error - ILLEGAL REQUEST:READ OF SCRAMBLED SECTOR WITHOUT AUTHENTICATION","BD-ROM TSSTcorp DVDWBD SH-B123L SB04","1048576"
DRV:0,2,999,1,"BD-ROM TSSTcorp DVDWBD SH-B123L SB04","DOTHACKLEGEND_TWILIGHT_VOL_01","/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:5021,260,1,"This application version is too old. Please download the latest version at http://www.makemkv.com/ or enter a registration key to continue using the current version.","This application version is too old. Please download the latest version at %1 or enter a registration key to continue using the current version.","http://www.makemkv.com/"
eject: tried to use `devtmpfs' as device name but it is no block deviceI have also provided my own makemkv key and put it in the settings.conf file to see if that would fix it, it did not. Any help would be appreciated.
[Support] ich777 - Gameserver Dockers
in Docker Containers
Posted
I am having the same issue as well, but the workaround I came up with in the meantime was to stop the docker, download the 1.4.0.2 server files and copy them to the appdata folder that the game files download to, and start the docker. The server launches just fine as 1.4.0.2. Just make sure the version number is the same in the docker settings. From the active log it was saying that it couldn't rm some serverfiles or unzip the new update.