(Look at bottom)
Sorry, I thought tonight was the ping
node but it isn't.
Now it is an exec
node.
This evening - just a short while ago I got this:
This is the best I can capture.
21:34:50
{"message":"Error: spawn ENOMEM","source":{"id":"3ca1bd56.5515aa","type":"ping","name":"Ping","count":1},"stack":"Error: spawn ENOMEM\n at ChildProcess.spawn (internal/child_process.js:408:11)\n at spawn (child_process.js:553:9)\n at doPing (/home/pi/.node-red/node_modules/node-red-node-ping/88-ping.js:40:14)\n at PingNode._inputCallback (/home/pi/.node-red/node_modules/node-red-node-ping/88-ping.js:120:36)\n at /usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:203:26\n at Object.trigger (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/hooks.js:113:9)\n at PingNode.Node._emitInput (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:195:11)\n at PingNode.Node.emit (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:179:25)\n at PingNode.Node.receive (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:476:10)\n at Immediate._...
syslog for about that time:
Feb 6 21:32:39 TimePi Node-RED[4875]: 6 Feb 21:32:39 - [info] [ping:Ping] ping - Host '192.168.0.83' process timeout - sending SIGINT
Feb 6 21:32:39 TimePi Node-RED[4875]: 6 Feb 21:32:39 - [info] [ping:Ping] ping - Host '192.168.0.86' process timeout - sending SIGINT
Feb 6 21:32:39 TimePi Node-RED[4875]: 6 Feb 21:32:39 - [info] [ping:Ping] ping - Host '192.168.0.89' process timeout - sending SIGINT
Feb 6 21:32:39 TimePi Node-RED[4875]: 6 Feb 21:32:39 - [info] [ping:Ping] ping - Host '192.168.0.91' process timeout - sending SIGINT
Feb 6 21:32:39 TimePi Node-RED[4875]: 6 Feb 21:32:39 - [info] [ping:Ping] ping - Host '192.168.0.92' process timeout - sending SIGINT
Feb 6 21:34:46 TimePi Node-RED[4875]: 6 Feb 21:34:46 - [info] [ping:Ping] ping - Host '192.168.0.1' process timeout - sending SIGINT
Feb 6 21:35:37 TimePi Node-RED[4875]: 6 Feb 21:35:37 - [warn] [function:Er indicator] 0
Feb 6 21:39:17 TimePi kernel: [648611.732577] rtc rtc0: __rtc_set_alarm: err=-22
Feb 6 21:44:49 TimePi Node-RED[4875]: 6 Feb 21:44:48 - [info] [ping:Ping] ping - Host '192.168.0.1' process timeout - sending SIGINT
Feb 6 21:44:49 TimePi Node-RED[4875]: 6 Feb 21:44:48 - [info] [ping:Ping] ping - Host '192.168.0.21' process timeout - sending SIGINT
Feb 6 21:44:49 TimePi Node-RED[4875]: 6 Feb 21:44:48 - [info] [ping:Ping] ping - Host '192.168.0.34' process timeout - sending SIGINT
Feb 6 21:44:49 TimePi Node-RED[4875]: 6 Feb 21:44:48 - [info] [ping:Ping] ping - Host '192.168.0.82' process timeout - sending SIGINT
Feb 6 21:44:49 TimePi Node-RED[4875]: 6 Feb 21:44:48 - [info] [ping:Ping] ping - Host '192.168.0.83' process timeout - sending SIGINT
Feb 6 21:44:49 TimePi Node-RED[4875]: 6 Feb 21:44:48 - [info] [ping:Ping] ping - Host '192.168.0.86' process timeout - sending SIGINT
Feb 6 21:44:49 TimePi Node-RED[4875]: 6 Feb 21:44:48 - [info] [ping:Ping] ping - Host '192.168.0.89' process timeout - sending SIGINT
Feb 6 21:44:49 TimePi Node-RED[4875]: 6 Feb 21:44:48 - [info] [ping:Ping] ping - Host '192.168.0.91' process timeout - sending SIGINT
Feb 6 21:44:49 TimePi Node-RED[4875]: 6 Feb 21:44:48 - [info] [ping:Ping] ping - Host '192.168.0.92' process timeout - sending SIGINT
Feb 6 21:46:47 TimePi Node-RED[4875]: 6 Feb 21:46:47 - [info] [ping:Ping] ping - Host '192.168.0.1' process timeout - sending SIGINT
Feb 6 21:46:47 TimePi Node-RED[4875]: 6 Feb 21:46:47 - [info] [ping:Ping] ping - Host '192.168.0.21' process timeout - sending SIGINT
Feb 6 21:46:47 TimePi Node-RED[4875]: 6 Feb 21:46:47 - [info] [ping:Ping] ping - Host '192.168.0.34' process timeout - sending SIGINT
Feb 6 21:46:47 TimePi Node-RED[4875]: 6 Feb 21:46:47 - [info] [ping:Ping] ping - Host '192.168.0.82' process timeout - sending SIGINT
Feb 6 21:46:47 TimePi Node-RED[4875]: 6 Feb 21:46:47 - [info] [ping:Ping] ping - Host '192.168.0.83' process timeout - sending SIGINT
Feb 6 21:46:47 TimePi Node-RED[4875]: 6 Feb 21:46:47 - [info] [ping:Ping] ping - Host '192.168.0.86' process timeout - sending SIGINT
Feb 6 21:46:47 TimePi Node-RED[4875]: 6 Feb 21:46:47 - [info] [ping:Ping] ping - Host '192.168.0.89' process timeout - sending SIGINT
Feb 6 21:46:47 TimePi Node-RED[4875]: 6 Feb 21:46:47 - [info] [ping:Ping] ping - Host '192.168.0.91' process timeout - sending SIGINT
Feb 6 21:46:47 TimePi Node-RED[4875]: 6 Feb 21:46:47 - [info] [ping:Ping] ping - Host '192.168.0.92' process timeout - sending SIGINT
Feb 6 21:46:47 TimePi Node-RED[4875]: 6 Feb 21:46:47 - [info] [ping:Ping] ping - Host '192.168.0.93' process timeout - sending SIGINT
Feb 6 21:48:31 TimePi systemd[1]: Started Session c8 of user pi.
Feb 6 21:48:35 TimePi systemd[1]: fake-hwclock.service: Cannot add dependency job, ignoring: Unit fake-hwclock.service is masked.
Feb 6 21:48:35 TimePi systemd[1]: Stopping LSB: Start NTP daemon...
The pings are done every 20 seconds.
But this line kind of has my attention:
Feb 6 21:35:37 TimePi Node-RED[4875]: 6 Feb 21:35:37 - [warn] [function:Er indicator] 0
Alas soon there after another one happened.
This is the captured error message - I hope.
{"message":"Error: spawn ENOMEM","source":{"id":"596dfbde.39bc6c","type":"exec","name":"HWC time","count":1},"stack":"Error: spawn ENOMEM\n at ChildProcess.spawn (internal/child_process.js:408:11)\n at spawn (child_process.js:553:9)\n at Object.execFile (child_process.js:237:17)\n at exec (child_process.js:158:25)\n at ExecNode._inputCallback (/usr/lib/node_modules/node-red/node_modules/@node-red/nodes/core/function/90-exec.js:134:29)\n at /usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:203:26\n at Object.trigger (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/hooks.js:113:9)\n at ExecNode.Node._emitInput (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:195:11)\n at ExecNode.Node.emit (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:179:25)\n at ExecNode.Node.receive (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:476:10)\n at Immediate._onImmediate (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/Flow.js:657:5..."}
This one happened at 22:11 local.
From the syslog:
Feb 6 21:59:29 TimePi kernel: [649823.768575] rtc rtc0: __rtc_set_alarm: err=-22
Feb 6 22:00:54 TimePi ntpd[24732]: 129.250.35.251 local addr 192.168.0.99 -> <null>
Feb 6 22:03:01 TimePi ntpd[24732]: 103.214.220.220 local addr 192.168.0.99 -> <null>
Feb 6 22:04:12 TimePi ntpd[24732]: 27.124.125.250 local addr 192.168.0.99 -> <null>
Feb 6 22:11:14 TimePi Node-RED[4875]: 6 Feb 22:11:14 - [warn] [function:Er indicator] 0
Feb 6 22:17:01 TimePi CRON[30712]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Feb 6 22:29:01 TimePi Node-RED[4875]: 6 Feb 22:29:01 - [info] [ping:Ping] ping - Host '192.168.0.1' process timeout - sending SIGINT
Feb 6 22:29:01 TimePi Node-RED[4875]: 6 Feb 22:29:01 - [info] [ping:Ping] ping - Host '192.168.0.21' process timeout - sending SIGINT
Feb 6 22:29:01 TimePi Node-RED[4875]: 6 Feb 22:29:01 - [info] [ping:Ping] ping - Host '192.168.0.34' process timeout - sending SIGINT
Feb 6 22:29:01 TimePi Node-RED[4875]: 6 Feb 22:29:01 - [info] [ping:Ping] ping - Host '192.168.0.82' process timeout - sending SIGINT
Feb 6 22:29:01 TimePi Node-RED[4875]: 6 Feb 22:29:01 - [info] [ping:Ping] ping - Host '192.168.0.83' process timeout - sending SIGINT
and again at close to that time there is this line:
Feb 6 22:11:14 TimePi Node-RED[4875]: 6 Feb 22:11:14 - [warn] [function:Er indicator] 0
This is the node:
[{"id":"596dfbde.39bc6c","type":"exec","z":"e2bd5a4e.5597e8","command":"sudo hwclock -r","addpay":false,"append":"","useSpawn":"false","timer":"","oldrc":false,"name":"HWC time","x":660,"y":2450,"wires":[["f90ccbc3.25a8b","8601b654.799c6"],[],[]]}]
UPDATE:
This is beyond annoying now.
Ok, the first post of the error message: (extract)
"message":"Error: spawn ENOMEM","source":{"id":"3ca1bd56.5515aa","type
That is a PING
node.
But somewhere in it I also see reference (or think I do) to an exec
node.
So I took the post off my thread about the ping
node and started this new one.
That is because soon after I got the second one and it clearly is the HW clock
node.
{"message":"Error: spawn ENOMEM","source":{"id":"596dfbde.39bc6c","t
That is the node I posted.
I can understand it is annoying / frustrating to you who is reading this pathetic post of mine asking for help, but can you understand (please) my situation?
For a few days it has been behaving itself.
Then it spits the dummy on me.
I was away for a couple of weeks and errors happened.
(See other post here)
I don't understand the message. Yeah, ok. Maybe I should sit down and look at them.
But what I am pasting seems to be truncated, so it is kind of frustrating thinking "this is the entire story" when it isn't.
If you wouldn't mind having a look at the (error) message and tell me if there is something there which is telling me what is going on.
These errors seem to come in waves....
Theory as of now: possible lack of memory because something is eating up the available memory.
But I can't be sure.