Node-Red Logs

Peter Scargill

unread,

Nov 16, 2015, 6:08:48 AM11/16/15

to Node-RED

I wonder if someone can advise - and bearing in mind I'm not a Linux whiz. I have left Node-Red running (in a place far, far away) - and most recently added the Blynk app to it.. I'm thinking that Blynk might be causing Node-Red crashes but need to prove that or otherwise and fix it. I have only remote access via WINSCP (and hence a terminal) and Webmin.

I don't know where the log files are - not in /var/log an not in /root on my Raspberry Pi.. can anyone suggest how to find the Node-Red log file - and is that the right place to look for Node-red reboots. It is rebooting at 11.07 or thereabouts in the morning - and rarely at other times too. I know this as I have it email me whenever it powers up - checking with Webmin says that it is NOT the Pi rebooting - that's fine - just Node-Red itself.

Any thoughts as to where to start? I installed the whole thing as ROOT.

Pete.

Nicholas O'Leary

unread,

Nov 16, 2015, 6:09:37 AM11/16/15

to Node-RED Mailing LIst

How are you running node-red? That's the biggest clue as to where the logs will be.

--
http://nodered.org
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Zenofmud

unread,

Nov 16, 2015, 6:44:47 AM11/16/15

to node...@googlegroups.com

Any cron jobs that are scheduled at that time?

> <...snip…> It is rebooting at 11.07 or thereabouts in the morning - and rarely at other times too. <…/snip…>

Peter Scargill

unread,

Nov 16, 2015, 6:58:29 AM11/16/15

to node...@googlegroups.com

Erm, not sure I follow the question.. I installed it as root…. On a Raspberry Pi 2 using the Raspbian version of Debian - - Wheezy.

--
http://nodered.org
---
You received this message because you are subscribed to a topic in the Google Groups "Node-RED" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/node-red/YgdPNpqEKzI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to node-red+u...@googlegroups.com.

Peter Scargill

unread,

Nov 16, 2015, 7:03:33 AM11/16/15

to node...@googlegroups.com

Definitely worth checking - no - nearly all are at 6am in the morning - nothing anywhere near 11am...

Pete.

-----Original Message-----
From: node...@googlegroups.com [mailto:node...@googlegroups.com] On Behalf Of Zenofmud
Sent: 16 November 2015 11:45
To: node...@googlegroups.com
Subject: Re: [node-red] Node-Red Logs

Mark Setrem

unread,

Nov 16, 2015, 7:08:28 AM11/16/15

to Node-RED

If you used pm2 to run node-red for example the log files are in a different place...

Nicholas O'Leary

unread,

Nov 16, 2015, 7:18:39 AM11/16/15

to Node-RED Mailing LIst

Peter,

ok, let me ask it a different way.

Node-RED just prints its log output to the console. It is up to script that starts node-red to redirect that output to a file. The location of that file will depend entirely on that script.

You must have followed some instruction to get node-red to startup when you reboot. There are a few different instructions floating out there. It could you've set it up as an init.d service, or maybe use the forever library, or pm2. Each will result in the log file being somewhere different.

If you followed the 'Starting node-red on boot' instructions here http://nodered.org/docs/getting-started/running.html - then you are using pm2. And as those docs also say, you can use 'pm2 logs node-red' to see the logs. Although you may equally have to use 'sudo pm2 logs node-red' depending how closely or not you followed the instructions.

Nick

Peter Scargill

unread,

Nov 16, 2015, 7:41:19 AM11/16/15

to node...@googlegroups.com

Yes, PM2 installed...

Peter Scargill

unread,

Nov 16, 2015, 7:53:38 AM11/16/15

to node...@googlegroups.com

Yes indeed, PM2 did it…

The 2 variable names I can solve today (selected and good_day) …. That’s simple… not at ALL sure what ECONNREFUSED means…

There was an exit with code 1 at 11.47 by the look of it (10.47 UK time – this is in Spain)…. Any idea what that might be??

