Node-Red don't longer start

[fredshortlv129bis]

In the meantime, I was doing the above instructions but without success. The installation of Node.js12 and 14 LTS is always aborted with the same error message in the line above.

bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered) --node12

I now uninstall Mosquitto and redo everything again.
I'll let you know.
Many thanks. Jack

[fredshortlv129bis]

Unfortunately, with all that I have done, no 1 mm of progress has been made. I am getting close to despair.

In between, I also did a shutdown

Meanwhile, it is past midnight here and bedtime.

With many heartfelt thanks for yours compassion.
It is commendable.

Jack

[Colin]

Have you got as far as these commands working?

sudo apt-get update
sudo apt-get dist-upgrade

[fredshortlv129bis]

pi@raspberrypi:~ $ sudo apt-get update
Geraakt:1 http://raspbian.raspberrypi.org/raspbian stretch InRelease
Geraakt:2 http://archive.raspberrypi.org/debian stretch InRelease
Ophalen:3 https://repo.mosquitto.org/debian jessie InRelease [11,0 kB]
Geraakt:3 https://repo.mosquitto.org/debian jessie InRelease
Geraakt:4 https://repos.influxdata.com/debian stretch InRelease
Ophalen:5 https://repo.mosquitto.org/debian stretch InRelease [12,4 kB]
Geraakt:5 https://repo.mosquitto.org/debian stretch InRelease
Segmentation fault                                        
Pakketlijsten worden ingelezen... Klaar
N: Negeren van bestand 'mosquitto-jessie.list.2' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
N: Negeren van bestand 'mosquitto-jessie.list.6' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
N: Negeren van bestand 'mosquitto-jessie.list.5' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
N: Negeren van bestand 'mosquitto-stretch.list.1' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
N: Negeren van bestand 'mosquitto-jessie.list.4' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
N: Negeren van bestand 'mosquitto-jessie.list.1' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
N: Negeren van bestand 'mosquitto-jessie.list.3' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
N: Negeren van bestand 'mosquitto-stretch.list.2' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
pi@raspberrypi:~ $ sudo apt-get dist-upgrade
Pakketlijsten worden ingelezen... Klaar
Boom van vereisten wordt opgebouwd       
De statusinformatie wordt gelezen... Klaar
Opwaardering wordt doorgerekend... Klaar
0 opgewaardeerd, 0 nieuw geïnstalleerd, 0 te verwijderen en 0 niet opgewaardeerd.
N: Negeren van bestand 'mosquitto-jessie.list.2' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
N: Negeren van bestand 'mosquitto-jessie.list.6' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
N: Negeren van bestand 'mosquitto-jessie.list.5' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
N: Negeren van bestand 'mosquitto-stretch.list.1' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
N: Negeren van bestand 'mosquitto-jessie.list.4' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
N: Negeren van bestand 'mosquitto-jessie.list.1' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
N: Negeren van bestand 'mosquitto-jessie.list.3' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
N: Negeren van bestand 'mosquitto-stretch.list.2' in map '/etc/apt/sources.list.d/' omdat het een ongeldige bestandsextensie heeft
pi@raspberrypi:~ $

[dceejay]

As @colin suggested above - you need to clean you the /etc/apt/sources.list.d files first...

@Colin

you can first remove the package
sudo apt-get remove mosquitto mosquitto-clients
then you must remove the references to the repository. Look in the folder /etc/apt/sources.list.d and there should be a file with mosquitto in the name. Remove that and run the apt-get update again.

[Colin]

@fredshortlv129bis

Ophalen:3 https://repo.mosquitto.org/debian jessie InRelease [11,0 kB]
Geraakt:3 https://repo.mosquitto.org/debian jessie InRelease
Geraakt:4 https://repos.influxdata.com/debian stretch InRelease
Ophalen:5 https://repo.mosquitto.org/debian stretch InRelease [12,4 kB]
Geraakt:5 https://repo.mosquitto.org/debian stretch InRelease

I have just noticed, you have mosquitto sources for both jessie and stretch. Make sure you get rid of both of those. You can look inside the files to see what each is doing. That may be the fundamental cause of all these problems. If you can't find the files in sources.list.d then the reference must be in the file \etc\apt\sources.list. You can comment them out by adding a # at the front of each mosquitto line.

[fredshortlv129bis]

I find the files in the map sources.list.d .
Even though those files were previously moved to the Recycle Bin.

It is impossible to complete the files with a '#'.
Even though the Existing Properties/Rights in View/Edit/Execute are changed to 'Everyone'.
Each time the following message appears: 'The file operation was completed with errors'.

[Colin]

Do you mean you have done what I suggested, which is delete the files from sources.list.d (you will need to use sudo for that of course, you can't use your GUI file manager, I don't think) and have checked that the files are deleted, (reboot and check that they are still gone) that when you run
sudo apt-get update
they come back again?

[fredshortlv129bis]

Do I delete the mosquitto files in the map '/etc/apt/sources.list.d' with the command
'sudo rm rf /etc/apt/sources.list.d/mosquitto*'?

[Colin]

