array health report, change scheduled time

[sota]

I know I must be missing the obvious, but how do I change the time when the array health report test is run?  mine currently is every monday morning at 12:20am, and it's annoying as hell as I get a text message at that time.  I have my phone programmed to sound on texts from specific senders, regardless of the do-not-disturb setting, in case of trouble.

[ChatNoir]

You can find this in the Settings, the Scheduler is in the User Preferences section.  

[sota]

 

(note I did just change the weekly from 8:20 to 8:00.  I'll be curious to see if the text comes in earlier than normal.) If you mean this, it apparently doesn't respect my settings for weekly, or it doesn't respect my time zone.  I'm UTC -05:00 right now.  I'm getting a text at 12:20am right now, and expecting it to be 12:00 next monday morning.

[ChatNoir]

Oh, re-reading your initial post, I realise that my answer was not so accurate.   

Regarding your timing issues, did you adjusted the Time settings (also in settings) ?

 

I do have it set correctly for UTC+1 and the events seem to start a the appropriate time.

[sota]

If you mean 'Date and Time', yes they're correct for my UTC location as well as the actual time.

[sota]

So the answer is, nothing I've changed did squat.

12:20am monday morning I got a text.

If anyone has any ideas how to change what time the array health report is run, I'd appreciate it.

[sota]

*bump*

still getting the same message at the same time, and I can't find a way to change it.

next step is to try and change the time zone on sunday, to see if it happens later, or earlier.

 

I can't believe no one knows where this setting is.

[trurl]

1 hour ago, sota said:

where this setting is

 

[sota]

I don't see how that helps.

 

Here's the email:

 

Quote

Sep 14, 2020, 12:20 AM

Unraid Status: Notice [CUBE] - array health report [PASS]

 

Event: Unraid Status
Subject: Notice [CUBE] - array health report [PASS]
Description: Array has 8 disks (including parity & cache)
Importance: normal

Parity - WDC_WD100EMAZ-00WJTA0_JEH1JDMM (sde) - standby [OK]
Disk 1 - WDC_WD100EMAZ-00WJTA0_JEH74KHM (sdb) - standby [OK]
Disk 2 - WDC_WD100EMAZ-00WJTA0_JEH1D31M (sdc) - standby [OK]
Disk 3 - WDC_WD100EMAZ-00WJTA0_JEH8DX9N (sdd) - standby [OK]
Disk 4 - WDC_WD100EMAZ-00WJTA0_2TKTGAHD (sdf) - standby [OK]
Disk 5 - WDC_WD100EMAZ-00WJTA0_2TKLZJED (sdg) - standby [OK]
Cache - SAMSUNG_MZ7PD256_S1MFNYAF500120_35001438028fe498d (sdk) - standby [OK]
Cache 2 - SAMSUNG_MZ7PD256_S1MFNYAF500123_35001438028fe498e (sdl) - standby [OK]

Parity is valid
Last checked on Wed 02 Sep 2020 04:08:03 PM EDT (12 days ago), finding 0 errors.
Duration: 18 hours, 8 minutes, 2 seconds. Average speed: 153.2 MB/s

That event time survives a reboot, so it's not some kind of counter/timer.

[sota]

Looking around with I guess some new search terms, i'm seeing multiple people reporting the same date/time stamp as me... monday at 12:20am.

 

@limetechIs this some hard-coded item?

[trurl]

49 minutes ago, sota said:

I don't see how that helps.

It tells you where it is stored.

 

This is the specific line:

status="20 0 * * *"

http://corntab.com/?c=20_0_*_*_*

[sota]

Ok.

if I've done this right, it should now do it Monday at 10am.

Let's hope.

[trurl]

16 hours ago, sota said:

Ok.

if I've done this right, it should now do it Monday at 10am.

Let's hope.

I think you have to reboot or do this at the command line for the edit to take effect

update_cron

 

[sota]

just ran that too.

thanks.

[sota]

as of this post, I'll know in about 2 hours if it's fixed.

[sota]

didn't work.  still came in at 12:20am

Might try a reboot for next week's time slot.

file: /boot/config/plugins/dynamix/dynamix.cfg

line: status="0 10 * * 1"

should mean monday @ 10am, right?

 

 

 

[sota]

Weekly still doing it at the wrong time; actual occurence is at 00:20 Monday morning.