The reference to line 158 in my scheduler node is interesting as there is no “default” option in the case…. I must be mis-understanding that message.

PM2: 2015-11-16 10:24:27: BUS system [READY] on port /root/.pm2/pub.sock

PM2: 2015-11-16 10:24:27: RPC interface [READY] on port /root/.pm2/rpc.sock

PM2: 2015-11-16 10:24:28: Starting execution sequence in -fork mode- for app name:node-red id:0

PM2: 2015-11-16 10:24:28: App name:node-red id:0 online

PM2: 2015-11-16 11:06:58: App name:node-red id:0 exited with code 1

PM2: 2015-11-16 11:06:58: Starting execution sequence in -fork mode- for app name:node-red id:0

PM2: 2015-11-16 11:06:58: App name:node-red id:0 online

PM2: 2015-11-16 11:47:36: App name:node-red id:0 exited with code 1

PM2: 2015-11-16 11:47:36: Starting execution sequence in -fork mode- for app name:node-red id:0

PM2: 2015-11-16 11:47:36: App name:node-red id:0 online

node-red-0 (out): 16 Nov 13:42:26 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:27 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:28 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:29 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:30 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:31 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:32 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:34 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:35 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:36 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (err): Error undefined

node-red-0 (err): Error ECONNREFUSED

node-red-0 (err): Error undefined

node-red-0 (err): /root/.node-red/node_modules/node-red-contrib-scheduler/scheduler.js:158

node-red-0 (err): default selected=0:

node-red-0 (err): ^^^^^^^^

node-red-0 (err): /root/.node-red/node_modules/node-red-contrib-scheduler/scheduler.js:158

node-red-0 (err): default selected=0:

node-red-0 (err): ^^^^^^^^

node-red-0 (err): /root/.node-red/node_modules/node-red-contrib-scheduler/scheduler.js:158

node-red-0 (err): default good_day=0; break;

node-red-0 (err): ^^^^^^^^

node-red-0 (out): 16 Nov 13:42:37 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:38 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:39 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:40 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:41 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:42 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:43 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:44 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:45 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:46 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:47 - [info] [rpi-gpio out:gpio5] out: 1

0 (out): 16 Nov 13:42:36 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (err): Error undefined

node-red-0 (err): Error ECONNREFUSED

node-red-0 (err): Error undefined

node-red-0 (err): /root/.node-red/node_modules/node-red-contrib-scheduler/scheduler.js:158

node-red-0 (err): default selected=0:

node-red-0 (err): ^^^^^^^^

node-red-0 (err): /root/.node-red/node_modules/node-red-contrib-scheduler/scheduler.js:158

node-red-0 (err): default selected=0:

node-red-0 (err): ^^^^^^^^

node-red-0 (err): /root/.node-red/node_modules/node-red-contrib-scheduler/scheduler.js:158

node-red-0 (err): default good_day=0; break;

node-red-0 (err): ^^^^^^^^

node-red-0 (out): 16 Nov 13:42:37 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:38 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:39 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:40 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:41 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:48 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:49 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:50 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:51 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:53 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:54 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:55 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:56 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:57 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:58 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:59 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:00 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:01 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:02 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:03 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:04 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:05 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:06 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:07 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:08 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:10 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:11 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:12 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:13 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:14 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:15 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:16 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:17 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:18 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

0 (out): 16 Nov 13:42:36 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (err): Error undefined

node-red-0 (err): Error ECONNREFUSED

node-red-0 (err): Error undefined

node-red-0 (err): /root/.node-red/node_modules/node-red-contrib-scheduler/scheduler.js:158

node-red-0 (err): default selected=0:

node-red-0 (err): ^^^^^^^^

node-red-0 (err): /root/.node-red/node_modules/node-red-contrib-scheduler/scheduler.js:158

node-red-0 (err): default selected=0:

node-red-0 (err): ^^^^^^^^

node-red-0 (err): /root/.node-red/node_modules/node-red-contrib-scheduler/scheduler.js:158

node-red-0 (err): default good_day=0; break;

