clb92

Members
  • Posts

    32
  • Joined

  • Last visited

Posts posted by clb92

  1. On 6/18/2022 at 12:38 AM, CmdrKeen said:

    anybody else have an issue where the docker takes almost 20 minutes to finish loading so i can access the webui?

    The log will stay at this screen for 17-18 minutes or so before finishing booting, and any time i need to restart the docker it does the same thing.

     

    image.png.087b662b8905ba80226c224402bec409.png

    Eventually it finishes booting and the log looks like this (note the timestamps to see the delay):

    image.png.5e6078462a6269f20185cad54eb238a1.png

    Yes, I'm having this issue too now. No problems two days ago, but it takes forever to start up now. I'm seeing it stuck exactly like in your first screenshot. Haven't waited long enough for it to reach "MineOS-node started" yet.

    I'm actually looking for an alternative to MineOS, as it also no longer has PaperMC profiles built-in anyway.

  2. 8 hours ago, CmdrKeen said:

    Is PaperMC no longer available from the profiles download page in the webui?

    EDIT: this appears to be an issue with where papermc hosts their files:

    https://discourse.codeemo.com/t/paper-profiles-no-longer-available/5100

    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. 1 hour ago, craig_read said:

    "docker: Error response from daemon: driver failed programming external connectivity on endpoint binhex-mineos-node (a2bcf15bc8d80088d401ae9411f93e328e38faf17bd15b7ed165ca1c8cc95f8f): Error starting userland proxy: listen tcp4 0.0.0.0:8443: bind: address already in use."

    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. Just now, AlphaOmegaKappa said:

    I'm experiencing the same "operation not permitted" error that multiple people in this thread had in late March. Was there ever a concrete solution to the error? I saw several possible solutions in the thread, but none seemed definitive.

     

    Here's my logs for reference:

    [23:03:51] ain/INFO]: Environment: authHost='https://authserver.mojang.com', accountsHost='https://api.mojang.com', sessionHost='https://sessionserver.mojang.com', servicesHost='https://api.minecraftservices.com', name='PROD'

    [23:03:51] ain/FATAL]: Failed to start the minecraft server

    java.lang.RuntimeException: java.nio.file.FileSystemException: .: Operation not permitted

    at cyg.<init>(SourceFile:98) ~inecraft_server.1.16.5.jar:?]

    at cyg.a(SourceFile:105) ~inecraft_server.1.16.5.jar:?]

    at net.minecraft.server.Main.main(SourceFile:117) inecraft_server.1.16.5.jar:?]

    Caused by: java.nio.file.FileSystemException: .: Operation not permitted

    at sun.nio.fs.UnixException.translateToIOException(UnixException.java:91) ~[?:1.8.0_282]

    at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) ~[?:1.8.0_282]

    at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) ~[?:1.8.0_282]

    at sun.nio.fs.UnixPath.toRealPath(UnixPath.java:837) ~[?:1.8.0_282]

    at cyg.<init>(SourceFile:96) ~inecraft_server.1.16.5.jar:?]

    ... 2 more

    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)

    • Thanks 1
  6. 5 hours ago, Joe Rees said:

    Yeah, I know how to get past the usual SSL self-signed certificate error. The problem is that there is no option to get past it like you suggest. When I click "Advanced", I get a different error than I have ever seen before and there is literally no "Connect anyway" kind of link or button so I can continue on to the website. It's like the browser is seeing a problem with it and completely rejecting my ability to go to the site. I believe it is seeing it as a MITM attack and just blocks it. I've even tried a bare, fresh install of another browser with no extensions installed that might be responsible for blocking it. 

    I appreciate the video and will definitely give it a watch, as I know it will help me a ton once I figure out what is causing this. I think I'll reboot the entire UnRaid server and see if that clears it up. This is a weird one that I've just never seen or experienced before, and I'm an ex-Network Security Engineer, lol. 

     

    Are you accessing the web interface through a reverse proxy or something that maybe adds HSTS?

  7. 10 minutes ago, DGB said:

    Sounds like i'm having a similar problem

     

    Minecraft server was running fine until I did the update now I can't connect to it unless i turn on "privileged" is this likely to cause any problems?

     

    Thanks

    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:

     

    • Like 1
  8. 37 minutes ago, binhex said:

    alright got another test image to try, this one uses the older jre that was used in the old 'test' tagged image that works for you. so please give binhex/mineos-node:test2 image a whirl and let me know how that goes.

    Unfortunately, it did not work. Same error as earlier.

  9. Just now, PsykoB said:

    I'm hesitant to update the docker. Should I do it? Have the issues been resolved?

    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. 22 minutes ago, binhex said:

    ok this seems to be an issue that is spreading across my minecraft images, the issue i have is that i am still unable to replicate this problem which is just weird!. 

     

    in any case, i have a theory for a possible fix, please can you do unraid web ui/docker/left click icon and select edit and then change the repository to binhex/arch-minecraftserver:test

     

    this will then pull down a test tagged image, let me know if it fixes the issue, dont forget to turn off privileged!.

    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?!

  11. 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!)

  12. 30 minutes ago, binhex said:

    agreed

     

    ok well the only real difference from my system to yours is the fact i am using XFS for my cache drive (not in a pool), and your processor is different, im using a AMD 2700x, i guess it COULD be related to BTRFS, other than that i am clueless at the moment as to the fix, other than switching to privileged mode, hmmm.

    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.

  13. 2 hours ago, binhex said:

    i too can replicate the download bug, mineos-node sometimes simply crashes if you attempt to download a new release, especially if you attempt 2 downloads simultaneously, no idea why at this point, it is interesting though that you do not see the permissions issue though, which docker image are you using, latest?

    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 hour ago, binhex said:

    ok thanks for this, i followed your instructions above to the letter and i did run into memory related issues, which is not surprising due to the default low value, so i did see this:-

    
    [09:29:15] [Server thread/FATAL]: Error executing task on Chunk source main thread executor for minecraft:overworld
    java.util.concurrent.CompletionException: java.lang.OutOfMemoryError: GC overhead limit exceeded

     

    Once i had tweaked the default value for memory for the server to 2048 then it started without issue,, i double checked and i did NOT have privileged set so its not that, so it must be something else going on, can you answer the following:-

     

    1. do you have any cpu pinning going on?

    2. do you limit ram for the container?

    3. what filesystem are you running, btrfs or xfs?

    4. what is the location for the docker image, cache or array?

    5. are you using unassigned devices?

    6. how much ram does your host have in total?

    7. what is the cpu in your host?.

    8. just to confirm, you are logging into the webui as user 'nobody' right?

    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.

     

  14. 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 :(

    • Thanks 1
  15. 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='https://authserver.mojang.com', accountsHost='https://api.mojang.com', sessionHost='https://sessionserver.mojang.com', servicesHost='https://api.minecraftservices.com', 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>(Convertable.java:42) ~[patched_1.16.5.jar:git-Paper-445]
    at net.minecraft.server.v1_16_R3.Convertable.a(Convertable.java:50) ~[patched_1.16.5.jar:git-Paper-445]
    at net.minecraft.server.v1_16_R3.Main.main(Main.java:112) ~[patched_1.16.5.jar:git-Paper-445]
    at org.bukkit.craftbukkit.Main.main(Main.java:276) ~[patched_1.16.5.jar:git-Paper-445]
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
    at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
    at io.papermc.paperclip.Paperclip.main(Paperclip.java:58) ~[paperclip.jar:?]
    Caused by: java.nio.file.FileSystemException: .: Operation not permitted
    at sun.nio.fs.UnixException.translateToIOException(UnixException.java:100) ~[?:?]
    at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111) ~[?:?]
    at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:116) ~[?:?]
    at sun.nio.fs.UnixPath.toRealPath(UnixPath.java:860) ~[?:?]
    at net.minecraft.server.v1_16_R3.Convertable.<init>(Convertable.java:40) ~[patched_1.16.5.jar:git-Paper-445]
    ... 8 more

     

  16. 10 minutes ago, binhex said:

    ive been doing some further investigation into the above, and whilst i cannot directly confirm my fix works (no java minecraft client) i have good confidence it does fix the problem, if you are still game do you fancy trying a 'test' tagged image with the fix included?, if so then please do the following:-

     

    1. open unraid web ui and go to docker tab

    2. left click minecraft icon and select edit

    3. append ':test' to the repository field

    4. click on apply at the bottom to pull down the test tagged image.

     

    to switch back to latest do the reverse of the above.

    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.

    • Like 1
  17. 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 🙂