Scheduled parity check suddenly no longer starting (Possibly Daylight Saving Time Related)

[ssh]

I have my parity check scheduled to run on the last day of each month at 0:00. This always ran fine (for multiple years), except for today when it suddenly did not. It didn't start at 0:00. I've waited till 01:05, but it never started.

 

Looking at the root file in /etc/cron.d it shows that "the last day of the month" is calculated as follows: [[ $(date +%e -d +1day) -eq 1 ]].

 

I suspect this to be an issue with the fact that today is the day when daylight saving time ends, as 31st 0:00 + 1 day will probably result in 31st 23:00, getting just the day value of that is 31 which is not equal to 1, so the cron job results in false and won't run.

 

Edited October 30, 2021 by ssh
Spelling

[Kydonakis]

Same issue here under almost same settings (start at 00:30 end of month). Parity check didn't start.

Edited November 1, 2021 by Kydonakis

[JorgeB]

On the other hand I had a user script schedulled to run at 1AM running twice, second time causing an error, just rescheduled it and made sure I have nothing else scheduled between midnight and 1AM.