node-red-0 (err): ^^^^^^^^

node-red-0 (out): 16 Nov 13:42:37 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:38 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:39 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:40 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:42:41 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:19 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

0 (out): 16 Nov 13:42:36 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (err): Error undefined

node-red-0 (err): Error ECONNREFUSED

node-red-0 (err): Error undefined

node-red-0 (err): /root/.node-red/node_modules/node-red-contrib-scheduler/scheduler.js:158

node-red-0 (err): default selected=0:

nodnode-red-0 (out): 16 Nov 13:43:20 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:21 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:22 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:23 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:24 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:25 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:27 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:28 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:29 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:30 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 13:43:31 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

Peter Scargill

unread,

Nov 16, 2015, 7:57:43 AM11/16/15

to node...@googlegroups.com

Here’s a case in point where I am utterly lost..

node-red-0 (err): Error undefined

node-red-0 (err): /root/.node-red/node_modules/node-red-contrib-scheduler/scheduler.js:158

node-red-0 (err): default selected=0:

node-red-0 (err): ^^^^^^^^

node-red-0 (err): /root/.node-red/node_modules/node-red-contrib-scheduler/scheduler.js:158

node-red-0 (err): default selected=0:

node-red-0 (err): ^^^^^^^^

node-red-0 (err): /root/.node-red/node_modules/node-red-contrib-scheduler/scheduler.js:158

node-red-0 (err): default good_day=0; break;

node-red-0 (err): ^^^^^^^^

So that’s the error message - around line 158. Here is the code from 126 to 158…

var proceed; proceed = 0;

var good_day; good_day = 0;

switch (now.getDay()) {

case 0:

if (node.sun)

proceed++;

break;

case 1:

if (node.mon)

proceed++;

break;

case 2:

if (node.tue)

proceed++;

break;

case 3:

if (node.wed)

proceed++;

break;

case 4:

if (node.thu)

proceed++;

break;

case 5:

if (node.fri)

proceed++;

break;

case 6:

if (node.sat)

proceed++;

break;

Peter Scargill

unread,

Nov 16, 2015, 1:56:19 PM11/16/15

to Node-RED

For the life of me I do not know what those 3 ERR message are referring to line 158. There is no "selected" variable and as far as I can see nothing wrong with my use of the variable "good_day". I've no idea what it is on about.

Nicholas O'Leary

unread,

Nov 16, 2015, 1:59:02 PM11/16/15

to Node-RED

It looks like the code for the node on github is out of date compared to the snippet you shared. Can you share the full .js file?

Peter Scargill

unread,

Nov 16, 2015, 2:12:17 PM11/16/15

to Node-RED

Sure of course I can... don't know why I didn't before - so here in the log is the sequence where things are regularly going wrong ( no doubt this has nothing to do with my node-red reset issue but I figure I may as well get things at least looking perfect first)....

So you can see all is well then we see a series of errors - might be nothing to do with this node - apart from the obvious ones) - but in DEBUG window I am seeing no gripes at all!! Here's the funny thing though - if I run the log file continually - I do NOT see these errors occurring.. if I stop and start the log - bang - immediately I get that group of errors.

it is possible that calling "pm2 logs node-red" is actually CAUSING that group of errors?

Ignore the GPIO OUT thats just a 1 second flashing light defined elsewhere.

PM2: 2015-11-16 11:06:58: App name:node-red id:0 exited with code 1

PM2: 2015-11-16 11:06:58: Starting execution sequence in -fork mode- for app name:node-red id:0

PM2: 2015-11-16 11:06:58: App name:node-red id:0 online

PM2: 2015-11-16 11:47:36: App name:node-red id:0 exited with code 1

PM2: 2015-11-16 11:47:36: Starting execution sequence in -fork mode- for app name:node-red id:0

PM2: 2015-11-16 11:47:36: App name:node-red id:0 online

node-red-0 (out): 16 Nov 19:58:33 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 19:58:34 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 19:58:35 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 19:58:36 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 19:58:37 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 19:58:38 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 19:58:39 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 19:58:40 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 19:58:41 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 19:58:42 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (err): Error undefined

