cron fails on two servers, approximately same time, without error
See original GitHub issueI have two aws servers, identical setup:
lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic
uname -r 4.15.0-1035-aws
node --version v8.16.0
cat package.json | grep cron "cron": "^1.7.1",
both have cron running with this code:
new CronJob('*/10 * * * * *', procNewBlock, null, true, 'Europe/Berlin');
both stopped running at approximately the same time, the first was running the last time at: May 2 09:05:47 UTC
the second last run was at: May 2 09:06:30 UTC
so far this was the only time that this happend (running for about 1 month now). To me it looks as if some scheduled system task outside of nodejs is killing the crons. But any help greatly appreciated. The nodejs processes did not see any interruption.
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (2 by maintainers)
Top GitHub Comments
No, not yet. I am still waiting that it happens again so I get more debug info. So far it happened once more, which showed me that: a) it is actually not related to the cron package but some deeper source in nodejs b) it was probably a coincidence that it happend on both servers at the same time
This morning I got this same error and tried out with a fresh new install of rasbian and node-red. I was able to pinpoint it to an inject node with specific content. With this (below) node it crashed, with other configurated inject nodes there are no problems.
[{“id”:“a02e32cd.28c53”,“type”:“tab”,“label”:“Flow 6”,“disabled”:false,“info”:“”},{“id”:“a78a0f31.f1bc9”,“type”:“inject”,“z”:“a02e32cd.28c53”,“name”:“Init & reset”,“topic”:“”,“payload”:“auto”,“payloadType”:“str”,“repeat”:“”,“crontab”:“*/20 2 * * *”,“once”:true,“onceDelay”:0.1,“x”:130,“y”:120,“wires”:[[]]}]