Start ... and freeze?

#1

I have installed the last version of Node RED on my Siemens IOT2040.

I have developped my Node RED software with the 0.18.7 version. Normally it take 6/7min to start.
It perfectly running with the 0.18.7 version.

I put my "flows_iot2000.json" on the Node RED folder (last version) and it doesn't start completly... after 3/4min it stop !
I don't understand ..

0 Likes

#2

Have a look at the node red log on startup (the log that starts with Welcome to node red), that may well give you a clue. Post it here if it doesn't help.

0 Likes

#3
Welcome to Node-RED
===================

16 Nov 10:18:09 - [info] Node-RED version: v0.19.5
16 Nov 10:18:09 - [info] Node.js  version: v6.12.3
16 Nov 10:18:09 - [info] Linux 4.4.105-cip15 ia32 LE
16 Nov 10:18:21 - [info] Loading palette nodes
16 Nov 10:18:25 - [debug] Module: node-red-node-email 0.1.29
16 Nov 10:18:25 - [debug]         /usr/lib/node_modules/node-red/node_modules/node-red-node-email
16 Nov 10:18:25 - [debug] Module: node-red-node-feedparser 0.1.14
16 Nov 10:18:25 - [debug]         /usr/lib/node_modules/node-red/node_modules/node-red-node-feedparser
16 Nov 10:18:25 - [debug] Module: node-red-node-rbe 0.2.4
16 Nov 10:18:25 - [debug]         /usr/lib/node_modules/node-red/node_modules/node-red-node-rbe
16 Nov 10:18:25 - [debug] Module: node-red-node-twitter 1.1.4
16 Nov 10:18:25 - [debug]         /usr/lib/node_modules/node-red/node_modules/node-red-node-twitter
16 Nov 10:18:25 - [debug] Module: node-red-configurable-ping 1.0.1
16 Nov 10:18:25 - [debug]         /usr/lib/node_modules/node-red-configurable-ping
16 Nov 10:18:25 - [debug] Module: node-red-contrib-boolean-logic 0.0.3
16 Nov 10:18:25 - [debug]         /usr/lib/node_modules/node-red-contrib-boolean-logic
16 Nov 10:18:25 - [debug] Module: node-red-dashboard 2.10.1
16 Nov 10:18:25 - [debug]         /usr/lib/node_modules/node-red-dashboard
16 Nov 10:18:25 - [debug] Module: node-red-node-intel-gpio 0.0.5
16 Nov 10:18:25 - [debug]         /usr/lib/node_modules/node-red-node-intel-gpio
16 Nov 10:18:25 - [debug] Module: node-red-node-serialport 0.6.8
16 Nov 10:18:25 - [debug]         /usr/lib/node_modules/node-red-node-serialport
16 Nov 10:18:34 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
16 Nov 10:18:34 - [warn] rpi-gpio : Cannot find Pi RPi.GPIO python library
16 Nov 10:19:06 - [info] Dashboard version 2.10.1 started at /ui
16 Nov 10:19:08 - [info] Settings file  : /home/root/.node-red/settings.js
16 Nov 10:19:09 - [info] Context store  : 'default' [module=memory]
16 Nov 10:19:09 - [info] User directory : /home/root/.node-red
16 Nov 10:19:09 - [warn] Projects disabled : editorTheme.projects.enabled=false
16 Nov 10:19:09 - [info] Flows file     : /home/root/.node-red/flows_iot2000.json
16 Nov 10:19:10 - [info] Server now running at http://127.0.0.1:1880/
16 Nov 10:19:10 - [debug] loaded flow revision: 7f50c56271550d8a9624f492f44bbbd9
16 Nov 10:19:10 - [debug] red/runtime/nodes/credentials.load : no user key present
16 Nov 10:19:10 - [debug] red/runtime/nodes/credentials.load : using default key
16 Nov 10:19:10 - [debug] red/runtime/nodes/credentials.load : keyType=system
16 Nov 10:19:10 - [warn]

---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------

