Rockstar

Same thing happened to me once I updated the container. Container logs: Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2021-03-12 01:05:09.206100 [info] Host is running unRAID 2021-03-12 01:05:09.220444 [info] System information Linux 6742fc3c0e04 5.10.19-Unraid #1 SMP Sat Feb 27 08:00:30 PST 2021 x86_64 GNU/Linux 2021-03-12 01:05:09.240847 [info] OS_ARCH defined as 'x86-64' 2021-03-12 01:05:09.261576 [info] PUID defined as '0' 2021-03-12 01:05:09.346306 [info] PGID defined as '0' 2021-03-12 01:05:09.391288 [info] UMASK defined as '000' 2021-03-12 01:05:09.408985 [info] Permissions already set for volume mappings 2021-03-12 01:05:09.444222 [info] Deleting files in /tmp (non recursive)... 2021-03-12 01:05:09.462838 [info] WEBUI_PASSWORD defined as 'mineos' 2021-03-12 01:05:09.620495 [info] Starting Supervisor... 2021-03-12 01:05:09,864 INFO Included extra file "/etc/supervisor/conf.d/mineos-node.conf" during parsing 2021-03-12 01:05:09,864 INFO Set uid to user 0 succeeded 2021-03-12 01:05:09,867 INFO supervisord started with pid 6 2021-03-12 01:05:10,869 INFO spawned: 'shutdown-script' with pid 70 2021-03-12 01:05:10,871 INFO spawned: 'start-script' with pid 71 2021-03-12 01:05:10,871 INFO reaped unknown pid 7 (exit status 0) 2021-03-12 01:05:10,879 DEBG 'start-script' stdout output: [info] Starting MineOS-node... 2021-03-12 01:05:10,879 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2021-03-12 01:05:10,879 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2021-03-12 01:05:11,017 DEBG 'start-script' stdout output: Starting mineos daemon... 2021-03-12 01:05:11,329 DEBG 'start-script' stdout output: mineos daemon started. PID: 81 2021-03-12 01:05:11,332 DEBG 'start-script' stdout output: [info] MineOS-node started 2021-03-12 01:05:11,332 DEBG 'start-script' stdout output: [info] Running chmod for /config (no exclusions)... 2021-03-12 01:05:12,499 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22743530855728 for <Subprocess at 22743530855056 with name start-script in state RUNNING> (stdout)> 2021-03-12 01:05:12,499 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22743531017360 for <Subprocess at 22743530855056 with name start-script in state RUNNING> (stderr)> 2021-03-12 01:05:12,499 INFO exited: start-script (exit status 0; expected) 2021-03-12 01:05:12,499 DEBG received SIGCHLD indicating a child quit This is also signed in via nobody/mineos. From the server logs (inside MineOS) Failed to start the minecraft server java.lang.RuntimeException: java.nio.file.FileSystemException: .: Operation not permitted Seems to indicate a permissions issue. I can also confirm running the container (as a test) as privileged allows everything to work again.

Honestly, I would leave it as is. I reckon those of us running dynmap are in the small % of users. Not to mention that MineOS has it's own limitations in regards to very large servers and files. Regarding Java 11: So far no issues at all. If I haven't done so already, thank you for your work in providing us with this container!

In the initial config, it should have defaulted to a range of ports (25565 -25570). In the server properties (gui or file via text editor of choice), you change the query.port and server-port to the desired port. This process is the same if you're using Bungeecord.

Yeah I noticed after I moved my dynmap folder outside of where MineOS was coded to check on that the WEBui is rather decent in terms of speed... but now the container takes around 1/2 hour to load if I had to restart it or something. This makes sense now if there's a check on each file for permissions... dynmap can have 100's or 1000's of files in its directory. Bah, can't win with this plugin lol

Just used your steps and this worked! Thank you so much for posting this!

So.. pretty sure I figured out the issue to my WebUI problem. After doing quite a bit of research on the main dev's forums...it looks like mineOS scans everything at specific intervals. Why? I have no idea. One of the plugins I was using was Dynmap and this program creates a TON of small files for it's own webapp. I am not sure if I am right or not, but it seems every time mineos did it's scan, it had to parse every single file created. I think mine had in the realm of 190k files (totaling about 800mb). Once i removed this plug-in and all it's contents...everything went back to normal. Seems like this is a limitation with mineOS. So now that I am running without dynmap, the server is happy again and the webui is extremely responsive.

Hello! I'm not quite sure what's happened but I noticed as of the last 2 weeks a few interesting things started to happen to the WebUI: When the array comes online (or container is started) the WebUI takes around 10 mins or so to start working. -During the time where the WebUI won't load, I can still connect to the sever from the game without issue When it does finally load up, all the cores I have assigned to this container peak to 80-100% usage for anywhere between 5 and 10 mins ( have 2 cores 2 threads assigned and these are not shared with any other container/application/VM). It no longer shows I have any backups from the WebUI (but if I check the files, I do). Perms on the folders are 0777 and accessible by "nobody", so I can't see why that would affect this. Refreshing the page (I use firefox however, behavior is the same on Chrome), causes the WebUI to become extremely unresponsive for 1-2 mins. This will cause the cores to peak to 80-100% usage during the 1-2 mins I tried removing the container completely and re-doing it....and it's still doing the same behavior it was before. Container logs don't really show anything worthwhile at all but are attached. I am not sure if anything else may be causing this but I don't really know where else to diagnose. All other containers are working fine. Only 1 server is running: PAper-MC with the following Java parameters: -XX:+UseG1GC -XX:+ParallelRefProcEnabled -XX:MaxGCPauseMillis=200 -XX:+UnlockExperimentalVMOptions -XX:+DisableExplicitGC -XX:+AlwaysPreTouch -XX:G1NewSizePercent=30 -XX:G1MaxNewSizePercent=40 -XX:G1HeapRegionSize=8M -XX:G1ReservePercent=20 -XX:G1HeapWastePercent=5 -XX:G1MixedGCCountTarget=4 -XX:InitiatingHeapOccupancyPercent=15 -XX:G1MixedGCLiveThresholdPercent=90 -XX:G1RSetUpdatingPauseTimePercent=5 -XX:SurvivorRatio=32 -XX:+PerfDisableSharedMem -XX:MaxTenuringThreshold=1 -Dusing.aikars.flags=https://mcflags.emc.gs -Daikars.new.flags=true I have assigned 8gb of ram to this server from the parameters. Will be glad to upload any other logs if someone can point me to which ones might be good to pull. I apologize if this is something not related to the container but to Hexparot's code, just figured I'd start here first. Binhex-MineOS-Node Logs.txt