• [SOLVED] UPDATE fixed on [6.12.2] - Now Log is filling up my cache and CPU is high

    casperse

    By casperse

      • Solved Urgent

    UPDATE: I did status urgent since I could see many people reporting high CPU usage, please change status if needed) 
    After upgrading to 6.12.0 I experienced very high CPU usage to a extend that the whole system unresponsive.
    Dockers stopped working and i Got the cache drive warning some log is filling it up.

    image.png.678749cfeaf8a29fb546c8daef60e09a.png
    Also I had to stop doing a parity check (To few resources, it almost crashed it).

     

    The log shows this today?:

    image.thumb.png.7375dd6373d11d1366e7e8df723f3e01.png

     

    Diagnostics attached.

    I also tried to do some PINNING of the cores to get some functions back, that did help opening the Unraid GUI but not on anything else.

    I am almost ready to do a rollback, any would be really appreciated would like to stay on this version.


     

    diagnostics-20230619-2110.zip

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    casperse

    I just got the new update 6.12.1 installed and its back to normal.
    Even the parity check can now run with all services running all at around +60% CPU like before!

    My only issue is that the "logs" have not been freed up after the update to 6.12.1 - before after problems and a reboot the utilization of my cache drive was back to normal afterwards (I suspect some logging would get flushed) but now after the update I didn't get the space back from my cache drive its still gives warning about high utilization.

    Is there any command I can run to "clean" up my cache drive?

    Link to comment
    casperse

    After running the 6.12.1 for 4 days I now have CPU problems again?

    And the error I saw in the attached log is back again?

    What does this mean?

    image.thumb.png.bb552b4bbb3d01658bbd9b8f17892177.png

     

    Link to comment
    sittingmongoose
    9 hours ago, casperse said:

    After running the 6.12.1 for 4 days I now have CPU problems again?

    And the error I saw in the attached log is back again?

    What does this mean?

    image.thumb.png.bb552b4bbb3d01658bbd9b8f17892177.png

     

    Can you post diagnostics now?

    Link to comment
    casperse
    On 6/26/2023 at 5:45 AM, sittingmongoose said:

    Can you post diagnostics now?

    Sure Thing! (I just believe its the same as the first one I posted?)

    diagnostics-20230626-2016.zip
     

    Got out of memory (64G ECC)

    image.thumb.png.82195f72b9183b47db31420773609f7a.png

    I did another reboot and stopped different Dockers to see if that would help.
    But my Cache didnt return to normal size, anyway to find out what docker app filled up my cache drive?
    (I would really like to get that space back again)
    image.thumb.png.21c7ec36257f1b08c4b6b2018d9b359f.png

    UPDATE: I had a full backup of my "appdata share" and after comparing all subfolders in size with the existing one.
    I found 414G of *.err data files under the maria db for nextcloud folder in the appdata , I used krusader to delete them all and re-start nextcloud.
    This solved the cache drive full issue for me. I have also stopped my paperless docker and some other ones and so far the memory is okay, and haven't seen any "memory full yet"? But its like stumbling in the dark.

    Edited by casperse
    Link to comment
    casperse

    Can someone please help me find the reason for why I keep getting the Out of memory?
    Do I need to do a reboot every time I get this or can I ignore it?

     

    image.thumb.png.c3cd96d302751dad392352faf70cebbd.png

    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.