Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

one schedule but multiple events #22

Closed
hklages opened this issue Aug 14, 2020 · 3 comments
Closed

one schedule but multiple events #22

hklages opened this issue Aug 14, 2020 · 3 comments
Labels
need more info Need more information to resolve this issue

Comments

@hklages
Copy link

hklages commented Aug 14, 2020

I want to renew a bearer every month. For that I use cron plus with a simple schedule: "0 0 0 15 * *". My expectation is that this will only create one trigger per month. But today I got triggers on 03:49, ..., 16:33, 16:45

What is wrong?

Could you also help me to understand the provided information in the screen shot - there are multiple triggers on 14th and schedule is for - (minus) xxxx.

cronplus

@Steve-Mcl
Copy link
Owner

Hi @hklages , that does look most strange. For me I see...

image

Can you tell me...

  • what hardware and OS was this running on? (PI? VM? Raspian? Windows? etc)
  • what version of cron-plus is being used?
  • how many cron-plus nodes are in operation on your flow?

One theory I have is your clock adjusted after node-red was running & caused it to get confused. In V1.1.0 (not yet published) I have added code to handle system clock changes - this might already be fixed.

Please keep an eye out for V1.1 or above appearing in the node-red pallete manager soon (in the next few of days) & please update. Let me know if you get this again.

Thank you for feeding back to me this issue.

Cheers, Steve.

@Steve-Mcl Steve-Mcl added the need more info Need more information to resolve this issue label Aug 22, 2020
@hklages
Copy link
Author

hklages commented Aug 24, 2020

Hardware is CCU3 based on raspberry pi 3b with specialized operating system (debian type).

There were about 10 cron-plus nodes - some with multiple schedules.

I did use the recent (at that time when reporting the issue) cron-plus version but had to install it as NodeRED crashes permanently shortly after restart. There were hundreds of messages in the log file - just information. I did delete the log file to clean up everything. After removing all nodes and cron-plus the system started and since then worked fine.

As I can not provide any further information we can close this issue.

@hklages hklages closed this as completed Aug 24, 2020
@Steve-Mcl
Copy link
Owner

@hklages thanks for the feedback - your issues may have impacted cron plus before i updated it to handle system time changes. Hopefully since the updates (to cron-plus and your system) it will behave.

Let me know if it happens again - I would hate to think this is an issue in the cron-plus node & would appreciate feedback if it happens again.

Cheers, Steve.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need more info Need more information to resolve this issue
Projects
None yet
Development

No branches or pull requests

2 participants