Cron-plus error "System Time Change Detected" and not executing

General
1

Hello,
I am running NodeRed 4.0.2 on a Pi Model 2B. I have some very simple flow with cronplus nodes that sends mqtt commands. I am getting quite often (not all the time for some weird reason) this error:

System Time Change Detected - refreshing schedules! If the system time was not changed then this typically occurs due to blocking code elsewhere in your application

Sometime this even causes the Timers to not get executed.
I have a DS3231 RTC installed on the Pi, since its offline most of the time.
Might this cause any issues, if not what might be the problem?

2

I put that in there to let users know that inaccurate cron times can occur if your flows or nodes cause blocking such that nodejs didnt even see the clock change. It turns out to be a handy notification to let you know something aint right

Typically, this happens when you have hard processing loops (usually in a function or a contrib node) or heavy processing (like large payloads being manipulated by a node). Do you have any of this going one around the time you see the message?

Keep an eye on your CPU usage - do you see spikes?

3

@Steve-Mcl - would a time shift due to summer/winter time trigger it also ?

4

Yeah. That is initially why it was added - to refresh schedules to ensure they happen at the correct time. Code for ref: node-red-contrib-cron-plus/cronplus.js at master · Steve-Mcl/node-red-contrib-cron-plus · GitHub

5

Thanks, just checked, indeed node red was 100% load on one core.
So I started disabling some nodes and found out that the contrib valetudo-map-png node seems to be the problem.

I will check in the long term if it happens again.