• [6.12.4/5/6] Major GUI delays after upgrade (specially dashboard, docker and apps tab)


    unCoreX
    • Solved Urgent

    Hi, after upgrading from 6.12.3 to 6.12.4 my Webui has been very slow. Special on docker tab and dashboard.

    Takes almost 12 sec before the page is visible. I can see my CPU are wokring MUCH more when i try to open DOCKER tab or the Dashboard.
    Never seen a behaver like this before. I tried to stop Array, but Dashboard is still slow 12 seconds to open it, normally it tooks 2 seconds.
    Tried to remove some plugins, but still the same

    EDIT 1:
    After removing more plugins and multiple reboots. The issue is till there.

     

    EDIT 2: I decide to revert back to 6.12.3. And guess what, it working normally again, fast like it always was :)
    So can someone please explain me why I had this kind of issue with 6.12.4 ?

    EDIT 3: Tested v.6.12.5 RC 1 and the latest version released yesterday, v.6.12.5. It's still the same.
    Adding the diagnostics from my backup server (Galactica)
     

     

     

    • Like 1
    • Upvote 2



    User Feedback

    Recommended Comments



    Tested the latest release 6.12.6.

    Still the same.  Any devs looking at this issue? I'm not the only one here with the same issue I see.

     

    Edited by CiscoCoreX
    Link to comment
    17 hours ago, CiscoCoreX said:

    I'm not the only one here with the same issue I see.

     

    Just wanted to weigh in I'm experiencing this _exact_ issue.  Thanks for all the work to test and report back; you're definitely not alone in experiencing this.

    Link to comment

    It is unclear why this is happening, could be specific to your set up.

     

    Try the following

     

    1. Make a backup of your current flash device, see Main -> Flash -> Flash Backup

    2. Install the plugin “Dynamix Factory Reset”

    3. Do a factory reset and keep your disk assignments.

    4. After a reboot the system has all default settings

     

    Check the behavior of the GUI in this state

     

    You can restore docker containers by installing CA and use it to do a restoration (make sure your docker settings are correct before doing so)

     

    Configure your VM settings as required and re-install VMs by creating a new VM and select the existing image.

     

    If desired you can always restore the flash device from the backup using the creator tool.

     

     

    Link to comment

    This is not about hiding a bug, but starting from scratch and add things back to determine when and where it goes wrong.

     

    • Upvote 1
    Link to comment
    15 hours ago, bonienl said:

    This is not about hiding a bug, but starting from scratch and add things back to determine when and where it goes wrong.

     

    Hi, give me a day or two. Then I'm going to do an clean install + just add my license key.
    I did this on an early post here, I think it was on version 6.12.4. Then same problem.

    Link to comment

    I'm also experiencing the same problem with 6.12.6 after recently upgrading from 6.11.5.  Currently rolled back to 6.11.5 waiting for a resolution to this.

    Link to comment
    On 12/6/2023 at 5:47 AM, bonienl said:

    It is unclear why this is happening, could be specific to your set up.

     

    Try the following

     

    1. Make a backup of your current flash device, see Main -> Flash -> Flash Backup

    2. Install the plugin “Dynamix Factory Reset”

    3. Do a factory reset and keep your disk assignments.

    4. After a reboot the system has all default settings

     

    Check the behavior of the GUI in this state

     

    You can restore docker containers by installing CA and use it to do a restoration (make sure your docker settings are correct before doing so)

     

    Configure your VM settings as required and re-install VMs by creating a new VM and select the existing image.

     

    If desired you can always restore the flash device from the backup using the creator tool.

     

     

    Hi,

    - I just did an clean install of the latest version 6.12.6. Just downloaded the zip file and extracted to my USB pen and copy my license key.
    - Booted up my backup server

    - Made a new root password.

    - Signed in for the first time

    - First time it goes ti the MAIN page. I didn't assiged any disk this time. No Arrray or Cache.
    Now the speed is much more normal, around 1 - 2 seconds when I go back to Dashboard page from any other page.
    image.png.83576b4a5a95f286ded63bf917c308c1.png
     

    - Next thing I did was changing the timezone, after that the problem start again. Slow Dashboard, almost 20 seconds.

    I change back do default settings in the "Time and Date" but still same, slow Dashboard. Rebooted the server.

    - But that didn't help. So the problem is back. Slow, Did another reboot.

    - Same again after a reboot.

    - I turn off use NTP and rebooted again. Same problem. I don't believe NTP has something to do with this slow pages.

    image.png.2b247e4ffc431be3e0bd50bd252400b3.png

     

    So what has changed since 6.12.3 to 6.12.4 when my problem start?
    My primary server are stuck on version 6.12.3

     

     

    Edited by CiscoCoreX
    Link to comment

    Please test the following to see what is being executed while the delay happens:

     

    1. Open /etc/php-fpm.d/www.conf
    2. Uncomment ";slowlog ="
    3. Adapt the same line to "slowlog = /var/log/php.slow.log"
    4. Uncomment ";request_slowlog_timeout = 0"
    5. Change the same line to "request_slowlog_timeout = 10"

     

    Open a terminal (SSH) and type in "/etc/rc.d/rc.php-fpm restart"

     

    Try to reproduce the delay. After this, Upload the file at /var/log/php.slow.log here. Then please add a semicolon (;) to BOTH changed lines again and restart PHP-FPM again.

     

    This will show us a trace on the portion of code, which lasts longer than 10 seconds.

     

    Offtopic: The Pool Config could get updated to latest package templates - inside of the current one there still PHP5 metioned. The nginx socket paths could get updated too..

    Edited by KluthR
    • Like 1
    Link to comment
    On 12/9/2023 at 5:17 PM, KluthR said:

    Please test the following to see what is being executed while the delay happens:

     

    1. Open /etc/php-fpm.d/www.conf
    2. Uncomment ";slowlog ="
    3. Adapt the same line to "slowlog = /var/log/php.slow.log"
    4. Uncomment ";request_slowlog_timeout = 0"
    5. Change the same line to "request_slowlog_timeout = 10"

     

    Open a terminal (SSH) and type in "/etc/rc.d/rc.php-fpm restart"

     

    Try to reproduce the delay. After this, Upload the file at /var/log/php.slow.log here. Then please add a semicolon (;) to BOTH changed lines again and restart PHP-FPM again.

     

    This will show us a trace on the portion of code, which lasts longer than 10 seconds.

     

    Offtopic: The Pool Config could get updated to latest package templates - inside of the current one there still PHP5 metioned. The nginx socket paths could get updated too..

    Hi,

     

    Here is the new log file included and diagnostics if needed.

     

    Thanks for looking at this issue.

    php.slow.zip

    Edited by CiscoCoreX
    Link to comment

    Followed the same steps (using Unraid version 6.12.6 on Chrome browser)

     

    1. Start system with factory settings

    2. Change default timezone to my own timezone (Europe)

     

    Loading the Dashboard page is always instant.

    image.png

     

    A couple of things you can try, which hopefully give more insight

    Try each suggestion at the time to see its effect.

     

    1. Access the system using its IP address. e.g. http://192.168.1.100 (replace by your server address)

    2. Under network settings change to a static DNS server assigment, e.g. use 1.1.1.1 or 8.8.8.8

    3. Under display settings change "Show Dashboard apps --> None"

    4. Do a file system check (using Windows) on your USB device to check for any errors to repair

     

    Ps. The file "php.slow.log" shows the dashboard page loading takes a long time (duh) without further details.

     

    Link to comment
    17 hours ago, bonienl said:

    Followed the same steps (using Unraid version 6.12.6 on Chrome browser)

     

    1. Start system with factory settings

    2. Change default timezone to my own timezone (Europe)

     

    Loading the Dashboard page is always instant.

    image.png

     

    A couple of things you can try, which hopefully give more insight

    Try each suggestion at the time to see its effect.

     

    1. Access the system using its IP address. e.g. http://192.168.1.100 (replace by your server address)

    2. Under network settings change to a static DNS server assigment, e.g. use 1.1.1.1 or 8.8.8.8

    3. Under display settings change "Show Dashboard apps --> None"

    4. Do a file system check (using Windows) on your USB device to check for any errors to repair

     

    Ps. The file "php.slow.log" shows the dashboard page loading takes a long time (duh) without further details.

     

    Hi,

    1. 

    1. Access the system using its IP address. e.g. http://192.168.1.100 (replace by your server address)

    I always use ip to login into my unraid: http://10.10.60.105/

     

    2. Under network settings change to a static DNS server assigment, e.g. use 1.1.1.1 or 8.8.8.8
    image.png.f0b83e6b47595eb6ef09d3e0a1b181d9.png

     

    3. Under display settings change "Show Dashboard apps --> None"

    Nothing change, still the same.

     

    4. Do a file system check (using Windows) on your USB device to check for any errors to repair
    Did a check on my USB driver, no error found. This is also 2nd time I did an clean install, formatted the USB drive also.

     

    Edited by CiscoCoreX
    Link to comment
    17 hours ago, bonienl said:

    Ps. The file "php.slow.log" shows the dashboard page loading takes a long time (duh) without further details.

    And why dont we dig deeper there? There are further details.

     

    I checked the eval'd code. The affected page is DashStats and line 53 is the docker status exec.

    I asked him to execute the rc.docker status command and this command takes ~20 secs to complete, so here we have our issue at least for him.

     

    The question is: Is this the same cause for all others? And if yes, what is taking so long time inside the rc.d script for some users.

     

    For others having the issue, I would ask them to execute the command "/etc/rc.d/rc.docker status" in a terminal and observe, how many seconds it need to generate output.

     

    That are my findings. Correct me if anything looks wrong. :)

    • Upvote 1
    Link to comment
    2 hours ago, KluthR said:

    The question is: Is this the same cause for all others? And if yes, what is taking so long time inside the rc.d script for some users.

     

     

    Not the cause for me.  After upgrading to 6.12.6 and noticing this slow GUI response on dashboard, I disabled VMs and Docker services, rebooted.  Problem was still there.  I even rebooted without starting the array, same problem.  🤷‍♂️

    Link to comment

    But is the mentioned command taking so long anyway? Unraid calls this command regardless of docker/vms enabled/disabled. If there is any "issue" in the script, it could be triggered anyway. Please try it and report back.

     

    EDIT: If the docker status command is not delaying, please share the PHP-Slowlog for your system.

    Edited by KluthR
    Link to comment

    I just checked - the rc.docker command has this sed in it as well. Those write back to USB Boot drive. This is what me brings me back to bonie's suggestion to check the Boot-Drive. The sed would be extremely slow, when writes to the USB drive would be slow (a failing device maybe?). But ANY write would be slow then.

     

    Maybe a performance check with CrystalDiskMark would expose issues writing to the USB key.

     

    Iam very curious if this could be the root cause for all affected users.

    Link to comment

    I let @CiscoCoreX do several „echo 1 > /boot/test.xml“ which delayed up to 6 seconds. (Btw, could you test „echo 1 > /mnt/user/someshare/test.txt“ with started array and real share name?)

     

    downgrading fixes all delays.

     

    The issue seems to be Linux related. At least nothing to do with webgui.

     

    anyway, Iam out now. The slowlog brought a new finding which was my only idea 😂

     

    Maybe LimeTech can share some thoughts on this.

    • Like 1
    Link to comment
    18 hours ago, KluthR said:

    I let @CiscoCoreX do several „echo 1 > /boot/test.xml“ which delayed up to 6 seconds. (Btw, could you test „echo 1 > /mnt/user/someshare/test.txt“ with started array and real share name?)

     


    I did run your command: echo 1 > /mnt/user/appdata/test.txt

    It responded imminently, no delay :)

     

    The command: echo 1 > /boot/test.xml
    Gave me a delay around 5 - 6 seconds.

     

    But the best part, I did run this command ( echo 1 > /boot/test.xml ) on my primary unraid server, still on version 6.12.3.
    And have the same delay as on my backup server with version 6.12.6.
    Interesting since my version 6.12.3 are working perfectly fine on booth computers. 

    I uploaded to short recording of the delay on booth servers.

    Pegasus 6.12.3.zip Backup_Server_6.12.6.zip

    Edited by CiscoCoreX
    Link to comment

    I made an update for two files which check for changes in the docker configuration and update as needed.

    The check now also looks for the presence of _SUBNET_ to make valid changes.

     

    rc.docker --> copy this file to folder /usr/local/etc/rc.d and make the file executable (chmod +x rc.docker)

    DockerClient.php --> copy this file to folder /usr/local/emhttp/plugins/dynamix.docker.manager/include

     

    Please test if this solves the delays.

    Thx.

     

    dashboard-test.zip

    Link to comment

    @bonienl
    I just copied your files, and now the dashboard is fast :)

    But the APPS page are just white.

    image.png.f4c46f3c9386417c0220129c153271dc.png

     

    And DOCKER page is missing something. Same if you go to Settings ---> DOCKER, nothing happening, just white page.
    image.png.29b258a5c88e761431e3c725a09c6b59.png

     

    And the DOCKER page:
     

    image.png.add375030b3d2da26aaff78bd72a3c73.png



    But the Dashboard is fast 

    image.thumb.png.c6fbd5f9ed001b07430841d137015a7f.png

    Edited by CiscoCoreX
    • Like 1
    Link to comment
    7 hours ago, bonienl said:

    I made an update for two files which check for changes in the docker configuration and update as needed.

    Did not took a look but what is the fix actually? Calling exec with sed only of really needed?

     

    If yes: This fixes the always-calling-sed-issue but what is the underlying write-to-boot-is-slow issue then?

    Link to comment

    @CiscoCoreX

    Can you go to Tools -> PHP Settings

     

    Error reporting level = All Categories

     

    Then open the View Log

     

    Revisit the pages which end up blank and observe the PHP log for any errors.

    Please post these errors.

    Thx

    Fixed my typos, please use the updated files.

     

    @KluthR

    The fix is not really the answer to the root cause, which I don't know but it prevents unnecessary writing to the flash device.

     

     

    • Upvote 2
    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.