davper

In regards to the docker image being corrupt... How can you tell? Is it one docker in particular or is it all of them? In previous posts instructing to fix, you mention remove the image. Needing to be sure because the steps looks like they have changed... Is this done in the docker tab and clicking on the docker icon to select remove and then you get the pop-up (shown below). If correct, do I need to backup anything before doing this or is the info contained elsewhere and it will remember the previous info?

I keep freeing up space manually, but the mover is not doing anything and the cache fills back up. I did a hard reboot about 2 hours ago because it would not gracefully reboot on its own. Shut down all the dockers and started the mover. Main page says mover is running, but log doesn't even indicate that it started. Is the only way to stop the mover, so I can restart it, to do a reboot?

What did you see in the log that led you to deleting those files? I had seen that mover attempted to move them but they were still on the /mnt/cache/ drive when I checked. So using the console, I deleted them already. But I deleted them from mnt/cache/ not disk 1/2. Is that OK? The cache pool was at one time 2 drives. I started with a 250GB and then later added the 500GB when I got deal when buying 2. One was for a laptop and threw the 2nd into unraid. At the time, it showed my cache increasing in size. But I later learned that this was a false report and removed the smaller one. The other laptop is no longer in use so I will grab that drive and add it to the pool.

Hi My mover hasn't been working correctly and my cache just fills up. The only way I have been able to get it to work at all, is to reboot unraid. This forces the mover to stop so I can start it again. I also need to shut down all dockers. Checking the logs, the mover works for a short time and then goes hours without any activity in the logs. In checking the logs, I am seeing all kinds of errors. Some errors I have been able to google a solution for. And I have made fixes based on info found. But it seems after I fix one, 2 more popup. And most are greek to me. I suppose many of these errors are stemming from my power going out every few hours lately. I hear the unmistakable sound of a transformer blow, and I hold my breath waiting for the power to go out. Last night a transformer blew, fell to the ground and burned white light like a welding torch. This morning, 2 poles from there, a truck took out the pole. I have lost power 4 times in less than 12 hours. UPS is on order. I am asking 2 things from you: Feed me a fish today by looking at my diagnostics and tell me what is wrong. Teach me to fish so that I can troubleshoot this crap on my own. Is there a listing of common errors that I can reference? How do many of you just look at the log and know what to fix? I really wish you guys would highlight the line on the log that gave you the clue of what was wrong in the post. People ask for help, post there logs and someone says do this. I want to how you know and why that is the fix. Are there tools that you use to read the logs that highlight issues. I have been using notepad++ and scanning each line. is there a log monitoring tool (reasonable cost for the home user) that will alert me when it encounters an error in real-time so I don't have to learn about issues after it is too late. Please and Thank You tower-diagnostics-20210727-1427.zip

Disregard. For the last 12 hours, I have been unable to connect. Then when I post for additional help, it resolves itself. effin gremlins!

Hi Just installed the docker on my unraid and it appeared to install correctly and is running on my server. But when I try to go to the webui, I get a "refused to connect" error. I left the ports at default, confirmed there is no conflict with another docker. I tried using the unraid menu to connect and typing the address and port directly in the browser. All other dockers work fine. I just installed a pfSense hardware router and am still learning its voodoo. It is mostly default configuration. I see no rules that exclude my unraid server or ports 7803/7903. So I don't think that is it. But I tried making a rule to allow all ports on the unraid server and placed it 2nd in priority behind the anti lockout rule. Again, I am new to pfsense and firewall rules, so I may have done that wrong. Please and Thank you

