AlphaOmegaKappa

Members
  • Content Count

    27
  • Joined

  • Last visited

Community Reputation

2 Neutral

About AlphaOmegaKappa

  • Rank
    Newbie
  1. I've followed your instructions, and have made the variable, named it JAVA_VERSION, etc. without a hitch. In addition, the new server I made to test 1.17 has the correct JARs, enough memory allocated to it, and so on. However, when I try to launch the server, it either • Doesn't launch • Launches for about 10 seconds and then stops, leaving no record in the log I'm running the next-to-latest image of the docker (the latest being the one you pushed out a few hours ago), but there's no option for me to update it. Should I reinstall the docker, or is there another solution?
  2. On version 6.9.2 So I had an issue with my docker services recently; to solve it, I just deleted my docker.img, reinstalled my container images, and everything was good. However, the cache drive is reporting much higher utilization than I would normally expect. Before resetting my docker image, the cache drive was sitting at 27% utilization (55/200gb), but now it's reporting 43% utilization (85/200gb). This conflicts both with what krusader's reporting, as well as the breakdown from a terminal command. The 30gb difference is close to what I've allocated for docker (28gb) so is that
  3. 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.RuntimeEx
  4. I just checked, and the main folder where the files are is set to "Prefer", and was set to "Only" until a month ago. I also made a copy of the server using a different docker, but I'm running into the same error.
  5. Yes, MinecraftBasicServer. No custom versions, just plain vanilla 1.16.5. I'll try to delete the runtime folder and .jar, and then update you. EDIT: The same error occurs, at the same lines, after letting Minecraft generate a fresh runtime and server.jar.
  6. Noticed that my Minecraft server wasn't working, so I cracked open the logs, and noticed that it was calling a null pointer exception. ---Checking if UID: 99 matches user--- usermod: no changes ---Checking if GID: 100 matches user--- usermod: no changes ---Setting umask to 000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Starting...--- ---Checking for 'runtime' folder--- ---'runtime' folder found--- ---Checking if Runtime is installed--- ---Runtime found--- ---Checking for Minecraft Server executable --- ---Minecraft
  7. The .crt file would be ca.RSA.2048 right?
  8. So I feel like other people have been having the same issue, but I've tried some of the fixes in this and the qbittorrent thread to no luck. I use PIA and recently the WebUI of deluge and qbittorrent won't load when I enable the VPN in the container settings, but it will when I disable it. I downloaded the most recent OpenVPN config files from PIA, with no luck. I also changed the files from Toronto to Ontario, as someone mentioned in this thread, also to no luck. Removing the container image and deleting all files with the CA cleanup utility and starting fresh also did nothing. Before the iss
  9. Sorry, I run 2 different templates, here's the correct run command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='plex' --net='host' -e TZ="America/Chicago" -e HOST_OS="Unraid" -e 'VERSION'='docker' -e 'NVIDIA_VISIBLE_DEVICES'='' -e 'TCP_PORT_32400'='32400' -e 'TCP_PORT_300'='300' -e 'TCP_PORT_8324'='8324' -e 'TCP_PORT_32469'='32469' -e 'UDP_PORT_1900'='1900' -e 'UDP_PORT_32410'='32410' -e 'UDP_PORT_32412'='32412' -e 'UDP_PORT_32413'='32413' -e 'UDP_PORT_32414'='32414' -e 'PUID'='99' -e 'PGID'='100' -v '':'/movies':'rw' -v '':'/tv':
  10. Yeah there's a few left (mostly dockers I don't really use) so I'll have to transfer it. Gotcha, that'd make sense, which is why I saw the 2 different dated libraries within my appdata share. I do, just ran a backup from a version before I made the edit. Unfortunately no luck, same problem as before.
  11. Here it is! root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='Plex-Media-Server' --net='host' -e TZ="America/Chicago" -e HOST_OS="Unraid" -e 'PLEX_CLAIM'='claim-[Claim code redacted]' -e 'PLEX_UID'='99' -e 'PLEX_GID'='100' -e 'VERSION'='latest' -v '/tmp':'/transcode':'rw' -v '/mnt/user/data/media/':'/data':'rw' -v '/mnt/user/appdata/Plex-Media-Server/':'/config':'rw' 'plexinc/pms-docker' 728c7e77866761a818d19d7b2a29cc6b66500dc165846f499c84e9f87d5f89ff The command finished successfully!
  12. Got it, thanks very much, I've attached it below. home-diagnostics-20210405-2145.zip
  13. Sorry for the basic question, but where would I get the diagnostics (is that just the logs)?
  14. Got it, to try and fix the issue I set my appdata user share to "prefer," invoked the mover (which transferred the majority of the Plex files from my array to the cache drive), and then I used krusader to transfer the few files that were left. Howevever, even after I did this and changed the path back to /mnt/user, I'm still running into the same issue.