Node-red keeps restarting

#1

Hello,

I am new to node-red. I try to use node-red-contrib-viseo.
Everything was fine at first but now I am stuck with node-red rebooting all the time.
I thought my flow somehow get corrupted so it rename flows.json temporary as flows.json.bak but the same error keeps occuring.

0|MyFirstBot | Welcome to Node-RED
0|MyFirstBot | ===================
0|MyFirstBot | 5 Nov 13:32:50 - [info] Node-RED version: v0.17.5
0|MyFirstBot | 5 Nov 13:32:50 - [info] Node.js version: v8.12.0
0|MyFirstBot | 5 Nov 13:32:50 - [info] Linux 4.4.0-138-generic x64 LE
0|MyFirstBot | 5 Nov 13:32:50 - [info] Loading palette nodes
0|MyFirstBot | Loading locale: default for /home/godestalbin/mybot/bot/data/locales/default.json
0|MyFirstBot | ###
0|MyFirstBot | ### The "request" library is not installed automatically anymore.
0|MyFirstBot | ### But required by "request-promise".
0|MyFirstBot | ###
0|MyFirstBot | ### npm install request --save
0|MyFirstBot | ###
0|MyFirstBot | 5 Nov 13:33:01 - [warn] ------------------------------------------------------
0|MyFirstBot | 5 Nov 13:33:01 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node
0|MyFirstBot | 5 Nov 13:33:01 - [warn] [dialogflow] Error: Cannot find module 'request' (line:4)
0|MyFirstBot | 5 Nov 13:33:01 - [warn] [log-sqlite] Error: Cannot find module 'sqlite3' (line:5)
0|MyFirstBot | 5 Nov 13:33:01 - [warn] [salesforce-cc-object] Error: /home/godestalbin/mybot/framework/node_modules/node-red-contrib-viseo-salesforce/node-salesforce-cc-object.html does not exist
0|MyFirstBot | 5 Nov 13:33:01 - [warn] [salesforce-cc-config] Error: /home/godestalbin/mybot/framework/node_modules/node-red-contrib-viseo-salesforce/node-salesforce-cc-config.html does not exist
0|MyFirstBot | 5 Nov 13:33:01 - [warn] ------------------------------------------------------
0|MyFirstBot | 5 Nov 13:33:01 - [info] Settings file : /home/godestalbin/mybot/framework/conf/node-red-config.js
0|MyFirstBot | 5 Nov 13:33:01 - [info] User directory : /home/godestalbin/mybot/bot/data/
0|MyFirstBot | 5 Nov 13:33:01 - [info] Flows file : /home/godestalbin/mybot/bot/data/flows.json
0|MyFirstB | 5 Nov 13:32:47 - [info] Settings file : /home/godestalbin/mybot/framework/conf/node-red-config.js
0|MyFirstB | 5 Nov 13:32:47 - [info] User directory : /home/godestalbin/mybot/bot/data/
0|MyFirstB | 5 Nov 13:32:47 - [info] Flows file : /home/godestalbin/mybot/bot/data/flows.json
0|MyFirstB | 5 Nov 13:32:47 - [info] Server now running at http://127.0.0.1:1880/
0|MyFirstB | 5 Nov 13:32:47 - [info] Starting flows
0|MyFirstB | Missing server configuration, fallback on Node-RED server
0|MyFirstB | 5 Nov 13:32:47 - [info] Started flows