about 2 weeks after installing Sickchill on my unraid, I get "Refused to Connect" error when I try to log into the gui. It is still trunning and doing it's job in the background, but I can't log into the gui. I can log into every other GUI with no problem. What would be causing this and how do I fix? Unraid Ver 6.5.3 Can't see ver of Sickchill Here is the log from the docker: 2019-01-26 10:42:58.485199 [info] Host is running unRAID 2019-01-26 10:42:58.512301 [info] System information Linux 1dd50a0c82bb 4.14.49-unRAID #1 SMP Mon Jun 11 16:21:07 PDT 2018 x86_64 GNU/Linux 2019-01-26 10:42:58.547303 [info] PUID defined as '99' 2019-01-26 10:42:58.604592 [info] PGID defined as '100' 2019-01-26 10:42:58.673902 [info] UMASK defined as '000' 2019-01-26 10:42:58.704887 [info] Permissions already set for volume mappings 2019-01-26 10:42:58.830231 [info] Starting Supervisor... 2019-01-26 10:42:59,191 INFO Included extra file "/etc/supervisor/conf.d/sickchill.conf" during parsing 2019-01-26 10:42:59,191 INFO Set uid to user 0 succeeded 2019-01-26 10:42:59,194 INFO supervisord started with pid 7 2019-01-26 10:43:00,196 INFO spawned: 'sickchill' with pid 49 2019-01-26 10:43:00,196 INFO reaped unknown pid 8 2019-01-26 10:43:01,198 INFO success: sickchill entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2019-01-26 10:43:03,642 DEBG 'sickchill' stderr output: 10:43:03 INFO::MAIN :: 79173: Unable to find IMDb show info in the database 2019-01-26 10:43:03,959 DEBG 'sickchill' stderr output: 10:43:03 INFO::MAIN :: 342225: Unable to find IMDb show info in the database ~Repeated 22 more times 2019-01-26 10:43:11,222 DEBG 'sickchill' stderr output: 10:43:11 INFO::MAIN :: Starting SickChill [master] using '/config/config.ini' 2019-01-26 10:43:11,238 DEBG 'sickchill' stderr output: 10:43:11 INFO::TORNADO :: Starting SickChill on http://0.0.0.0:8082/ 2019-01-26 10:43:11,238 DEBG 'sickchill' stderr output: 10:43:11 INFO::CHECKVERSION :: Checking for updates using SOURCE 2019-01-26 10:48:03,522 DEBG 'sickchill' stderr output: 10:48:03 INFO::POSTPROCESSOR :: Auto post processing task for /media/appdata/data/Complete was added to the queue 2019-01-26 10:48:06,515 DEBG 'sickchill' stderr output: 10:48:06 INFO::POSTPROCESSOR-AUTO :: Beginning auto post processing task: /media/appdata/data/Complete 2019-01-26 10:48:06,517 DEBG 'sickchill' stderr output: 10:48:06 INFO::POSTPROCESSOR-AUTO :: Processing /media/appdata/data/Complete 2019-01-26 10:48:06,589 DEBG 'sickchill' stderr output: 10:48:06 INFO::POSTPROCESSOR-AUTO :: Successfully processed 2019-01-26 10:48:06,590 DEBG 'sickchill' stderr output: 10:48:06 INFO::POSTPROCESSOR-AUTO :: Auto post processing task for /media/appdata/data/Complete completed 2019-01-26 10:53:03,818 DEBG 'sickchill' stderr output: 10:53:03 INFO::DAILYSEARCHER :: Searching for new released episodes ... 2019-01-26 10:53:04,029 DEBG 'sickchill' stderr output: 10:53:04 INFO::DAILYSEARCHER :: No new released episodes found ... 2019-01-26 10:53:08,818 DEBG 'sickchill' stderr output: 10:53:08 INFO::SEARCHQUEUE-DAILY-SEARCH :: Beginning daily search for new episodes 2019-01-26 10:53:28,284 DEBG 'sickchill' stderr output: 10:53:28 INFO::SEARCHQUEUE-DAILY-SEARCH :: No needed episodes found 2019-01-26 10:58:04,123 DEBG 'sickchill' stderr output: 10:58:04 INFO::POSTPROCESSOR :: Auto post processing task for /media/appdata/data/Complete was added to the queue 2019-01-26 10:58:07,106 DEBG 'sickchill' stderr output: 10:58:07 INFO::POSTPROCESSOR-AUTO :: Beginning auto post processing task: /media/appdata/data/Complete 2019-01-26 10:58:07,108 DEBG 'sickchill' stderr output: 10:58:07 INFO::POSTPROCESSOR-AUTO :: Processing /media/appdata/data/Complete 2019-01-26 10:58:07,863 DEBG 'sickchill' stderr output: 10:58:07 INFO::POSTPROCESSOR-AUTO :: Successfully processed 2019-01-26 10:58:07,864 DEBG 'sickchill' stderr output: 10:58:07 INFO::POSTPROCESSOR-AUTO :: Auto post processing task for /media/appdata/data/Complete completed

OK, I got the Docker service running by increasing the size of my image from 20GB to 30GB. I need to spend time understanding why the space gets filled up without adding more dockers. That is a task for another day when I am not so swamped. Thank you for the info.

Thanks for responding. But this appears to be step 2. I still need to recreate the Docker.img. Also, keep in mind that my Docker tab is blank.

Hi After running without issue for the last year or so, My dockers are not appearing, the Docker tab gives a blank page, and my log says I have no space left. I can't remember the last time I installed a new docker. My existing drives and shares all have space left. Albeit they are getting full. I have just received in 2 new larger drives to replace a couple of smaller drives. After doing a search, it appears that I have to delete my docker.img and rebuild it. But I haven't found out how to do that. I am a windows guy and rely on the Unraid gui for getting things done. While I have edited in linux, I really haven't done any systems work. So I need instructions. I checked the FAQ Contents and didn't see anything related. Please and Thank You tower-diagnostics-20180712-1145.zip