Since I upgraded to v0.11.5, I cant connect to Node-Red either at IP address or at localhost:1880
Worked ok on v0.11.3
Worked ok on v0.11.3
[SOLVED] v0.11.5 Cant connect to Node-Red Host
|
Since I upgraded to v0.11.5, I cant connect to Node-Red either at IP address or at localhost:1880
Worked ok on v0.11.3
2017-05-15, 04:53 PM
run openplotter in debug mode to see any error on the terminal.
if no error, open a terminal and type "startup restart" too see any error. Checked your network connection? Checked your Node-Red option in Startup tab? (2017-05-15, 04:53 PM)Sailoog Wrote: run openplotter in debug mode to see any error on the terminal. (EDIT: I just tried unchecking start nodeRed in the OP Startup tab I then ran NodeRed from a terminal with "node-red-start" That came up with a string of errors and these are in attached file "nodered manual startup.txt") I get no errors in OP startup screen except usual ones wrt changing default passwords etc I could not run debug mode (see terminal extract below) but did manage startup restart Network connection is fine as is NodeRed startup option checked in startup tab startup restart hangs at "Started flows" pi@openplotter:~ $ python /home/pi/.config/openplotter/openplotter.py python: can't open file '/home/pi/.config/openplotter/openplotter.py': [Errno 2] No such file or directory pi@openplotter:~ $ startup restart Signal K starting No settings/defaults.json available signalk-server running at 0.0.0.0:3000 Cannot open NGT-1-A device /dev/ttyOP_N2K GET /signalk/v1/api/vessels/self 200 123.853 ms - 299 Stop Node-RED Use node-red-start to start Node-RED again Start Node-RED Once Node-RED has started, point a browser at http://192.168.1.106:1880 On Pi Node-RED works better with the Firefox browser Use node-red-stop to stop Node-RED Use node-red-start to start Node-RED again Use node-red-log to view the recent log output Use sudo systemctl enable nodered.service to autostart Node-RED at every boot Use sudo systemctl disable nodered.service to disable autostart on boot To find more nodes and example flows - go to http://flows.nodered.org Mon 15 May 00:00:00 UTC 2017 Mon 15 May 19:21:13 UTC 2017 Date and time retrieved from NMEA data successfully. Started Node-RED graphical event wiring tool.. 15 May 19:21:17 - [info] Welcome to Node-RED =================== 15 May 19:21:17 - [info] Node-RED version: v0.16.2 15 May 19:21:17 - [info] Node.js version: v6.10.2 15 May 19:21:17 - [info] Linux 4.4.50-v7+ arm LE 15 May 19:21:19 - [info] Loading palette nodes pi@openplotter:~ $ 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(sudoession): session opened for user root by (uid=0) pam_unix(sudoession): session closed for user root 15 May 19:21:25 - [info] Dashboard version 2.3.6 started at /ui 15 May 19:21:30 - [info] Settings file : /home/pi/.node-red/settings.js 15 May 19:21:30 - [info] User directory : /home/pi/.node-red 15 May 19:21:30 - [info] Flows file : /home/pi/.node-red/flows_openplotter.json 15 May 19:21:30 - [info] Server now running at http://127.0.0.1:1880/ 15 May 19:21:30 - [info] Starting flows 15 May 19:21:31 - [info] Started flows (EDIT: I just tried unchecking start nodeRed in the OP Startup tab I then ran NodeRed from a terminal with "node-red-start" That came up with a string of errors and these are in attached file nodered errors.txt
2017-05-16, 05:13 PM
These errors are non blocking errors, your node-red is working. I don know why you can't access to the node-red interface.
Have you checked your network connection? Are you browsing from openplotter browser or remote browser?
2017-05-16, 08:02 PM
(2017-05-16, 05:13 PM)Sailoog Wrote: These errors are non blocking errors, your node-red is working. I don know why you can't access to the node-red interface. I was browsing from remote laptop on same network but also tried Chromium on Pi OK i think Ive found (stumbled my way through) a way around it. I restored to a known good system image of OP v0.11.3 I backed up my NR flows by exporting them to the clipboard and then to a text file I then deleted all NR flows and deployed I then updated OP to v0.11.5 Stopped NR I deleted file "flows_openplotter.json" Restarted NR I then imported (from clipboard) all my previously backed up flows Deleted a few unimportant flows Deployed NR Some sort of Node-Red flow corruption during the upgrade process ? Anyway - Its working now Thanks for your help
2017-05-16, 08:10 PM
Could be.
The default node-red examples included with openplotter "flows_openplotter.json" are not the best but I do not have enough time to play with them. Maybe we should start a contest to define good default flows Please, report if this happens again. Thanks for testing |
« Next Oldest | Next Newest »
|