• Posts

  • Joined

  • Last visited

Everything posted by clb92

  1. It's already in the issue tracker, it seems:
  2. Yeah, I just noticed that too a few days ago when my server wouldn't run, and I couldn't find PaperMC anywhere. I just manually downloaded the .jar, put it in the mineos/games/servers/SERVERNAME/ folder and selected it in the dropdown "Change runnable .jar to:" and it seems to work for now.
  3. It simply means that you are already using that port (8443) for something else, maybe another docker or another program running on the server. A port can only be used by one program at a time. If you have multiple dockers that use this port, only one of them can run at a time.
  4. My temporary solution has been to just delete the existing symlink (pointing to java 1.8 by default) rm /usr/sbin/java and create the new symlink to newer included java binary ls -s /usr/lib/jvm/java-11-openjdk/bin/java /usr/sbin/java to point to the newer included java 11 instead. I'm only running a single PaperMC server, but so far it works fine. This solution probably doesn't persist through reboots, so you'll likely need to redo it either if you reboot or update this container.
  5. The solution should be to update Unraid, or if that's not possible, install a newer version of 'runc' yourself (search and you'll find a how-to somewhere around here by binhex)
  6. Are you accessing the web interface through a reverse proxy or something that maybe adds HSTS?
  7. Do not run it as privileged. It's a big security risk. Binhex posted in the MinecraftServer (not MineOS) support thread that it can be temporarily fixed with a simple command (after every reboot), until it's permanently fixed in a future Unraid update:
  8. Unfortunately, it did not work. Same error as earlier.
  9. Has not been resolved yet. If it works for you now, just stay on that version for a while longer. Binhex made a new test image of binhex-minecraftserver (not MineOS) yesterday and is waiting for feedback, since he's not able to reproduce the issue himself.
  10. Oh, so that an image from before whatever changed and ruined things?
  11. OMG, based on your post here I guessed that you'd have an "arch-mineos-node:test" image too, so I tried it (and remembered to turn off privileged) and it seems to work for me! What was the issue?!
  12. I just tried making that change to my template XML, but it changes nothing for me. Same error as before. Am I reading it right that you needed both this XML change AND to run as privileged to get it working? If so, that's strange. Simply running as privileged without the XML change works for me (but obviously that's a terrible solution!)
  13. I found this itzg/docker-minecraft-server issue where the title alone caught my attention. Could it be related, or am I just grasping at straws?
  14. I just created a completely fresh container again and put the config in a share that's never cached (so it never touches my BTRFS cache pool). Didn't make any difference. Man, this is frustrating.
  15. I experienced that bug a couple times long time ago too. I doubt it's related to any of the other permissions stuff, to be honest. 1. No CPU pinning on any of my docker containers. I do use it for my VMs. 2. I don't think I'm limiting the RAM. I'm not sure where I would do that even. Never experienced any OutOfMemory errors at least, and inside MineOS I usually give the server 6-10GB to work with. 3. Using XFS on my array and BTRFS on my cache pool. 4. Docker volume is located in "/mnt/user/system/docker/docker.img" and the System share is set to "Cache: Prefer" 5. Yes, I am running Unassigned Devices (but not using any unassigned disks or mounts for anything related to Docker) 6. Host has 128 GB memory in total. 7. CPU is 2 x Intel Xeon E5-2670v2 @2.50GHz (in total 20 cores / 40 threads). 8. Yes, in MineOS I log in as "nobody" with the password I set in the container template.
  16. I've been testing some more. I just tried with a completely empty config folder (just made a new folder in my appdata and mapped it to /config) and made sure (just one more time) to force update the image (it was already the latest). MineOS web interface starts up just as expected after a short while. I go to Profiles and pull the latest 1.16.5 Mojang jar. I go to Create Server, leave everything at default except the name "Test". Click create. Go to the Server Status page. I wait for the 1.16.5 jar to show up in the dropdown, select it, and click the "Copy profile to live server files" button below. I select the 1.16.5 jar over in the Java Settings too. Leave everything else as default. (For the record, it says "Server Owner: root (0)" in the "Ownership and Disk Usage" box, in case that's useful.) I then click Accept EULA and again the grey Accept EULA (which seems to do nothing) and then Start. At this point it show status as "Up". After maybe 10 seconds it will say status "Down" again. At this point I check the log where I see Java throwing the same "Operation not permitted" error as before. Note however, that I did NOT remove my binhex-mineos-node container completely and start over with a fresh container template. Has anything changed in the template recently? Could my container template be outdated somehow? EDIT: Just tried pulling a new fresh template from CA, leaving it at default (with a new empty folder in my appdata again), and going through same procedure as before - Same permissions error as before
  17. Same result. The chown and chmod commands took maybe 10-15 seconds to finish. Restarted the container, logged into MineOS web interface, MC server tried to start (it's set to autostart) but failed with same persission error as before.
  18. sh-5.1# java -version openjdk version "1.8.0_282" OpenJDK Runtime Environment (build 1.8.0_282-b08) OpenJDK 64-Bit Server VM (build 25.282-b08, mixed mode) My Minecraft server is an existing "Paper-1.16.5-latest" server.
  19. Still same permission issue with latest version here too.
  20. Same issue here after updating Unraid and the binhex-mineos-node image (confirmed I have the latest too). Running "Paper-1.16.5-latest" Minecraft server. I can connect just fine to the MineOS web interface, but the server status is "Down". Manually trying to start it fails after maybe 10 seconds. Getting this in the MineOS's log: [18:01:38] ain/INFO]: Environment: authHost='', accountsHost='', sessionHost='', servicesHost='', name='PROD' [18:01:38] ain/FATAL]: Failed to start the minecraft server java.lang.RuntimeException: java.nio.file.FileSystemException: .: Operation not permitted at net.minecraft.server.v1_16_R3.Convertable.<init>( ~[patched_1.16.5.jar:git-Paper-445] at net.minecraft.server.v1_16_R3.Convertable.a( ~[patched_1.16.5.jar:git-Paper-445] at net.minecraft.server.v1_16_R3.Main.main( ~[patched_1.16.5.jar:git-Paper-445] at org.bukkit.craftbukkit.Main.main( ~[patched_1.16.5.jar:git-Paper-445] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke( ~[?:?] at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke( ~[?:?] at java.lang.reflect.Method.invoke( ~[?:?] at io.papermc.paperclip.Paperclip.main( ~[paperclip.jar:?] Caused by: java.nio.file.FileSystemException: .: Operation not permitted at sun.nio.fs.UnixException.translateToIOException( ~[?:?] at sun.nio.fs.UnixException.rethrowAsIOException( ~[?:?] at sun.nio.fs.UnixException.rethrowAsIOException( ~[?:?] at sun.nio.fs.UnixPath.toRealPath( ~[?:?] at net.minecraft.server.v1_16_R3.Convertable.<init>( ~[patched_1.16.5.jar:git-Paper-445] ... 8 more
  21. It may be a couple of days before I get to it, but I'll test it out and let you know. Thanks for taking the time to investigate further! I would be willing to lend you my Minecraft account too (with a temporary password), if further testing becomes necessary.
  22. About the world not saving issue I had some time ago, it does indeed seem to be a container issue. I set up a completely new container with a completely new world and everything (new /config location entirely) and I have the same issue there. World still doesn't save if the container is shut down. I have also ruled out permissions issues. World saves correctly if I go into the console and type the command 'stop' and then stop the docker container. For now, I'm trying out your MineOS container instead - Just doing some tests there too right now to make sure it saves correctly 🙂
  23. This container. It's been running absolutely perfectly until like 1 or 2 weeks ago.
  24. A single-SSD cache pool (been running the Minecraft server on there for about a year). I'll let you know if I find anything. Thanks for maintaining all these containers, by the way!