I would have thought that googling for how to delete a file using the command line in linux might have told you how.
For safety I would do them one at a time, . Also if you did have to use rf it would be -rf, but don't use -rf unless you know what you are doing. -rf tells it to empty complete folders, so if, for example you used sudo -rf and specified / etc/.. with a space after the / then it would empty the whole of the / folder, which is the complete OS, effectively erasing the disc. There would be no recovery from that.
So run
ls -l /etc/apt/sources.list.d
to see all the files. You will probably see one or more with mosquitto in the name. Then run
sudo rm /etc/apt/sources.list.d/the_first_mosquitto_file.list
then do the same for the other one.
then repeat the ls command to make sure they have gone.

[fredshortlv129bis]

pi@raspberrypi:~ $ ls -l /etc/apt/sources.list.d
totaal 8
-rw-r--r-- 1 root root  55 aug 28 22:07 influxdb.list
-rw-r--r-- 1 root root 195 apr  8  2019 raspi.list

pi@raspberrypi:~ $ sudo apt-get update
Geraakt:1 http://raspbian.raspberrypi.org/raspbian stretch InRelease
Geraakt:2 http://archive.raspberrypi.org/debian stretch InRelease
Geraakt:3 https://repos.influxdata.com/debian stretch InRelease
Segmentation fault           
Pakketlijsten worden ingelezen... Klaar
pi@raspberrypi:~ $

pi@raspberrypi:~ $ bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered) --node14
........................

Running Node-RED install for user pi at /home/pi on raspbian

This can take 20-30 minutes on the slower Pi versions - please wait.

  Stop Node-RED                       ✔
  Remove old version of Node-RED      ✔
/dev/fd/63: regel 408: /usr/bin/head: kan binair bestand Verkeerd uitvoerbaar bestand niet uitvoeren
  Remove old version of Node.js       ✔   v8.11.1
  Install Node.js 14 LTS              ✘   Bad install:  Node.js v8.11.1  Npm missing - Exit
  Install Node-RED core               
  Move global nodes to local          
  Npm rebuild existing nodes          
  Install extra Pi nodes              
  Add shortcut commands               
  Update systemd script               
                                      

Any errors will be logged to   /var/log/nodered-install.log

nodered-install.log (116.3 KB)

[Colin]

@fredshortlv129bis

Segmentation fault

Your system is broken. Bin the SD card (after checking that your backups are up to date) and start again.

If you have not been backing up your flows then you should be. Backup the whole .node-red folder except node_modules.
After installing node red on the new system and making sure it works then restore the .node-red folder and, in that folder run
npm install
Then restart node red.

[fredshortlv129bis]

The fact that my system is broken is no bad thing at all.
I feel remorseful that I have received so much time and patience from all of you.
I will certainly continue to install and use Node-Red on a renewed system.
Earlier, I stopped using it after I couldn't send an e-mail. Now I hear from my MAM and Fablab friends that sending a Whatsapp is a piece of cake.
How to do an npm install in a Node-Red folder I will learn later.
I will keep a positive and happy memory of your willingness and endless helpfulness.
With many heartfelt thanks.
Jack.

[Colin]

Going into the .node-red folder in a terminal and running npm install tells npm to install the extra nodes that you had installed in the old system. The information on which nodes you were using is in package.json and package-lock.json, which is how npm knows what to do.

[fredshortlv129bis]

After installing a new system, I have not dared to install Node-Red for 24 hours for fear of yet another failure.
Nevertheless, I now come across another obstacle, namely the choice below:

Options:
  --help            display this help and exits
  --confirm-root    install as root without asking confirmation
  --confirm-install confirm installation without asking confirmation
  --confirm-pi      confirm installation of PI specific nodes without asking confirmation
  --skip-pi         skip installing PI specific nodes without asking confirmation
  --restart         restart service if install succeeds
  --update-nodes    run npm update on existing installed nodes (within scope of package.json)
  --nodered-version if not set, the latest version is used - e.g. --nodered-version="1.3.4"
  --node12          if set, forces install of major version of nodejs 12 LTS
  --node14          if set, forces install of major version of nodejs 14 LTS
  --node16          if set, forces install of major version of nodejs 16 LTS
                    if none set, install nodejs 14 LTS if nodejs version is less than 12,
                    otherwise leave current install pi@raspberrypi:~

What do you recommend if I want to make use of the 'Palette Manager' for the effective use of the 'WhatsApp' node?
Finally, where version '15' was recommended earlier, '15' is not mentioned here.

Is there anything I can do wrong if I choose a forced installation, or can I miss something in that case?

[jbudd]

My most recent installation of Node-Red was on a Raspberry Pi 3B. I didn't force any particular version.
It installed Node-Red 2.1.1, node.js 12.22.7 and npm 6.14.15.

Another Pi, a recently updated 4B, has Node-Red 2.1.3, node.js 16.13.0 and npm 8.1.0.

Palette manager and Node-Red generally works fine on both systems.

[fredshortlv129bis]

Yep, it finally worked, but not as predicted due to my NOOBS version.
Thank you. Jack