node-red-0 (err): Error ECONNREFUSED

node-red-0 (err): Error undefined

node-red-0 (err): /root/.node-red/node_modules/node-red-contrib-scheduler/scheduler.js:158

node-red-0 (err): default selected=0:

node-red-0 (err): ^^^^^^^^

node-red-0 (err): /root/.node-red/node_modules/node-red-contrib-scheduler/scheduler.js:158

node-red-0 (err): default selected=0:

node-red-0 (err): ^^^^^^^^

node-red-0 (err): /root/.node-red/node_modules/node-red-contrib-scheduler/scheduler.js:158

node-red-0 (err): default good_day=0; break;

node-red-0 (err): ^^^^^^^^

node-red-0 (out): 16 Nov 19:58:43 - [info] [rpi-gpio out:gpio5] out: 0

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 19:58:44 - [info] [rpi-gpio out:gpio5] out: 1

node-red-0 (out): input on virtual write

node-red-0 (out): 16 Nov 19:58:45 - [info] [rpi-gpio out:gpio5] out: 0

On Monday, 16 November 2015 11:08:48 UTC, Peter Scargill wrote:

scheduler.js

Julian Knight

unread,

Nov 16, 2015, 6:11:54 PM11/16/15

to Node-RED

Just a thought - have you checked whether the Pi is running out of memory? I've had a few issues with PM2 in the past where it seems to take up a lot of memory. This might also be made worse if you've followed some of the blog posts on saving wear and tear on your SD card as they redirect some things to memory and turn off swap space.

It might be worth trying to run it manually for a while if you can take the hit on downtime. There are also other ways to keep a node.js process running.

You could also check the output from dmesg to see if there are any hardware issues being reported.

The Error ECONNREFUSED message is some kind of connection error from node.js. I've mainly seen that on serial devices. It might be that PM2 is restarting after a crash but the serial port hasn't been freed?

Peter Scargill

unread,

Nov 17, 2015, 4:54:35 AM11/17/15

to Node-RED

Hi Nick

No, so firstly I'm using the RPi2 which has twice the memory of the original Pi and secondly I'm running off a 2.5" hard drive using the excellent BERRYBOOT. The reason for that is I'm really concerned about this issue with SDs.. for example you'll have seen in those logs - every second I toggle a GPIO on and off and that's generating a log entry (I wish we could turn individual log entry items on and off as that one is utterly pointless) every second.. and of course that's just ONE thing generating logs... So I've done nothing really in ternals of optimisation and memory use. According to WEBMIN I'm typically using 1% CPU and 50% memory.

I cannot get those errors to appear EXCEPT when I start running that PM2 log command.. I left it running overnight - not one error showing! So I guess that's not the best place to look for the issue. Waiting to see if I get Node-Red resets today.

Nicholas O'Leary

unread,

Nov 17, 2015, 5:03:57 AM11/17/15

to Node-RED Mailing LIst

Peter,

if you run 'pm2 info node-red', you'll get a bit table of information like:

$ pm2 info node-red

Describing process with id 0 - name node-red

┌───────────────────┬───────────────────────────────────────────┐

│ status │ online │

│ name │ node-red │

│ id │ 0 │

│ path │ /Users/nol/code/node-red/node-red/red.js │

│ args │ │

│ exec cwd │ /Users/nol/code/node-red/node-red │

│ error log path │ /Users/nol/.pm2/logs/node-red-error-0.log │

│ out log path │ /Users/nol/.pm2/logs/node-red-out-0.log │

│ pid path │ /Users/nol/.pm2/pids/node-red-0.pid │

│ mode │ fork_mode │

│ node v8 arguments │ │

│ watch & reload │ ✘ │

│ interpreter │ node │

│ restarts │ 0 │

│ unstable restarts │ 0 │

│ uptime │ 5s │

│ created at │ 2015-11-17T10:03:04.075Z │

└───────────────────┴───────────────────────────────────────────┘

