optiman

Members
  • Posts

    1077
  • Joined

  • Last visited

Posts posted by optiman

  1. I disabled the EPC and did the upgrade and haven't had any issues.  I guess the EPC was the issue, because as I mentioned in my other post, I wasn't able to disable the lowpowerspinup.  As long as you disabled EPC, you should be good to go.

     

    Based on input from others, it sounds like future unraid version will not effect us.  The issue is with LSI and Seagate.  We need updated LSI drivers that address this, or updated fw from Seagate that addresses these issues.

     

    For me, I'm moving back to WD drives.  I used those for years without any issues.

    • Thanks 1
  2. @Squid  new issue that may be related.  When I go to the Plugins page, the status for each plugin says Unknown.  I click on the Plugins header at the top and it will come back after only 10 - 20 seconds and say unknown for status.  I have to do this 5 or 6 times and then it will take about 2 or 3 minutes to come back and then say Up to Date.  I've never had this issue before.

     

    Now looking at my Docker page, it now says up-to-date.  However, if I click on the Check for Updates at the bottom, each one just spins, same as before and I get the error in the syslog.  The docker page never recovers, will spin forever until I go to another page, Main for example.  When I go back to the Docker page, it will say up-to-date.  So the check seems to work (maybe), but given the syslog errors and the fact that the docker page never refreshes, something is still wrong.

     

    I've tried changing to another ISP DNS, but that didn't help.

     

    Any ideas?

     

     

     

    tower-diagnostics-20210929-0542.zip

  3. When I try to Check For Updates on the Docker page, each docker just spins forever.

     

    I see this error in the syslog

     

    Sep 23 15:43:25 Tower nginx: 2021/09/23 15:43:25 [error] 8444#8444: *269827 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.11.79.248, server: , request: "POST /plugins/dynamix.docker.manager/include/DockerUpdate.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "10.11.79.162", referrer: "http://10.11.79.162/Docker"

     

    Any ideas?

  4. Ok, changed it back and restarted the Docker service, and again when I check for updates, same thing, just spins and times out. wtf

     

    Sep 23 15:43:25 Tower nginx: 2021/09/23 15:43:25 [error] 8444#8444: *269827 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.11.79.248, server: , request: "POST /plugins/dynamix.docker.manager/include/DockerUpdate.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "10.11.79.162", referrer: "http://10.11.79.162/Docker"

     

    As suggested, I started a new topic

  5. upgraded to 6.9.2 and still the docker update issue continues

     

    Sep 22 19:02:26 Tower nginx: 2021/09/22 19:02:26 [error] 8444#8444: *6597 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.11.79.248, server: , request: "POST /plugins/dynamix.docker.manager/include/DockerUpdate.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "10.11.79.162", referrer: "http://10.11.79.162/Docker"

     

  6. thanks guys!  My issue is that the instructions to disable the lowcurrentspinup did not work for me on any of my drives.  Even after cold boot, they show that feature is still enabled.  Weird because after issuing the command, it says it successfully disabled that feature and a reboot is required, yet the feature is still enabled.

     

    I guess I will just have to take a chance and upgrade. 

     

    So what should I watch for?  Errors in the syslog, disk log, SMART log?  Will the main screen show the errors counting up?

    image.png.2e0b64988c51ce7559cc9b0ada322db6.png

     

    And if I do see errors, what should I do, roll back ASAP.  I don't want to loose data.

     

    Thanks!

  7. I decided to try the fix so that I can upgrade to the latest unraid version.

     

    I followed the instructions exactly and each time I saw a response saying that lowpowerspinup was disabled.  it also says you have to reboot to take effect.  I did this on all 10 of my seagate drives.  I cold booted and went back to confirm and none of them are disabled, all show lowcurrentspinup enabled.  I even turned off my power supply switch.  The only thing I didn't try was unplugging the power cord from the power supply.  The EPC steps worked fine and all 10 show disabled now.

     

    I'm worried about trying the 6.9.2 upgrade while the lowcurrentspinup is still enabled.

     

    I didn't get any errors and the seachest version I used was SeaChest_Configure_1170_11923_64

     

     Drive models are ST12000NE0008 and ST8000NM0055

     

    Any ideas?

     

  8. I was able to change the file and copy it over the existing file.

     

    I copied to a user share using MC, then to my pc and used Notepad++

     

    Here is what my line 457 looks like"

     

    preg_match('@Docker-Content-Digest:\s*(.*)@i', $reply, $matches);

     

    I then copied the updated file back to my user share and then again used MC to copy it / overwrite the existing.  I then enabled Docker in Settings and tried again.  It did not help.

     

    Do i need to reboot?

     

    Rebooted and it seems to be back to normal now.  Thanks!

  9. On 5/14/2021 at 6:30 AM, HyperV said:

    I had exactly the same issue and could not find any solutions on the forum or the internet. So I did some digging myself and found the cause of the issue. The docker update check script gets the remote digest of the latest tag from the docker repository via a header called 'Docker-Content-Digest'. The script checks for this header with a case-sensitive regex pattern. Manually querying the docker hub registry gives me a header called 'docker-content-digest' (mind the casing). The docker hub registry must have recently changed the casing of this header, because it broke for me in the last 24 hours. I'm running on Unraid 6.8.3 still, so I'm not 100% sure if this issue also exists in 6.9.x.

    If you feel up to it, you could quite easily fix this yourself until there is a real fix. I'll describe the steps below:

    Open file: /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php

    Go to line 457.

    There you should look for the text:

    @Docker-Content-Digest:\s*(.*)@

    and replace it with:

    @Docker-Content-Digest:\s*(.*)@i


    Save the file.

    This will make the header check case-insensitive and should make it work again.

    I tried this and I get Access Denied when I try to save it.  I've disabled Docker in Settings.  How did you get around that?

  10. All of my dockers are no longer able to check for updates and when I chick on the button to Check, they all spin for a long time and then it times out.  Something has changed.  I can do a Force update and those work fine.  Any idea why this is happening?

     

    image.png.27b7fc5b74317f66c167f90ab0d4f1b9.png

    error in syslog:

     

    Sep 17 07:48:54 Tower nginx: 2021/09/17 07:48:54 [error] 8396#8396: *911273 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.11.79.248, server: , request: "POST /plugins/dynamix.docker.manager/include/DockerUpdate.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "10.11.79.162", referrer: "http://10.11.79.162/Docker"

     

  11. @binhex

     

    All of my dockers are no longer able to check for updates and when I chick on the button to Check, they all spin for a long time and then it times out.  Something has changed.  I can do a Force update and those work fine.  Any idea why this is happening?

    image.png.1f391184795c7f6c61686ca1660f532f.png

     

    error in syslog:

     

    Sep 17 07:48:54 Tower nginx: 2021/09/17 07:48:54 [error] 8396#8396: *911273 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.11.79.248, server: , request: "POST /plugins/dynamix.docker.manager/include/DockerUpdate.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "10.11.79.162", referrer: "http://10.11.79.162/Docker"

    Sep 17 07:48:54 Tower nginx: 2021/09/17 07:48:54 [error] 8396#8396: *911273 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.11.79.248, server: , request: "POST /plugins/dynamix.docker.manager/include/DockerUpdate.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "10.11.79.162", referrer: "http://10.11.79.162/Docker"