June 1, 20197 yr Hello My Problem startet with not being able to stop or restart a Docker Container. (Still not able) Then i noticed im not able to Update a Docker Container. Now i wanted to reboot or shutdown my System and this doesn't work aswell. I also tried shutdown now -r in console with no success. Im getting the following error message: Jun 1 10:28:47 unRAID nginx: 2019/06/01 10:28:47 [error] 5296#5296: *2759839 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.10.10.21, server: , request: "POST /webGui/include/Boot.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "10.10.10.10", referrer: "http://10.10.10.10/Dashboard" Also this keeps coming up every 5 minutes Quote Jun 1 10:55:01 unRAID Parity Check Tuning: DEBUG: -----------MONITOR start------ Jun 1 10:55:01 unRAID Parity Check Tuning: DEBUG: Monitor: No array operation currently in progress Jun 1 10:55:01 unRAID Parity Check Tuning: DEBUG: -----------MONITOR end------- Thanks for any help
June 1, 20197 yr Community Expert Try to get diagnostics before rebooting if possible. See the "Need Help?" sticky pinned near the top of this same subforum: https://forums.unraid.net/topic/37579-need-help-read-me-first/
June 1, 20197 yr Author Thank you for responding. I have attached the requested diagnostics file. unraid-diagnostics-20190601-1125.zip
June 1, 20197 yr Community Expert 5 hours ago, Regency said: Also this keeps coming up every 5 minutes Quote Jun 1 10:55:01 unRAID Parity Check Tuning: DEBUG: -----------MONITOR start------ Jun 1 10:55:01 unRAID Parity Check Tuning: DEBUG: Monitor: No array operation currently in progress Jun 1 10:55:01 unRAID Parity Check Tuning: DEBUG: -----------MONITOR end------- Thanks for any help That means : You have the Parity Check Tuning plugin installed AND you have the option in its settings for debug logging enabled AND you have the option to pause/resume long running array operations on disk temperature thresholds enabled Changing any of these conditions will stop these messages happening every 5 minutes. Simply turning off the 3rd option reduces the messages to a few messages a day. I could change the plugin to write its log elsewhere but having it in the syslog helps with keeping items in the correct order with other events going on in the server when investigating problems. I had also assumed that the average user would not leave the debug logging enabled unless they were experiencing problems. With the debug logging turned off one should only get messages from the plugin when it takes some action. BTW: The plugin will not be what is stopping your server from shutting down. The plugin takes no actions that can cause that to happen so you need to look elsewhere for the reason. Edited June 1, 20197 yr by itimpi
June 1, 20197 yr Author I disabled the plugin for the time being. As itimpi pointed out this didn't solve my problem. Last change i made to the server was installing Android-8.0 App from CA. I tested it out and it worked fine at first but then got stuck. Now i am unable to stop or uninstall it, do any docker updates, reboot or shutdown my system and even htop isn't working in the webterminal. Should i just pull the plug?
June 1, 20197 yr Community Expert 1 hour ago, Regency said: I disabled the plugin for the time being. As itimpi pointed out this didn't solve my problem. Last change i made to the server was installing Android-8.0 App from CA. I tested it out and it worked fine at first but then got stuck. Now i am unable to stop or uninstall it, do any docker updates, reboot or shutdown my system and even htop isn't working in the webterminal. Should i just pull the plug? Didn't really notice anything in the syslog but my guess is you have corrupted docker image by overfilling it. You have it set larger than is usually required, and it has more space used than it should. Delete docker image and recreate it at only 20G. While on that page turn on log rotation. Making docker image larger isn't the solution to filling it, it just makes it take longer to fill. You can reinstall your dockers exactly as they were using the Previous Apps feature on the Apps page, but you should consider if any of them are misconfigured and filling your docker image. The usual way docker image gets filled is by having an application write to a path that isn't mapped to a host path. Typical mistakes are specifying a different upper/lower case (Linux is case sensitive) or using a relative path instead of an absolute path (beginning with /). See "Docker Image Filling Up" section in the Docker FAQ: https://forums.unraid.net/topic/57181-real-docker-faq/
June 2, 20197 yr Author I tried to disable docker in the settings tab, but it wont give me any settings to change docker img size. This might be the case because it's not able to stop all Containers. (Half of my Containers are still running and unable to stop) Then i deleted the Docker img but that didn't seem to have any effect. The WebUI in the bottom left is telling me "Starting services..." If i try to open the log it's loading infinitely. It seems like i have no control over my server what so ever now.
Archived
This topic is now archived and is closed to further replies.