0|MyFirstBot | TypeError: Cannot read property 'getSessions' of undefined
0|MyFirstBot | at loadSessions (/home/godestalbin/mybot/framework/node_modules/node-red/red/api/auth/tokens.js:57:34)
0|MyFirstBot | at Object.get (/home/godestalbin/mybot/framework/node_modules/node-red/red/api/auth/tokens.js:75:16)
0|MyFirstBot | at WebSocket. (/home/godestalbin/mybot/framework/node_modules/node-red/red/api/comms.js:114:36)
0|MyFirstBot | at emitTwo (events.js:126:13)
0|MyFirstBot | at WebSocket.emit (events.js:214:7)
0|MyFirstBot | at Receiver.ontext (/home/godestalbin/mybot/framework/node_modules/ws/lib/WebSocket.js:841:10)
0|MyFirstBot | at /home/godestalbin/mybot/framework/node_modules/ws/lib/Receiver.js:536:18
0|MyFirstBot | at Receiver.applyExtensions (/home/godestalbin/mybot/framework/node_modules/ws/lib/Receiver.js:371:5)
0|MyFirstBot | at /home/godestalbin/mybot/framework/node_modules/ws/lib/Receiver.js:508:14
0|MyFirstBot | at Receiver.flush (/home/godestalbin/mybot/framework/node_modules/ws/lib/Receiver.js:347:3)
0|MyFirstBot | at Receiver.finish (/home/godestalbin/mybot/framework/node_modules/ws/lib/Receiver.js:541:12)
0|MyFirstBot | at Receiver.expectHandler (/home/godestalbin/mybot/framework/node_modules/ws/lib/Receiver.js:493:33)
0|MyFirstBot | at Receiver.add (/home/godestalbin/mybot/framework/node_modules/ws/lib/Receiver.js:103:24)
0|MyFirstBot | at Socket.realHandler (/home/godestalbin/mybot/framework/node_modules/ws/lib/WebSocket.js:825:20)
0|MyFirstBot | at emitOne (events.js:116:13)
0|MyFirstBot | at Socket.emit (events.js:211:7)
0|MyFirstBot | at addChunk (_stream_readable.js:263:12)
0|MyFirstBot | at readableAddChunk (_stream_readable.js:250:11)
0|MyFirstBot | at Socket.Readable.push (_stream_readable.js:208:10)
0|MyFirstBot | at TCP.onread (net.js:601:20)
0|MyFirstBot | 5 Nov 13:32:49 - [red] Uncaught Exception:
0|MyFirstBot | 5 Nov 13:32:49 - TypeError: Cannot read property 'getSessions' of undefined
0|MyFirstBot | at loadSessions (/home/godestalbin/mybot/framework/node_modules/node-red/red/api/auth/tokens.js:57:34)
0|MyFirstBot | at Object.get (/home/godestalbin/mybot/framework/node_modules/node-red/red/api/auth/tokens.js:75:16)
0|MyFirstBot | at WebSocket. (/home/godestalbin/mybot/framework/node_modules/node-red/red/api/comms.js:114:36)
0|MyFirstBot | at emitTwo (events.js:126:13)
0|MyFirstBot | at WebSocket.emit (events.js:214:7)
0|MyFirstBot | at Receiver.ontext (/home/godestalbin/mybot/framework/node_modules/ws/lib/WebSocket.js:841:10)
0|MyFirstBot | at /home/godestalbin/mybot/framework/node_modules/ws/lib/Receiver.js:536:18
0|MyFirstBot | at Receiver.applyExtensions (/home/godestalbin/mybot/framework/node_modules/ws/lib/Receiver.js:371:5)
0|MyFirstBot | at /home/godestalbin/mybot/framework/node_modules/ws/lib/Receiver.js:508:14
0|MyFirstBot | at Receiver.flush (/home/godestalbin/mybot/framework/node_modules/ws/lib/Receiver.js:347:3)
0|MyFirstBot | at Receiver.finish (/home/godestalbin/mybot/framework/node_modules/ws/lib/Receiver.js:541:12)
0|MyFirstBot | at Receiver.expectHandler (/home/godestalbin/mybot/framework/node_modules/ws/lib/Receiver.js:493:33)
0|MyFirstBot | at Receiver.add (/home/godestalbin/mybot/framework/node_modules/ws/lib/Receiver.js:103:24)
0|MyFirstBot | at Socket.realHandler (/home/godestalbin/mybot/framework/node_modules/ws/lib/WebSocket.js:825:20)
0|MyFirstBot | at emitOne (events.js:116:13)
0|MyFirstBot | at Socket.emit (events.js:211:7)
0|MyFirstBot | at addChunk (_stream_readable.js:263:12)
0|MyFirstBot | at readableAddChunk (_stream_readable.js:250:11)
0|MyFirstBot | at Socket.Readable.push (_stream_readable.js:208:10)
0|MyFirstBot | at TCP.onread (net.js:601:20)
PM2 | App [MyFirstBot:0] exited with code [1] via signal [SIGINT]
PM2 | App [MyFirstBot:0] starting in -fork mode-
PM2 | App [MyFirstBot:0] online
0|MyFirstBot | 5 Nov 13:32:50 - [info]

0 Likes

#2

You cut out the version of Node-RED and nodejs you are using.

0 Likes

#3

I updated my post with the beginning of the log showing node-red version: Node.js version: v8.12.0

0 Likes

#4

You are on a very old version of Node-RED - v0.17.5 0- the current release is v0.19.5

Is there a reason you are so far behind?
What OS?

0 Likes

#5

You need to sort out the errors at the start of the log. I suggest starting by using npm to install request as it suggests. I don't recognise the directory structure you have so I don't know which folder you should go to in order to install it. Is it a Mac? If so then possibly someone who uses Macs can advise.

0 Likes

#6

I installed node-red using the Documentation from node-red-contrib-viseo
I tried to update node-red using npm install -g --unsafe-perm node-red but I still see v0.17.5 0 in my logs.

0 Likes

#7

I've had problems with viseo before. The author tends to make too many assumptions. I believe he wrote the node to be part of a custom installation for his customers. He assumes that you are using his custom installation and not a standard node-red installation.

So if you are still seeing the different version of Node-RED, I think it likely that you are running his custom install version rather than your global version.

0 Likes

#8

Given this the best route is probably to open an issue on the github page you linked to.

0 Likes