[node-red] needs restart when changes in gui after some hours

[Roland Koch]

Hy,

I started with node-red on raspberry pi jessie and tested mqtt, dashboard and different different functions. Everything is running fine after I let the raspberry pi running for some hours. 

When I change something on the browser gui after some hours and try to deploy it starts with the information "The changes include no conflicts and can be merged automatically." which is confirmed using the button "Merge changes". Normally it is necessary to make a second deploy. 

I got the message "Successfully deployed". When I try not to use an inject node I got the information  "Error: node not deployed".

Checking "node-red-log" i got following infomation

6 Mar 07:07:23 - [info] [mqtt-broker:c6077e40.fb36e] Disconnected from broker: adafruit_client@mqtt://io.adafruit.com:1883

6 Mar 07:10:21 - [info] [mqtt-broker:c6077e40.fb36e] Connected to broker: adafruit_client@mqtt://io.adafruit.com:1883

6 Mar 18:51:46 - [debug] saved flow revision: 7a399977d3320830820c96ced8e0d4f1

6 Mar 18:51:46 - [info] Stopping flows

6 Mar 18:51:46 - [info] [udp in:165ea020.86c2e] udp listener stopped

6 Mar 18:51:47 - [info] [mqtt-broker:762c6bb3.fce30c] Disconnected from broker: mqtt://localhost:1883

6 Mar 18:55:41 - [debug] saved flow revision: e6be2be514a6ec33f1db327516cfe792

6 Mar 18:56:21 - [debug] saved flow revision: 53babd7e9a4bc3796457c6e6fdba01da

6 Mar 18:56:37 - [debug] saved flow revision: d44579ba4b5e501ef181c295903277d8

6 Mar 19:08:01 - [debug] saved flow revision: d44579ba4b5e501ef181c295903277d8

6 Mar 19:08:34 - [debug] saved flow revision: 7a399977d3320830820c96ced8e0d4f1

6 Mar 19:08:55 - [debug] saved flow revision: b27f508141fbae9b929bc19933e827fe

6 Mar 19:09:14 - [debug] saved flow revision: 7a399977d3320830820c96ced8e0d4f1

I can only see the the flows were stopped including udp and mqtt from localhost. But second mqtt connection to io.adafruit.com.

Can this be the problem? If yes, is there any idea to disconnect this connection?

Thanks for your help

Roland

[Colin Law]

Have you possibly had two browsers open editing the flow separately? If you edit it on one then go to the other, make sure you refresh the view before making changes. Multiple views on the dashboard is no problem.

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
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+unsubscribe@googlegroups.com.
To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.
To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/252622dc-cb6e-480f-9d81-e559f928ba6e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Roland Koch]

Merging is not the problem. When I node-red is running I merge it and it will be the flows will be started. The main problem I have is that the flows won´t be started after some hours.

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.

[Nick O'Leary]

That log output appears to show something has hung whilst stopping your flows during a previous deploy.

Do any have any non-default nodes in your flow? Perhaps ones that will be creating some sort of network connection ? If we can track down what node is hanging, we can get it reported and fixed.

Unfortunately we don't currently have the right debug messages in place to help track it down.

Nick

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/b133cc44-56ec-452e-bb99-83f5727660f5%40googlegroups.com.

[Roland Koch]

I´m using standard nodes

- inject

- debug

- MQTT Input

- MQTT Output

- functions

- switch

- json

- some dashboard UIs 

- some global variables

- udp input

is there any possibility to increase logging without any restart? or are there other logs available? after a restart it´s possible to deploy without any problems. waiting some time (I don´t know in detail how log) the problem appears again.

[Roland Koch]

I removed all flows and created a new one - just a inject with timestamp and one debug. the same behavior. 

with a restart (sudo service nodered restart) everything works fine again.

below is the latest log. Loglevel was set to trace in settings.js

6 Mar 21:13:03 - [debug] saved flow revision: 8fbb0cf1dbc44c7d6563bc170b21af12

6 Mar 21:13:18 - [debug] saved flow revision: 641605411baac4ee906a97e00cbba716

Stopping Node-RED graphical event wiring tool....

6 Mar 21:14:33 - [info] Stopping flows

Starting Node-RED graphical event wiring tool....

Started Node-RED graphical event wiring tool..

6 Mar 21:14:44 - [info]

Welcome to Node-RED

===================

6 Mar 21:14:44 - [info] Node-RED version: v0.16.2

6 Mar 21:14:44 - [info] Node.js  version: v6.9.5

6 Mar 21:14:44 - [info] Linux 4.4.38+ arm LE

6 Mar 21:14:51 - [info] Loading palette nodes

pi : TTY=unknown ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/python -u /usr/lib/node_modules/node-red/nodes/core/hardware/nrgpio.py info

pam_unix(sudo:session): session opened for user root by (uid=0)

pam_unix(sudo:session): session closed for user root

6 Mar 21:15:29 - [info] Dashboard version 2.3.2 started at /ui

6 Mar 21:15:40 - [info] Settings file  : /home/pi/.node-red/settings.js

6 Mar 21:15:40 - [info] User directory : /home/pi/.node-red

6 Mar 21:15:40 - [info] Flows file     : /home/pi/.node-red/flows_devPi.json

6 Mar 21:15:40 - [info] Server now running at https://127.0.0.1:1880/

6 Mar 21:15:40 - [debug] loaded flow revision: 8f236e3825d62e4d88c1ac2106cd707c

6 Mar 21:15:40 - [debug] red/runtime/nodes/credentials.load : no user key present

6 Mar 21:15:40 - [debug] red/runtime/nodes/credentials.load : using default key

6 Mar 21:15:40 - [info] Starting flows

6 Mar 21:15:41 - [info] Started flows

[Roland Koch]

It seems that the problem is solved. I guess the reason was the MQTT connection to io.adafruit which was not closed. I have to look for an other possibility to connect amazon alexa with my flows.