16 Nov 10:19:10 - [trace] runtime event: {"id":"runtime-state","retain":true}
16 Nov 10:19:21 - [trace] runtime event: {"id":"runtime-deploy","payload":{"revision":"7f50c56271550d8a9624f492f44bbbd9"},"retain":true}
16 Nov 10:19:21 - [info] Starting flows
16 Nov 10:19:21 - [debug] red/nodes/flows.start : starting flow : global
16 Nov 10:19:21 - [debug] red/nodes/flows.start : starting flow : 6d8f2a52.f3b124
16 Nov 10:19:21 - [debug] red/nodes/flows.start : starting flow : d29b12a6.bb8658
16 Nov 10:19:21 - [debug] red/nodes/flows.start : starting flow : 2c5eed53.6a139a
16 Nov 10:19:21 - [debug] red/nodes/flows.start : starting flow : b4be01a8.ad6e28
16 Nov 10:19:21 - [debug] red/nodes/flows.start : starting flow : 9f132dbd.a915e8
16 Nov 10:19:21 - [debug] red/nodes/flows.start : starting flow : 6c9408dc.27f8e8
16 Nov 10:19:21 - [debug] red/nodes/flows.start : starting flow : 9ba698e3.cfaf88
16 Nov 10:19:21 - [debug] red/nodes/flows.start : starting flow : 3bfe7ac1.ea9556
16 Nov 10:19:21 - [debug] red/nodes/flows.start : starting flow : a45d0edc.7555e
16 Nov 10:19:21 - [info] [inject:Send] repeat = 300000
16 Nov 10:19:21 - [info] [inject:Read] repeat = 60000
16 Nov 10:19:25 - [info] [inject:Read] repeat = 300000
16 Nov 10:19:49 - [info] [inject:Read] repeat = 10000
16 Nov 10:19:51 - [info] [inject:Send] repeat = 3600000
16 Nov 10:20:11 - [info] [inject:Read] repeat = 10000
16 Nov 10:20:11 - [info] [inject:Update] crontab = 01 03 * * *
16 Nov 10:20:19 - [info] [inject:Read] repeat = 10000
16 Nov 10:20:37 - [info] [inject:8fdff454.c4a648] repeat = 10000
16 Nov 10:21:01 - [info] [udp in:f607b0a2.f6ed8] udp: port 1027 already in use
16 Nov 10:21:15 - [trace] runtime event: {"id":"runtime-state","retain":true}
16 Nov 10:21:15 - [info] Started flows
16 Nov 10:21:15 - [info] [udp out:f210b1f6.82205] udp broadcast ready:  -> :1027
16 Nov 10:21:15 - [info] [udp in:f607b0a2.f6ed8] udp listener at 0.0.0.0:53771
0 Likes

#4

Then stop ... and I can't access to :1880 to see Node RED interface

0 Likes

#5

What happens when you try to access the web interface?
What do you see in the browser developer console when you try to access the url?

0 Likes

#6

Nothing .. i have error 404

0 Likes

#7

If you rename the folder containing the flows and settings file (normally .node-red but I don't know about that device) and restart node-red then does it work and if not what is in the log this time?

0 Likes

#8

Yes, if i delete the flow file it work normally
But my flow file work on Node RED 0.18.7 with an other device (but exactly the same installation)

0 Likes

#9

I try the same flow on a Raspberry with Node RED 0.19.2 and it work .. :frowning:
Is it possible it because the starting during 6 minutes ?

0 Likes

#10

Have you tried waiting for a very long time to see if it eventually starts? Also watch the log to see if anything further appears.

I presume you saw the problem in the log with udp: port 1027 already in use. It might be worth sorting that out in case it is related. It might be some sort of network hang. Are you still able to access the PLC on the network when node red has apparently stopped?

0 Likes

#11

Yes ... but nothing happen

Yes, it's possible to Ping and access with SSH

0 Likes

#12

Are you going to investigate the port 1027 issue?

0 Likes

#13

Hello, i'm investigating.. but i don't find anythink for the port 1027 ..

0 Likes

#14
root@iot2000:~# netstat -tlnu
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 0.0.0.0:1534            0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:1880            0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:1883            0.0.0.0:*               LISTEN
tcp        0      0 :::22                   :::*                    LISTEN
tcp        0      0 :::1883                 :::*                    LISTEN
udp        0      0 0.0.0.0:1534            0.0.0.0:*
udp        0      0 0.0.0.0:34655           0.0.0.0:*
0 Likes

#15

I have delete the udp node using port 1027 and i have the same problem. Loading is stop after 3 min...

0 Likes

#16

I can't think of anything other than to start chopping bits out of the flow till it works and then put them back to find which bit is causing the problems. Perhaps someone else will have an idea.

0 Likes