This shows you the actual files it is using for error output and log output. Because it has split them into separate files, it is hard to get a properly view of where errors occurred relative to normal output.

But regardless, this shows you where the raw log files are, so you don't need to use the pm2 logs command - just view those .log files yourself. That will remove any weirdness pm2 may be introducing when you access them.

Dave C-J

unread,

Nov 17, 2015, 12:03:11 PM11/17/15

to node...@googlegroups.com

Peter

why is it generating a log entry every second ? - the gpio node should only log like that if you have verbose turned on... it shouldn't do that if you don't use -v...

Peter Scargill

unread,

Nov 17, 2015, 12:22:36 PM11/17/15

to node...@googlegroups.com

Hi there

Until you mentioned this now I had no idea I’d set it up with –v but sure enough….

Ok, so this is the relevant part of my installation script..

cd /root

pm2 start /usr/bin/node-red -- -v

pm2 save

pm2 startup

Erm, any idea how to revert that???

From: node...@googlegroups.com [mailto:node...@googlegroups.com] On Behalf Of Dave C-J

Sent: 17 November 2015 17:03
To: node...@googlegroups.com

--
http://nodered.org
---
You received this message because you are subscribed to a topic in the Google Groups "Node-RED" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/node-red/YgdPNpqEKzI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to node-red+u...@googlegroups.com.

Mark Setrem

unread,

Nov 17, 2015, 12:39:01 PM11/17/15

to Node-RED, pe...@scargill.org

Theres a good cheat sheet on pm2 here...

http://pm2.keymetrics.io/docs/usage/quick-start/

Mark Setrem

unread,

Nov 17, 2015, 12:48:44 PM11/17/15

to Node-RED

You need to list the process running using "pm2 list"

Then delete the specific process id that you no longer want to autostart. e.g. "pm2 delete 0"

then recreate e.g.

"pm2 start /usr/bin/node-red"

Peter Scargill

unread,

Nov 17, 2015, 4:34:01 PM11/17/15

to node...@googlegroups.com

Yup that seems to have done it - both systems now reset - I wonder if that will have any effect on my regular rebooting issue - time will tell.

Both Spanish and English Pis have reported in rebooted. Clock is ticking :-)

Pete.

-----Original Message-----
From: node...@googlegroups.com [mailto:node...@googlegroups.com] On Behalf Of Mark Setrem
Sent: 17 November 2015 17:49
To: Node-RED <node...@googlegroups.com>
Subject: Re: [node-red] Re: Node-Red Logs

Peter Scargill

unread,

Nov 18, 2015, 8:37:04 AM11/18/15

to Node-RED, pe...@scargill.org

Guys

Firstly thanks to your input I'm now much more aware of the capabilities of PM2. Thank you for that.

Secondly, thanks to Dave I was made aware that I had verbose logging on - I've not realised that - amazing when you look back at code after a while and think "what was I on".

So now I have turned the logging off on both of my machines. I did this last night.

And here's the thing... though it is too early to make really sensible comment, for the first time since I put the power up email on both machines... I've had no reboots of Node-Red. I have made NO other changes other than using PM2 to scrap the service and start one the same in every way except no verbose logging. EVERY day in the morning I would get a "Node-Red has powered up" email. I'd checked with webmin and in neither case were the actual Raspberry Pis rebooting, just node-red. Similarly in BOTH cases, WEBMIN would report very minimal CPU use and under 50% RAM use (for everything) - so I'm wary about the idea that I could be running out of memory. But here we are, no reboots and it is well past the time I would have expected one. I'll report back longer term. What could there be in a log report that might reboot Node-Red (remembering I'm using a hard drive in each case, not SD memory). Of course - as soon as I send this off, one of them will probably reboot just to prove me wrong. I know they are both working as I'm sitting looking at the Node-Red interface via port 1880 and both have sent me a battery state report by email this morning (I have a solar pergola lighting installation and an ESP8266 measures the state of a solar-charged car battery every 15 minutes and reports minimum and maximum voltages daily).