• [6.9.2] Parity checking scheduling not working


    altyne
    • Closed

    I set to yearly.  I am expecting this should executed in year but it executes now.

    Before this, I used monthly or even disable still randomly it executes itself.

    Scheduled parity check: yearly (latest)
    Day of the week: ---
    Day of the month: First day
    Time of the day: 2:30
    Month of the year: December
    Write corrections to parity disk: Yes


    See the history:
    2021-12-20, 15:33:45    16 hr, 41 min, 43 sec    133.1 MB/s    OK    0
    2021-10-23, 15:30:27    16 hr, 33 min, 20 sec    134.3 MB/s    OK    0
    2021-10-10, 16:21:52    16 hr, 21 min, 51 sec    135.8 MB/s    OK    0
    2021-09-10, 16:18:48    16 hr, 18 min, 47 sec    136.3 MB/s    OK    0
    2021-08-08, 13:42:12    16 hr, 17 min, 50 sec    136.4 MB/s    OK    0

     

    Diagnostics attached.

    nightowl-diagnostics-20220101-1422.zip




    User Feedback

    Recommended Comments

    You should provide a copy of your diagnostics so we can get a better idea of what happened.   It would also be a good idea to provide a copy of /etc/cron.d/root so we can see how the schedule has been set.

     

    BTW:  It is normally recommended that scheduled checks are set to be non-correcting.   

    Link to comment

    @itimpi

    I have attached the diagnostics - nightowl-diagnostics-20220101-1422.zip

     

    this is the content of cron:

    # Generated parity check schedule:
    30 2 1 12 * /usr/local/sbin/mdcmd check  &> /dev/null || :

    Link to comment
    Jan  1 08:22:21 NightOwl emhttpd: unclean shutdown detected

     

    That cron setting is correct that's listed

     

    Dec 1st @ 2:30 am

     

    Since it's correct, and it's running at random times, it would appear that your system is randomly rebooting. (Confirmed by your diagnostics)  Maybe the system event log in the BIOS would shed some light on what's going on.

    Link to comment
    26 minutes ago, Squid said:
    Jan  1 08:22:21 NightOwl emhttpd: unclean shutdown detected

     

    That cron setting is correct that's listed

     

    Dec 1st @ 2:30 am

     

    Since it's correct, and it's running at random times, it would appear that your system is randomly rebooting. (Confirmed by your diagnostics)  Maybe the system event log in the BIOS would shed some light on what's going on.

     I didn't shutdown my machine. Its running 24x7. That's the reason  the parity check was triggered?

    Link to comment
    42 minutes ago, Squid said:

    Yes

    @Squid

    I know the reason. Just now we have  experience a brownout; it happens only a few seconds. Just now parity checking is running. During that time around 08:22:21AM , I didn't know we have a power outage and I was sleeping. Thanks to all. I need to protect my server with UPS since occasionally brownout occurs in my place.

    Edited by altyne
    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.