Hi. It's been 2 days i have started with node-red, i think i have installed a wrong package.
Before it was working fine then i see that when i tried to run node-red:
Start Node-RED
Once Node-RED has started, point a browser at http://192.168.0.169:1880
On Pi Node-RED works better with the Firefox or Chrome 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
Starting as a systemd service.
26 Nov 20:28:09 - [info] Dashboard version 2.10.1 started at /ui
26 Nov 20:28:10 - [warn] ------------------------------------------------------
26 Nov 20:28:10 - [warn] [node-red-contrib-pushover/pushover] Type already registered
26 Nov 20:28:10 - [warn] [node-red-contrib-ovia-os/os] Type already registered
26 Nov 20:28:10 - [warn] ------------------------------------------------------
26 Nov 20:28:10 - [info] Settings file : /home/pi/.node-red/settings.js
26 Nov 20:28:10 - [info] Context store : 'default' [module=memory]
26 Nov 20:28:10 - [info] User directory : /home/pi/.node-red
26 Nov 20:28:10 - [warn] Projects disabled : editorTheme.projects.enabled=false
26 Nov 20:28:10 - [info] Flows file : /home/pi/.node-red/flows_raspberrypi.json
26 Nov 20:28: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.
26 Nov 20:28:10 - [info] Starting flows
26 Nov 20:28:11 - [info] Started flows
26 Nov 20:28:11 - [info] Server now running at ....
26 Nov 20:28:11 - [red] Uncaught Exception:
26 Nov 20:28:11 - Error: ENOENT: no such file or directory, stat '/var/spool/sms/incoming'
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Unit entered failed state.
nodered.service: Failed with result 'exit-code'.
nodered.service: Service hold-off time over, scheduling restart.
Stopped Node-RED graphical event wiring tool.
Started Node-RED graphical event wiring tool.
26 Nov 20:28:14 - [info]
I really dont know what i did wrong.
I would like some help please.
you have managed to a couple of packages that overlap with existing package names. For now you will have to uninstall them manually. (We are trying to handle this situation better in the next release).
You need to find where they are installed (usually your ~/.node-red/ directory but may vary depending on how you installed.) - and then run npm uninstall node-red-contrib-pushover node-red-contrib-ovia-os
whatever node you have for handling sms is failing to access a directory. Which node is that ? Either there are some more pre-requisites required to et it up correctly or there is a bug in that node.
First can you post the start of the log, from the Welcome message. To see this you can run
node-red-stop
node-red-start
Then sort the Type already registered messages. These probably mean that you have installed two nodes that provide the same node types. Have you installed two pushover nodes? In the case of ovia I suspect possibly you have installed node-red-contrib-os as well as the ovia one. Fix those by uninstalling one of the duplicates and see where that takes you.
I suspected there was another problem, but my strategy is always to fix the problems that have obvious solutions first, sometimes you find unexpectedly that it also fixes other problems.
Which node-red directory? Do you mean the .node-red directory in your home folder? If so then all you have to do is to restart node-red and it will recreate the directory with an empty flow.
28 Nov 18:41:29 - [info] Node-RED version: v0.19.5
28 Nov 18:41:29 - [info] Node.js version: v10.13.0
28 Nov 18:41:29 - [info] Linux 4.14.79-v7+ arm LE
28 Nov 18:41:30 - [info] Loading palette nodes
28 Nov 18:41:35 - [info] Polymer started at /polymer
Missing ENV var CONFIG_PATH
28 Nov 18:41:40 - [info] Dashboard version 2.10.1 started at /ui
28 Nov 18:41:40 - [warn] ------------------------------------------------------
28 Nov 18:41:40 - [warn] [node-red-contrib-pushover-inline-image/pushover] Type already registered
28 Nov 18:41:40 - [warn] [node-red-contrib-ovia-os/os] Type already registered
28 Nov 18:41:40 - [warn] ------------------------------------------------------
28 Nov 18:41:40 - [info] Settings file : /home/pi/.node-red/settings.js
28 Nov 18:41:40 - [info] Context store : 'default' [module=memory]
28 Nov 18:41:40 - [info] User directory : /home/pi/.node-red
28 Nov 18:41:40 - [warn] Projects disabled : editorTheme.projects.enabled=false
28 Nov 18:41:40 - [info] Flows file : /home/pi/.node-red/flows_raspberrypi.json
28 Nov 18:41:40 - [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.
28 Nov 18:41:40 - [info] Starting flows
28 Nov 18:41:41 - [info] Started flows
28 Nov 18:41:41 - [info] Server now running at http://127.0.0.1:1880/
28 Nov 18:41:41 - [red] Uncaught Exception:
28 Nov 18:41:41 - Error: ENOENT: no such file or directory, stat '/var/spool/sms/incoming'
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Unit entered failed state.
nodered.service: Failed with result 'exit-code'.
nodered.service: Service hold-off time over, scheduling restart.
Stopped Node-RED graphical event wiring tool.
Started Node-RED graphical event wiring tool.
28 Nov 18:41:43 - [info]
As Dave pointed out previously, this missing directory appears to be causing the crash.
Does it exist? If so, what are its permissions? If not, try creating it and restarting node-red.
And you still need to get rid of these duplicate nodes. Have you tried to uninstall them, or do you need help with that also?
type that:
npm uninstall node-red-contrib-pushover node-red-contrib-ovia-os
got that:
npm WARN saveError ENOENT: no such file or directory, open '/home/pi/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/home/pi/package.json'
npm WARN pi No description
npm WARN pi No repository field.
npm WARN pi No README data
npm WARN pi No license field.
audited 938 packages in 11.606s
found 30 vulnerabilities (1 low, 29 moderate)
run npm audit fix to fix them, or npm audit for details
It is a hidden directory, since it starts with a dot. Try ls -la from your home directory. Or use cd ~/.node-red and see if it puts you into that hidden dir. If so, then you should be able to run npm uninstall node-red-contrib-pushover node-red-contrib-ovia-os
Hi there.
Another problems... and node-red- not quite start
here's the log
Welcome to Node-RED
3 Dec 11:59:56 - [info] Node-RED version: v0.19.5
3 Dec 11:59:56 - [info] Node.js version: v10.13.0
3 Dec 11:59:56 - [info] Linux 4.14.79-v7+ arm LE
3 Dec 11:59:57 - [info] Loading palette nodes
3 Dec 12:00:09 - [info] Polymer started at /polymer
Mon, 03 Dec 2018 17:00:11 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
In the future, you will have to enable it yourself.
See https://github.com/yagop/node-telegram-bot-api/issues/319. at internal/modules/cjs/loader.js:688:30
Missing ENV var CONFIG_PATH
3 Dec 12:00:18 - [info] Dashboard version 2.10.1 started at /ui
3 Dec 12:00:21 - [warn] ------------------------------------------------------
3 Dec 12:00:21 - [warn] [node-red-contrib-moment-bug_locale/moment] Type already registered
3 Dec 12:00:21 - [warn] [node-red-contrib-google-home-notify-volume-adjustable/google-notify] Type already registered
3 Dec 12:00:21 - [warn] ------------------------------------------------------
3 Dec 12:00:21 - [info] Settings file : /home/pi/.node-red/settings.js
3 Dec 12:00:21 - [info] Context store : 'default' [module=memory]
3 Dec 12:00:21 - [info] User directory : /home/pi/.node-red
3 Dec 12:00:21 - [warn] Projects disabled : editorTheme.projects.enabled=false
3 Dec 12:00:22 - [info] Flows file : /home/pi/.node-red/flows_raspberrypi.json
3 Dec 12:00:22 - [info] Server now running at http://127.0.0.1:1880/
3 Dec 12:00:22 - [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.
3 Dec 12:00:22 - [info] Starting flows
3 Dec 12:00:23 - [info] [google-config:643fae08.b4fb1] Reauthenticating YouTube API with AIzaSyBruo4RqbJ3XSkv1eBrF3FTH0SajC2MSHk
3 Dec 12:00:24 - [info] Started flows
3 Dec 12:00:24 - [red] Uncaught Exception:
3 Dec 12:00:24 - Error: ENOENT: no such file or directory, stat '/var/spool/sms/incoming'
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Unit entered failed state.
nodered.service: Failed with result 'exit-code'.
nodered.service: Service hold-off time over, scheduling restart.
Stopped Node-RED graphical event wiring tool.
Started Node-RED graphical event wiring tool.
3 Dec 12:00:27 - [info]
