Continuous Reload of node-red page

[roland van straten]

Node-red refuses to come back with the “programming” canvas.

Restarting the Conduit, power off/on, restart of node-red does’t make any difference.

The canvas was filled with two objects: serial input and debug

The node-red page on port 1880 keeps being reloaded.

So what now?

R

[roland van straten]

Extra info:

I logged in via the console and looked at the log file. It seems that my connection is refused (SSL). I wonder why, nothing changed from the moment it crashed until now…

Jan 19 13:31:53 mtcdt daemon.info stunnel: LOG6[420]: SSL closed (SSL_read)
Jan 19 13:31:53 mtcdt daemon.notice stunnel: LOG5[420]: Connection closed: 2605 byte(s) sent to SSL, 387 byte(s) sent to socket
Jan 19 13:31:53 mtcdt daemon.notice stunnel: LOG5[421]: Service [node-red] accepted connection from 192.168.2.2:54117
Jan 19 13:31:53 mtcdt daemon.notice stunnel: LOG5[423]: Service [node-red] accepted connection from 192.168.2.2:54115
Jan 19 13:31:53 mtcdt daemon.notice stunnel: LOG5[424]: Service [node-red] accepted connection from 192.168.2.2:54116
Jan 19 13:31:53 mtcdt daemon.notice stunnel: LOG5[422]: Service [node-red] accepted connection from 192.168.2.2:54114
Jan 19 13:31:53 mtcdt daemon.info stunnel: LOG6[421]: SSL accepted: previous session reused
Jan 19 13:31:53 mtcdt daemon.info stunnel: LOG6[421]: s_connect: connecting 127.0.0.1:1881
Jan 19 13:31:53 mtcdt daemon.err stunnel: LOG3[421]: s_connect: connect 127.0.0.1:1881: Connection refused (111)
Jan 19 13:31:53 mtcdt daemon.info stunnel: LOG6[421]: s_connect: connecting 127.0.0.1:1882
Jan 19 13:31:53 mtcdt daemon.notice stunnel: LOG5[421]: s_connect: connected 127.0.0.1:1882
Jan 19 13:31:53 mtcdt daemon.notice stunnel: LOG5[421]: Service [node-red] connected remote server from 127.0.0.1:44018
Jan 19 13:31:53 mtcdt daemon.info stunnel: LOG6[421]: Read socket closed (read hangup)
Jan 19 13:31:53 mtcdt daemon.info stunnel: LOG6[421]: SSL_shutdown successfully sent close_notify alert
Jan 19 13:31:53 mtcdt daemon.info stunnel: LOG6[422]: SSL accepted: previous session reused
Jan 19 13:31:53 mtcdt daemon.info stunnel: LOG6[422]: s_connect: connecting 127.0.0.1:1881
Jan 19 13:31:53 mtcdt daemon.err stunnel: LOG3[422]: s_connect: connect 127.0.0.1:1881: Connection refused (111)

[Jason Reiss]

What browser are you using?
Safari has a known issue with creating ssl web sockets to some web servers.

[wojtek t]

I also experienced problems with Safari, switching to Chrome helped.
Also, it takes some time to start node-red, so if you are trying right after boot…
WT

[roland van straten]

Dear all,

I have tried chrome instead. No luck. I started another Mac(Safari) with a browser and tried again. Same problem. Used my PC with FireFox No Luck.
Switched off SSL, no luck. Now I’m looking for restoring factory settings. Cannot find this… hint?

Weird.

[Jeff Hatch]

Roland,

Is the network interface you’re connecting to on the Conduit configured as a WAN or LAN? If it is configured as a WAN, you will need to go to the Administration->Access Configuration page and enable Node-RED access via WAN. Also, verify that Node-RED is running using the ‘ps’ command and verify that a listen on localhost port 1881 is currently posted. Another thing to look at is the /var/log/app/.log file (where is some UUID value) and see what Node-RED is logging there.

Jeff

[Heath Raftery]

Same problem here. Did you ever get it sorted?

I can confirm that the node-red process is crashing – as soon as I check the “Enabled” box in the Node-RED config page in AEP under Apps, the node-red process appears. Some 10s of seconds later it disappears and is replaced with node-angel and node.

In the intervening period, the /var/log/app/node-red.log file shows:

Welcome to Node-RED
===================

12 Dec 17:17:40 - [info] Node-RED version: v0.11.1
12 Dec 17:17:40 - [info] Node.js  version: v0.10.40
12 Dec 17:17:40 - [info] Loading palette nodes

but once the process disappears that file is wiped clean.

Hitting the Node-RED URL (port 1880) at this time results in the continuous refresh the OP reported.

I’ve tried increasing the log level to ‘debug’. Various restarts and reboots. Various browsers and cookie deletion. I tried removing the /var/config/app/install/development/ directory to start fresh. All with no change in behaviour.

This is killing us. We need a resolution.

[Heath Raftery]

Okay, finally solved it.

For me the problem was a damaged inode in the /opt/node-red/nodes/ folder. I had installed a new node there but the directory was no longer functional. node-red was choking on it during start up. I discovered that by running /opt/node-red/bin/node-red-pi from the command line, which reported the relevant error. Running node-red-pi was a wild guess – I tried for ages to find what the actual invocation command is when you click the “Enabled” button for Node-RED in the AEP web interface. After tracing through a heap of javascript and lighttpd.conf stuff I found a reference to /usr/bin/rcell_api but go no further.

Anyway, the inode was stuffed so I moved the enclosing folder out of the way, copied everything into a new folder of the same name and I’m back in business.

Took forever partly because all the node stuff (including npm and node-red) takes so bloody long to start.

[Author]

Posts