• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Mesias

  • Rank


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I've been dealing with theis issue for a while now... it started happening after I updated to SWAG from Letsencrypt, but it doen't seems to be related to it since it happens even with the docker stopped. It makes the box unresponsive, you can't even shut it down from command line. After every hard reboot all works well for a few hours until the errors come back and then I can't access several feature from the UI. I rolled back to 6.7.0 and uninstalled CA with the same results... Dec 28 07:29:40 TOWER nginx: 2020/12/28 07:29:40 [error] 9330#9330: *241606 upstream timed out (110: Con
  2. Hi there, I posted the problem I'm facing on the Unraid general support but I received no replies. I'm hoping I can get some feedback here. I changed from Letsencrypt to Swag recently and after the change i lose access to multiple sections in Unraid and all dockers stop functioning properly... I lose access thru the UI to the Dashboard, Docker and the bottom portion of the Main tab. The console gets unresponsive to any docker command and to the "powerdown" capability so every time I restart the system it has to do a parity check. Of course none of the apps using the reverse proxy are work
  3. I lost access to the Dashboard, Docker, Apps... any suggestion would be greatly appreciated.
  4. Hi there, I'm having an issue with the docker service after I added a cache drive and updated Letsencrypt to Swag. After restarting the system the logs show the following error while I can't access the different docker's UIs: nginx: 2020/10/12 10:06:48 [error] 32315#32315: *246154 upstream timed out (110: Connection timed out) while reading response header from upstream, client ... upstream: "fastcgi://unix:/var/run/php5-fpm.sock" ... I also lose the "powerdown" capability thru the console or the UI so every time I restart the system it has to do a parity check. Any ideas?
  5. Yes, it's a "downloads" pivot folder monitored by other apps. The system was doing just fine with the small SSD, the issue started once I started downloading too many large files. The files needed to stay longer for seeding which tested the limit of the drive. Definitely poor balance from my side, nothing to blame on the software. I now want to increase the cache size to have more capacity. After reading the FAQ in more detail, I'll balance the cache into single mode.
  6. The UI is showing the cache space increased after adding the drive. No writes into the new drive so I assume that is just a limitation. Well, I deleted some files and now the cache utilization is below the capacity of the original, smaller cache drive. Can I go ahead and perform a balance to convert the cache to Raid0 while having still some data in the drive?
  7. Hi there, I'm not sure how to best describe the issue I'm experiencing so I'll make a list of what happened: 1. I had Deluge downloading very large files, all working as expected 2. The temporary download folder in the cache drive reached its limit after a while. Basically the single SSD I had at that time was filled to the brim. 3. I ignored the system for a couple of days which resulted in all docker apps crashing. They were all on red and the Fix Common Problems plugin was showing some error with the docker image. 4. I added a new SSD to the system, which was recognize
  8. I initially made a huge bulk import... all releases are in their folders. Clearing the queue definitely resolved the issue. I went to the Queue tab in the Activity screen and delete all from download client. Now the logs are clean of import service errors. Thanks again for all the assistance!
  9. That didn't help... The import service is looking for versions never downloaded... all releases in both libraries (Radaar and Sonaar) are flagged "downloaded". I'm stuck, I don't understand yet the process of importing. Why, if a release is already flagged as downloaded, the import service continues trying to retrieve it from the download folder?
  10. That's exactly what's happening... I tried a fresh request and it worked just fine. On the other hand, Sonaar and Radarr are still looking for releases already downloaded. Not sure how to clear that queue. Thanks for all the help!
  11. I changed the path to the Sabnzbd categories and it didn't help. I then changed its download folders to absolute paths but it didn't resolve the issue. Logs continue showing the default path. Note I restarted all three dockers. Screenshot to User Folders in Sabnzbd: Previous step changed the path for the categories folders. They are now relative to /downloads: After all this, the logs keep showing the default path: Is there any other log I can enable that can provide more info?
  12. I'm going to try changing the path of Sabnzbd categories to absolute paths. Right now they are using the default, relative folders are based on: /config/Downloads/complete. This should fix it... Thanks for pointing this out!
  13. I posted this in Radaar and Sonaar support forums but it looks to me this is a Docker issue... Something is off and I can't find where the issue lies... Radarr and Sonarr are not looking for the downloads folder in the correct path. Sonarr log message: Import failed, path does not exist or is not accessible by Sonarr: /config/Downloads/complete/tv/ Radarr log message: Import failed, path does not exist or is not accessible by Radarr: /config/Downloads/complete/movies/ For some reason Raddar and Sonnar are looking under the config folder instead of the
  14. Actually this morning I resumed Screen and everything seems to be right. Updates are showing in intervals as usual but after a while it stopped receiving them again... very weird. I'm just letting it run until HD activity light goes off.
  15. Hello there... I'm running the preclear script (v1.13) on a 4TB HGST Deskstar HDS724040A through Screen in a telnet session. (5.0-rc13) The issue is the telnet windows stopped receiving updates. After an hour or so the screen just stop reseting the temperature, the elapsed time clock, etc. I tried twice running it in this drive with the same result but at different times. Fisrt when writing zeroes and the second time while the initial reading. The first time I thought the script halted, I panicked, and I restarted the box. The second time I looked deeper - I still see the preclear_di