DoesItHimself

Just updated everything on the server and I'm running into the below error. Its a paste of the log which repeats over and over as hydra tries to start. Nothing has changed on my end with the docker or any settings. I see it stating there is a corrupt config file - I've already tried to delete the container and image for it and reload from a template with no luck. Any ideas? 2021-03-16 02:46:26,300 INFO - Determined java version as '11' from version string 'openjdk version "11.0.10" 2021-01-19' 2021-03-16 02:46:26,301 INFO - Starting NZBHydra main process with command line: java -Xmx256M -DfromWrapper -XX:TieredStopAtLevel=1 -noverify -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/config/logs -Dspring.output.ansi.enabled=ALWAYS -jar /app/nzbhydra2/bin/lib/core-3.13.1-exec.jar --nobrowser --datafolder /config in folder /app/nzbhydra2/bin 02:46:27.053 [main] DEBUG org.nzbhydra.config.ConfigReaderWriter - Using temporary file /config/nzbhydra.yml.bak at [Source: (File); line: 1, column: 1] java.lang.RuntimeException: Config file /config/nzbhydra.yml corrupted. If you find a ZIP in your backup folder restore it from there. Otherwise you'll have to delete the file and start over. Please contact the developer when you have it running. at org.nzbhydra.NzbHydra.initializeAndValidateAndMigrateYamlFile(NzbHydra.java:215) at org.nzbhydra.NzbHydra.main(NzbHydra.java:114) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.springframework.boot.loader.Launcher.launch(Launcher.java:109) at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:88) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:49) at org.springframework.boot.loader.Launcher.launch(Launcher.java:58) Caused by: java.lang.RuntimeException: Config file /config/nzbhydra.yml corrupted. If you find a ZIP in your backup folder restore it from there. Otherwise you'll have to delete the file and start over. Please contact the developer when you have it running. at org.nzbhydra.NzbHydra.initializeAndValidateAndMigrateYamlFile(NzbHydra.java:215) at org.nzbhydra.NzbHydra.main(NzbHydra.java:114) 2021-03-16 02:46:27,069 ERROR - Main process shut down unexpectedly. If the wrapper was started in daemon mode you might not see the error output. Start Hydra manually with the same parameters in the same environment to see it Logging wrapper output to /config/logs/wrapper.log

Bumping this - I've tried a few more docker removals and re-install from profile after the Unraid 6.9.1 and docker container update for Plex itself. I'm still stuck with a server that is "currently unavailable" despite being on the same LAN and logged in directly to the IP:port combo of Plex. Hoping someone might have an answer on this. I pulled some logs via a rootshare and noted a whole bunch of 'normal' Plex activity such as renaming files, identifying that I added things, etc.

Ran into an issue today after a slew of other issues that a lot of googling and other troubleshooting has not solved. My Plex container is up and running but is unreachable (all on the same network via LAN). My server went thru a long move, restarted fine, but after a few weeks a drive randomly disabled and yesterday I had to remove it from the array, add it back and rebuild from parity. I had updated to 6.9 a day or two before the drive issue. I also had a weird issue where my docker image got full, but ended up clearing itself out after the rebuild. Now I'm running into the above issue trying to reach my server from any of my usual devices (Roku, web app / webGUI). Nothing seems to get to it even if I am logged in directly to the IP:port combo. I've run through all of the Plex official troubleshooting, deleted my docker image and rebuilt it via saved container templates but no luck. Unfortunately its been quite some time since I've had hands on the server due to the move, and I'm a bit out of my depth at this point in troubleshooting. I tried to pull the container logs but they just listed a few startup items with no errors (log attached.) I don't seem to have access to the actual Plex logs, assuming this is because I cannot actually get to my server. plexlog.txt

System setup - Win 10 Pro laptop, Unraid server Unfortunately it's my turn to jump on the share folder issues. The username matching fix helped me out early only but now I'm running into problems. Mine's a bit different than the one's I've read so far though. Recently setup my Unraid server and used a lot of SIO guides including the 'ultimate rootshare' setup. I did not realize at the time but I never had a working (permission wise) 'Media' share via the rootshare or the self-setup option. I was having permission issues trying to use TinyMediaManager on the folders within Media share and thought nothing of it originally and charged forward. Fast forward to today - I restarted the server and my 'ultimate rootshare' and personally setup shares failed to reappear. I troubleshot for an hour before a restart of my laptop solved that. Frustrating to say the least. Now I have discovered that I specifically cannot write to my 'Movies' or 'TV' folder within my 'Media' share. All of my other shared folders, including the parent 'Media' itself, work just fine - appdata, download, isos, etc. I created test folders in a handful of other shares to verify and I have no issues. Its specifically trying to write/modify within those two. Hoping @Frank1940 or some of the pros might know the obvious answer I'm missing here.

I've been having issues with write permissions. qBittorrent has been able successfully receive files from Radarr/Sonarr, however it will never start a download. Logs confirm permission denied. Deluge works and has the exact same volume mapping. I have tried the following steps with no success: 1. Used default PUID/PGID 2. Used PUID/PGID that successfully work with Deluge (exact same path as Deluge) 3. Used the 'id (user)' command and input the PUID/PGID (values shown in screenshot) Regardless of what values I use, it will not write.