eat_eat_the_doreets

Thanks so much for these instructions. I too use dynmap and saw rsync processes taking up all of the container's CPU .. i didn't put 2 and 2 together that Dynmap creates tons and tons of very small files. There are 2 modifications needed: Step 1 and 2 need to be "mkdir -p" to create the entire hierarchy of directories Step 5 - Copy the entire contents of the original web folder to the new folder. Something like: cd /mnt/user/appdata/binhex-mineos-node/mineos/games/servers/CREATIVE/plugins/dynmap/web <existing folder cp -pr * /mnt/user/appdata/binhex-mineos-node/mineos/games/dynmap/SURVIVAL/web/ < folder for server I was trying to fix Mine didn't work if I didn't do that - it only showed "directory : /" when you went to the webpage. Following those instructions has made my WebGUI load pretty much instantly again. Thanks!!

Hi Binhex, since you switched back to Java 8, my FTB Infinity server (based on minecraft 1.7.10) starts now. I just recreated the container. A lot of mod packs are still on older versions of the game that don't support Java 11. Is there a way to, in future when you're going to change to Java 11 again, make it a container parameter so we can launch with "java_runtime_8" or "java_runtime_11"? That would give everyone the most flexibility in running whatever servers they want. Thanks for making this container and for all that you do 😊

This has happened to me today, that's why I'm in this thread. I had 2 torrents queued (not actually started downloading) and I restarted the array (for a different issue) and when the container came back up they were gone. I also am having some completed (seeding) torrents going into Error, and the files are missing, frequently. But sonarr / radarr hardlinks / moves my media to my media / plex area so I'm not really too worried about that bug, but it is affecting my ratios on private trackers if I can't seed for 2 full weeks. Binhex... Do you want me to post some logs? I'd be happy to be a guinea pig and help with this. I think I still have my supervisord log from today when the container was restarted if that's helpful. There's nothing that stands out in it, to me.

Click Edit on the docker, and it's right above the variables and after the "console shell command" I changed this, and both my servers (1 FTB, one Vanilla) started perfectly.

for what it's worth, i'm getting this too in my logs, the container is operating normally right now (seeding and downloading fine) but I have had this issue in the past where I've had to restart the container. Previously, it ran for 11 days without issue. 2020-11-10 05:58:24,937 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38175' 2020-11-10 06:13:30,983 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38175' 2020-11-10 06:19:26,115 DEBG 'watchdog-script' stdout output: 0 2020-11-10 06:19:26,991 DEBG 'watchdog-script' stdout output: [warn] Incoming port site 'https://portchecker.co/' failed to web scrape, marking as failed 2020-11-10 06:19:27,904 DEBG 'watchdog-script' stdout output: 0 2020-11-10 06:28:31,377 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38175' 2020-11-10 06:43:31,851 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38175' 2020-11-10 06:50:33,809 DEBG 'watchdog-script' stdout output: 0 2020-11-10 06:50:34,691 DEBG 'watchdog-script' stdout output: [warn] Incoming port site 'https://portchecker.co/' failed to web scrape, marking as failed 2020-11-10 06:50:35,286 DEBG 'watchdog-script' stdout output: 0 2020-11-10 06:58:32,265 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '38175' Not sure if this is an early indicator of failure, or what.