Jump to content
  • [6.10.2] Server hangs (with high load)


    capino
    • Urgent

    After upgrading from 6.9.2 to 6.10.2 my server hangs during my backup using duplicati docker to OneDrive.
    During reading of the files (about 120GB an 1 million files) I noticed that there are processes in uninterruptible sleep. (ps aux with stat D).
    After a while the amount of processes in uninterruptible sleep are getting to a amount that the server becomes unresponsive.
    I noticed some of the Workers are in an uninterruptible sleep state.
    At that point, the only thing to do, is to stop the duplicati docker and everything comes back.
    If the duplicati docker is not stopped shortly after the load becomes to high, the server becomes unresponsive all to gather and only a hard reboot is possible to get unRaid working again.

     

    This same happend when upgrading to 6.10.0 so I downgraded back to 6.9.2
    Since this also happend in 6.10.2, my server is back to 6.9.2

    I imagine the problem has something to do with I/O.

    Is there a solution for this. Maybe restrict the I/O for the duplicati docker, or something overal?




    User Feedback

    Recommended Comments

    Just updated to 6.10.3 and in this version my problem seems to be resolved.
    I tested by running simultaneous:
    - duplicati backup to onedrive
    - running Parity-Check
    - streaming a video

    - and some other high I/O processes.
     

    Link to comment

    I thought everything was working as expected, but just a few minutes ago all load went up again and a there were a lot of  processes in uninterruptible sleep. After stopping Docker (/etc/rc.d/rc.docker stop) all load went down again.
    I had just a moment to watch docker stats, but there were no dockers running in high CPU.
    I was able to create a diagnostic which can be find underneath.

    I downgraded back to 6.9.2

     

    optimus-diagnostics-20220616-0035.zip

    Edited by capino
    Link to comment

    Server load average is very high, shfs seems to play a big part of that, unfortunately and AFAIK not quite clear what causes this for some users.

     

    Depending on where you have the data for the worst offending dockers any chance you can change the mappings to use disk shares instead of user shares? E.g., lets say the data Duplicati is syncing is on a pool or a single disk, change the mappings form "/mnt/user/share" to "/mnt/pool_name/share" or "/mnt/disk#/share" and test.

    Link to comment

    I already use "/mnt/pool_name/share" for most configurations in Dockers.
    Except for systems where the data is fragmented over the Disk array.

    Last night I had stopped the Duplicati docker.
    So this could not be the docker that creates this problem.

    I looked like the problem last night started at the moment the "Auto Update Applications" app did a check on available updatable dockers. The auto update had not started yet.

    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.

×
×
  • Create New...