• 6.6.0-rc1 Docker and Apps Tab dont work anymore


    DaLeberkasPepi
    • Retest Minor

    Hello,

     

    it seems like the docker and apps tab dont get properly loaded anymore, this effects also the docker sektion of the dashboard tab. The Apps tab keeps showning "Updating Content" and the docker tab keeps looking for dockers. The dockers themself still run as like nothing happened but i dont have access to them trough the website anymore.

     

    image.thumb.png.e0cd5f06b8a140f14f657fa4f40cc185.png

    image.thumb.png.2bcc5f3f549be941fac1e98877a61c2c.png

    image.thumb.png.4f0943803fea16416ac707cb9470a923.png

    image.thumb.png.a32954294d65c4fb29aed8c7661817d0.png

    homeserver-diagnostics-20180904-2259.zip




    User Feedback

    Recommended Comments

    i am now running in safe mode but i had to force shutdown the server with the power button. It got stuck on shutting down emhttpd.

     

    as a side note: is it normal that the ups looses connection in safe mode?

    Link to comment

    Why is your docker image 50G? That often indicates a user has been running out of space in docker image due to misconfigured dockers, so they try to fix it by increasing space. Most people never use anywhere near 20G if they have things configured correctly.

     

    You also have a surprisingly large number of share .cfg files. Maybe some of these are no longer in use, or maybe you just have a lot more shares than you intended. This can also be a sign of misconfigured dockers.

    Link to comment

    image.png.edaab9c99b382ac48e67abd4293f0143.png

     

    nope only use 10G. Thats probably just from testing around and still got stuck and im not in the mood of recreating all my dockers even though it only takes lake 10 minutes or so ^^

     

    what do you mean by share .cfg files? Do you mean the actual share count active or do you mean share .cfg including old deleted shares.

     

    Nevermind it shouldnt be neither of those problems, because i have those dockers running mostly since 2 years with only updating them and testing and deleting some other ones for testing and so on. And as you could see my docker file is just 10gb. Also if the docker file would be too big the dockers wouldnt work after some time anymore and they ran without a problem i just couldnt controll them using the website.

     

    the second statement also shouldnt be the problem because this has been running with 6.5.3 with over 40days without any problem and without restart.

    Link to comment

    The unRaid UI has a 120 second time out.  When you hit the docker tab, this happened

    Sep  4 22:44:28 HomeServer nginx: 2018/09/04 22:44:28 [error] 14423#14423: *321832 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.126, server: , request: "GET /plugins/dynamix.docker.manager/include/DockerContainers.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "1422ea8d47b47bc6e9dc7b17038a996b4f72ed75.unraid.net", referrer: "https://hash.unraid.net/Docker"
    

    Along with the Dashboard (This one happened first)

     

    Sep  4 19:55:31 HomeServer nginx: 2018/09/04 19:55:31 [error] 14423#14423: *296165 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.126, server: , request: "POST /webGui/include/DashboardApps.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "1422ea8d47b47bc6e9dc7b17038a996b4f72ed75.unraid.net", referrer: "https://hash.unraid.net/Dashboard"
    

     

    The same thing happened when you hit the apps tab

    Sep  4 22:59:32 HomeServer nginx: 2018/09/04 22:59:32 [error] 14423#14423: *324436 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.126, server: , request: "POST /plugins/community.applications/include/exec.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "homeserver.local", referrer: "https://homeserver.local/Apps"
    

    CA times out on any particular download after 45 seconds, so in *theory* you should not have seen the timeout from CA.  *in theory*  Very hard situation for me to replicate, and try to alleviate.  

     

    As far as CA is concerned, I can tell you that if the initial popup regarding "Downloading New App List" doesn't disappear within 120 seconds (which it should within max ~90 seconds, usually 1 second), it will never disappear.  But, if you wait a couple min, and then go into the Apps tab, everything *should* be good to go.

     

    Major Wild Guess:  Is it possible that it was your browser that crashed and was unresponsive?  Closing the browser, and going back to the server's UI does that fix the problem?  There's no real reason that I see for the problems that you've seen beyond that.

    Link to comment

    the apps tab didnt timeout with an message it just got stuck on "Updateing Content" for several minutes. I also tested the browser on my phone and at least the dashboard didnt show my running docker containers either. I didn't test apps and docker tab on my phone.

     

    Right now im running in safe mode so i'll see what happens.

     

    The strange was that only webpages that had something to do with my running docker containers had problems with that. The rest of the dashboard worked without a problem it just didnt show my running docker containers. And the 

    docker container ls

    command still showed my running dockers (which all ran just fine)

     

    i've just added my latest syslog which i copied over before i used the shutdown power button and subsequently after that holding down the power button till complete shutdown, because the system didnt shutdown itself properly. Sadly i dont have a log from that.

     

    But what i found was the subsequent trys to access the docker tab and also me trying it on my phone.

    Sep  4 23:01:34 HomeServer nginx: 2018/09/04 23:01:34 [error] 14423#14423: *325037 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.193, server: , request: "POST /webGui/include/DashboardApps.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "1422ea8d47b47bc6e9dc7b17038a996b4f72ed75.unraid.net", referrer: "https://1422ea8d47b47bc6e9dc7b17038a996b4f72ed75.unraid.net/Dashboard"
    Sep  4 23:06:44 HomeServer nginx: 2018/09/04 23:06:44 [error] 14423#14423: *324436 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.126, server: , request: "GET /plugins/dynamix.docker.manager/include/DockerContainers.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "homeserver.local", referrer: "https://homeserver.local/Docker"
    Sep  4 23:07:53 HomeServer nginx: 2018/09/04 23:07:53 [error] 14423#14423: *324436 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.126, server: , request: "POST /plugins/community.applications/include/exec.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "homeserver.local", referrer: "https://homeserver.local/Apps"
    Sep  4 23:08:43 HomeServer login[6602]: ROOT LOGIN  on '/dev/pts/0'
    Sep  4 23:09:52 HomeServer nginx: 2018/09/04 23:09:52 [error] 14423#14423: *326783 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.126, server: , request: "POST /webGui/include/DashboardApps.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "homeserver.local", referrer: "https://homeserver.local/Dashboard"
    Sep  4 23:11:13 HomeServer nginx: 2018/09/04 23:11:13 [error] 14423#14423: *326783 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.126, server: , request: "POST /plugins/community.applications/include/exec.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "homeserver.local", referrer: "https://homeserver.local/Apps"

    192.168.1.193 is the ip from my phone.

     

     

    syslog.txt

    Edited by DaLeberkasPepi
    added latest syslog just before force shutdown
    Link to comment

    Is it possible you have an adblocker or similar in your browser, and it is just getting tripped up with the new release? You should whitelist your server if you haven't. Also might be worth clearing browser cache since it sounds like this might just be a problem with the UI on your system. Have you tried another browser?

    Link to comment
    4 hours ago, DaLeberkasPepi said:

    the apps tab didnt timeout with an message it just got stuck on "Updateing Content" for several minutes. I also tested the browser on my phone and at least the dashboard didnt show my running docker containers either. I didn't test apps and docker tab on my phone.

    That was more or less my point.  CA never timed out, but rather the GUI hit it's hard limit of 120 seconds on any request at which point the GUI will not return a result for the request (success or failure)

     

     

    What containers are you running?

    Link to comment
    On 9/6/2018 at 3:48 AM, trurl said:

    Is it possible you have an adblocker or similar in your browser, and it is just getting tripped up with the new release? You should whitelist your server if you haven't. Also might be worth clearing browser cache since it sounds like this might just be a problem with the UI on your system. Have you tried another browser?

    like i mentioned in my previous post it also tried it on my smartphone and i got the same result and i dont even have an adblocker on my smartphone, sadly.... And i also did whitelist the webinterface long ago on my desktop pc, thanks to the fix common problems plugin.

     

    And i had those dockers running at the time i couldn't access the docker tab anymore (in fact those are the only ones that were running since the 6.6rc1 update. I have other dockers but those i never started with the new update):
    Thats also the picture i added at the OP

    image.png.e79609a159f07e2edfb5810b5173ecbb.thumb.png.3cef80312850ad320ead213ad0b41ceb.png

    Edited by DaLeberkasPepi
    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.