You can uninstall with the palette manager
But installing them once wouldnāt give that error.
Have you installed other nodes that have similar capabilities?
or had you installed them using the command line with your previous install?
Hi.
i cannot access nodered so i cannot uninstall it using pallette manager.
I just install them once.
I m just tited of those error i find it discouraging using it..
Thank you.
you guys are great.
have a good day.
Marc.
change directory to your .node-red (notice the dot) and then run the command
npm uninstall <full-name-of-the-node>
Hello.
Which nodes i have to install according to the log? I just begin nodered 1 week ago..
Thanks.
Marc.
This thread goes back more than a week.
You do not need to install any more nodes.
But you do need to clean somethings up, that do not usually happen.
The Log shows two odd things.
## [node-red-contrib-moment-bug_locale/moment] Type already registered
3 Dec 12:00:21 - [warn] [node-red-contrib-google-home-notify-volume-adjustable] Type already registered
The two nodes node-red-contrib-moment-bug_locale and node-red-contrib-google-home-notify-volume-adjustable
Show that Type is already registered. This usually occurs when a you are already using a very similar node, or that you have managed to install the same node twice.
This is the same error you had 7 days ago with two there nodes. You can delete the using the same method that @shrickus, @dceejay and I have all given you by using the npm uninstall command within your .node-red directory.
You also have the following which is causing the crash
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.
This is being caused by a node you have installed that uses SMS. Again I would suggest you delete it using teh same method and get Node-RED running again. I would also go to the nodes page on flows.nodered.org and following the link that says "View on github". There under the "Issue" tab you will able to create an issue that gets sent directly to the author about the fact that their node is crashing Node-RED when the directory doesn't exist.
Hi. I tried:
npm uninstall node-red-contrib-moment-bug_locale
the log is here:
npm ERR! file /home/pi/.node-red/package.json
npm ERR! code EJSONPARSE
npm ERR! JSON.parse Failed to parse json
npm ERR! JSON.parse Unexpected string in JSON at position 3244 while parsing '{
npm ERR! JSON.parse "name": "node-red-project",
npm ERR! JSON.parse "descr'
npm ERR! JSON.parse Failed to parse package.json data.
npm ERR! JSON.parse package.json must be actual JSON, not just JavaScript.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2018-12-05T22_46_26_291Z-debug.log
and also tried that:
npm uninstall node-red-contrib-google-home-notify-volume-adjustable
and the log about the same:
npm ERR! file /home/pi/.node-red/package.json
npm ERR! code EJSONPARSE
npm ERR! JSON.parse Failed to parse json
npm ERR! JSON.parse Unexpected string in JSON at position 3244 while parsing '{
npm ERR! JSON.parse "name": "node-red-project",
npm ERR! JSON.parse "descr'
npm ERR! JSON.parse Failed to parse package.json data.
npm ERR! JSON.parse package.json must be actual JSON, not just JavaScript.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2018-12-05T22_47_58_747Z-debug.log
thanks.
Good evening.
Marc.
did you do a cd .node-red before you ran the npm uninstall?
i did: cd ~/.node-red`
Can you go to the node-red directory (cd $HOME/.node-red) and issue cat package.json and copy and paste the results here.
notice the error:
npm ERR! JSON.parse package.json must be actual JSON, not just JavaScript.
here we go:
{
"name": "node-red-project",
"description": "A Node-RED Project",
"google-tts-api": "0.0.4",
"node-red-contrib-bigtimer": "~2.0.3",
"node-red-contrib-blynk-api": "0.0.5",
"node-red-contrib-blynk-websockets": "0.0.3",
"node-red-contrib-camerapi": "0.0.38",
"node-red-contrib-cast": "^0.2.1",
"version": "0.0.1",
"private": true,
"dependencies": {
"bonjour": "^3.5.0",
"cn-dashboard-nodes": "0.0.2",
"google-tts-api": "0.0.4",
"node-red-contrib-bigtimer": "~2.0.3",
"node-red-contrib-blynk-api": "0.0.5",
"node-red-contrib-blynk-websockets": "0.0.3",
"node-red-contrib-camerapi": "0.0.38",
"node-red-contrib-cast": "^0.2.1",
"node-red-contrib-cloud-firestore": "~1.2.0",
"node-red-contrib-cpu": "0.0.4",
"node-red-firebase": "~0.1.0",
"node-red-node-darksky": "~0.1.18",
"node-red-node-forecastio": "~0.1.13",
"node-red-node-ledborg": "0.0.21",
"node-red-node-openweathermap": "~0.2.1",
"node-red-node-pi-sense-hat": "0.0.18",
"node-red-node-ping": "0.0.15",
"node-red-node-pushbullet": "0.0.12",
"node-red-node-pushover": "0.0.13",
"node-red-node-random": "^0.1.2",
"node-red-node-serialport": "^0.6.8",
"node-red-node-smooth": "^0.1.0",
"node-red-node-weather-underground": "~0.1.12",
"node-red-contrib-date": "0.0.2",
"node-red-contrib-email-out": "~0.1.1",
"node-red-contrib-esplogin": "~1.3.7",
"node-red-contrib-eztimer": "~1.0.4",
"node-red-contrib-flatten": "0.0.1",
"node-red-contrib-fred": "0.0.6",
"node-red-contrib-freeboard": "0.0.7",
"node-red-contrib-google": "~0.2.0",
"node-red-contrib-google-action": "~1.2.1",
"node-red-contrib-google-firebase": "0.0.7",
"node-red-contrib-google-home-notify": "0.0.6",
"node-red-contrib-google-home-notify-volume-adjustable": "0.0.10",
"node-red-contrib-google-tts": "~1.1.0",
"node-red-contrib-http-logger": "~1.0.1",
"node-red-contrib-ibm-watson-iot": "^0.2.8",
"node-red-contrib-ifttt": "~0.1.0",
"node-red-contrib-jde-date-time": "0.0.5",
"node-red-contrib-jsonfilter": "~0.1.0",
"node-red-contrib-jsonpath": "~0.1.1",
"node-red-contrib-key-value-store": "~0.1.8",
"node-red-contrib-linux-memory": "~0.5.0",
"node-red-contrib-moment": "~3.0.1",
"node-red-contrib-moment-bug_locale": "~1.0.4",
"node-red-contrib-mqtt-json": "~1.0.1",
"node-red-contrib-nighttime": "~1.0.35",
"node-red-contrib-notification-center": "0.0.2",
"node-red-contrib-os": "~0.1.7",
"node-red-contrib-play-audio": "^2.3.2",
"node-red-contrib-polymer": "0.0.21",
"node-red-contrib-pushover-inline-image": "~0.1.10",
"node-red-contrib-rf-command": "~1.0.0",
"node-red-contrib-rflink": "~0.1.0",
"node-red-contrib-simpletime": "~2.3.1",
"node-red-contrib-smstools": "~1.1.1",
"node-red-contrib-stoptimer": "0.0.7",
"node-red-contrib-sun-position": "~0.1.4",
"node-red-contrib-telegrambot": "~4.4.0",
"node-red-contrib-telegrambot-home": "~0.5.1",
"node-red-contrib-thingspeak": "0.0.4",
"node-red-contrib-thingspeak42": "~0.1.4",
"node-red-contrib-timecheck": "~1.1.0",
"node-red-contrib-ui_list": "~0.1.2",
"node-red-contrib-viseo-google-maps": "0.0.1",
"node-red-contrib-viseo-google-youtube": "0.0.9",
"node-red-contrib-youtube": "0.0.10",
"node-red-dashboard": "~2.10.1",
"node-red-firebase": "~0.1.0",
"node-red-node-darksky": "~0.1.18",
"node-red-node-forecastio": "~0.1.13",
"node-red-node-ledborg": "0.0.21",
"node-red-node-openweathermap": "~0.2.1",
"node-red-node-pi-sense-hat": "0.0.18",
"node-red-node-ping": "0.0.15",
"node-red-node-pushbullet": "0.0.12",
"node-red-node-pushover": "0.0.13",
"node-red-node-random": "^0.1.2",
"node-red-node-serialport": "^0.6.8",
"node-red-node-smooth": "^0.1.0",
"node-red-node-weather-underground": "~0.1.12",
"node-red-node-youtube": "0.0.5",
"ttb-node-red-counter": "~0.1.0"
}
thanks.
marc.
If you have just started wiht NR, why do you have so many nodes installed?
Are you really going to use them all?
nope, just experimenting..
Well as an experimenter, you must know that failures are a part of learning. And a good experimenter keeps detailed notes so they can repeat their experiment.
Since you are experimenting, I would suggest you delete the .node-red folder and it's sub directories (cd $HOME and then rm .node-red -rf) and reinstall node-red using the install/upgrade script found here: https://nodered.org/docs/hardware/raspberrypi
Then you can repeat your experiment with what you have learned.
1 Like
thanks a lot
So one of the issues in your startup log is being caused by nodes that are forks of each other
When you start again only choose one of these nodes
But the SMS one needs to be reported to the nodes owner as I mentioned before
