• [6.12.3] Segfault in emhttpd after drive(s) dropping offline results in erroneous health report

    Michael_P

    By Michael_P

      • Urgent

    After 2 drives dropped offline, a segfault occured in emhttpd which resulted in inaccurate health and status displays on the dashboard, and aslo the nightly health report email to erroneously report that the array was healthy. No indication from the server that anything was wrong, save for the entries in the syslog which I happened to read by chance.

     

    When this happened back on 6.11.1 during a parity re-build, the correct FAIL email was sent so I'm not sure if this is specific to 6.12.3

     

     

    462077327_Screenshot2023-08-02052251.thumb.jpg.46e79b63ac2d29fcadec318af730c514.jpg

    867237761_Screenshot2023-08-02052234.thumb.jpg.e96e1c88b2946748ccdf8cf215d2e9c3.jpg

     

    image.png.37441409d8343a22275915f0e2e6488f.png

    urserver-diagnostics-20230802-0520.zip

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    There are no comments to display.



    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.