giova77
Topic Author
Posts: 5
Joined: 10 Dec 2020, 20:25

Unable to upgrading Node-RED

10 Dec 2020, 20:40

Hi,
im trying to upgrade node-red on my RevPI core 3 but I'm stuck with this error: "Failed to install Node.js - Exit", as shown in the screenshot attached.

Looking at the log it seems the script exit with this last row "Versions: node:v8.11.1 npm: ".

I searched online but i cannot find a fix, could you help me?

This is the last part of the log file:

Selecting previously unselected package libc-ares2:armhf.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 77168 files and directories currently installed.)
Preparing to unpack .../libc-ares2_1.14.0-1~bpo9+1_armhf.deb ...
Unpacking libc-ares2:armhf (1.14.0-1~bpo9+1) ...
Selecting previously unselected package libhttp-parser2.8:armhf.
Preparing to unpack .../libhttp-parser2.8_2.8.1-1~bpo9+1_armhf.deb ...
Unpacking libhttp-parser2.8:armhf (2.8.1-1~bpo9+1) ...
Selecting previously unselected package libuv1:armhf.
Preparing to unpack .../libuv1_1.18.0-3~bpo9+1_armhf.deb ...
Unpacking libuv1:armhf (1.18.0-3~bpo9+1) ...
Selecting previously unselected package nodejs.
Preparing to unpack .../nodejs_8.11.1~dfsg-2~bpo9+1_armhf.deb ...
Unpacking nodejs (8.11.1~dfsg-2~bpo9+1) ...
Setting up libuv1:armhf (1.18.0-3~bpo9+1) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up libc-ares2:armhf (1.14.0-1~bpo9+1) ...
Setting up libhttp-parser2.8:armhf (2.8.1-1~bpo9+1) ...
Setting up nodejs (8.11.1~dfsg-2~bpo9+1) ...
update-alternatives: using /usr/bin/nodejs to provide /usr/bin/js (js) in auto mode
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Versions: node:v8.11.1 npm:


Thanks in advance
Attachments
Cattura.PNG
Cattura.PNG (27.78 KiB) Viewed 6937 times
 
User avatar
dirk
KUNBUS
Posts: 1667
Joined: 15 Dec 2016, 13:19
Answers: 1

Re: Unable to upgrading Node-RED

11 Dec 2020, 16:06

Hi giova77, how did you initiate the update? I know this way https://nodered.org/docs/getting-started/raspberrypi
Or did you execute something else? Can you extend the verbosity of the output? There is an information about the install log on the screenshot. It would be helpful if you can post it.
 
giova77
Topic Author
Posts: 5
Joined: 10 Dec 2020, 20:25

Re: Unable to upgrading Node-RED

12 Dec 2020, 16:25

Hi Dirk,

I follow the same way https://nodered.org/docs/getting-started/raspberrypi
I have no idea how extend the verbosity, I use WIN SCP to see the log file.

I notice a first warning
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Then an error:
Err:5 https://teamviewer-revpi.teamviewer.com/deb tvstable Release
server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
Reading package lists...
E: The repository 'http://teamviewer-revpi.teamviewer.com/deb tvstable Release' does no longer have a Release file.
Error executing command, exiting
Then after a while the script always stops here:
Versions: node:v8.11.1 npm:
I paste the complete log file here:
Started : Sat 12 Dec 15:50:19 CET 2020
Running for user pi at /home/pi
Failed to stop nodered.service: Unit nodered.service not loaded.
Found global nodes: :

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
Package 'nodered' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 333 not upgraded.
Already have nodejs v8.11.1
Now install nodejs
Updating nodejs v8.11.1
Not using nodesource.list

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
Package 'nodejs-legacy' is not installed, so not removed
Package 'npm' is not installed, so not removed
The following packages were automatically installed and are no longer required:
libc-ares2 libhttp-parser2.8 libuv1
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
nodejs
0 upgraded, 0 newly installed, 1 to remove and 333 not upgraded.
After this operation, 15.8 MB disk space will be freed.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 77200 files and directories currently installed.)
Removing nodejs (8.11.1~dfsg-2~bpo9+1) ...
Processing triggers for man-db (2.7.6.1-2) ...
dpkg: warning: ignoring request to remove nodejs which isn't installed
dpkg: warning: ignoring request to remove node which isn't installed

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be REMOVED:
libc-ares2 libhttp-parser2.8 libuv1
0 upgraded, 0 newly installed, 3 to remove and 333 not upgraded.
After this operation, 384 kB disk space will be freed.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 77188 files and directories currently installed.)
Removing libc-ares2:armhf (1.14.0-1~bpo9+1) ...
Removing libhttp-parser2.8:armhf (2.8.1-1~bpo9+1) ...
Removing libuv1:armhf (1.18.0-3~bpo9+1) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Grab the LTS bundle

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
curl is already the newest version (7.52.1-5+deb9u12).
0 upgraded, 0 newly installed, 0 to remove and 333 not upgraded.

## Installing the NodeSource Node.js 12.x repo...


## Populating apt-get cache...

+ apt-get update
Hit:2 http://mirrordirector.raspbian.org/raspbian stretch InRelease
Get:3 http://archive.raspberrypi.org/debian stretch InRelease [25.4 kB]
Hit:4 http://packages.revolutionpi.de stretch InRelease
Ign:1 https://teamviewer-revpi.teamviewer.com/deb tvstable InRelease
Err:5 https://teamviewer-revpi.teamviewer.com/deb tvstable Release
server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
Reading package lists...
E: The repository 'http://teamviewer-revpi.teamviewer.com/deb tvstable Release' does no longer have a Release file.
Error executing command, exiting

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
libc-ares2 libhttp-parser2.8 libuv1
Recommended packages:
nodejs-doc
The following NEW packages will be installed:
libc-ares2 libhttp-parser2.8 libuv1 nodejs
0 upgraded, 4 newly installed, 0 to remove and 333 not upgraded.
Need to get 4,312 kB of archives.
After this operation, 16.2 MB of additional disk space will be used.
Get:1 http://archive.raspberrypi.org/debian stretch/main armhf libc-ares2 armhf 1.14.0-1~bpo9+1 [80.7 kB]
Get:2 http://archive.raspberrypi.org/debian stretch/main armhf libhttp-parser2.8 armhf 2.8.1-1~bpo9+1 [19.3 kB]
Get:3 http://archive.raspberrypi.org/debian stretch/main armhf libuv1 armhf 1.18.0-3~bpo9+1 [86.3 kB]
Get:4 http://archive.raspberrypi.org/debian stretch/main armhf nodejs armhf 8.11.1~dfsg-2~bpo9+1 [4,126 kB]
Fetched 4,312 kB in 31s (139 kB/s)
Selecting previously unselected package libc-ares2:armhf.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 77168 files and directories currently installed.)
Preparing to unpack .../libc-ares2_1.14.0-1~bpo9+1_armhf.deb ...
Unpacking libc-ares2:armhf (1.14.0-1~bpo9+1) ...
Selecting previously unselected package libhttp-parser2.8:armhf.
Preparing to unpack .../libhttp-parser2.8_2.8.1-1~bpo9+1_armhf.deb ...
Unpacking libhttp-parser2.8:armhf (2.8.1-1~bpo9+1) ...
Selecting previously unselected package libuv1:armhf.
Preparing to unpack .../libuv1_1.18.0-3~bpo9+1_armhf.deb ...
Unpacking libuv1:armhf (1.18.0-3~bpo9+1) ...
Selecting previously unselected package nodejs.
Preparing to unpack .../nodejs_8.11.1~dfsg-2~bpo9+1_armhf.deb ...
Unpacking nodejs (8.11.1~dfsg-2~bpo9+1) ...
Setting up libuv1:armhf (1.18.0-3~bpo9+1) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up libc-ares2:armhf (1.14.0-1~bpo9+1) ...
Setting up libhttp-parser2.8:armhf (2.8.1-1~bpo9+1) ...
Setting up nodejs (8.11.1~dfsg-2~bpo9+1) ...
update-alternatives: using /usr/bin/nodejs to provide /usr/bin/js (js) in auto mode
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Versions: node:v8.11.1 npm:

Maybe I have to launch apt-update and apt-upgrade on the RevPi?
Thanks in advance
 
User avatar
dirk
KUNBUS
Posts: 1667
Joined: 15 Dec 2016, 13:19
Answers: 1

Re: Unable to upgrading Node-RED

14 Dec 2020, 17:22

Hi giova77, the way you have performed the Node-RED update maches with me :) Yes, this is a good idea to do an update of the system with:
sudo apt update 
sudo apt upgrade
And then just then try it again afterwards.
 
giova77
Topic Author
Posts: 5
Joined: 10 Dec 2020, 20:25

Re: Unable to upgrading Node-RED

20 Dec 2020, 10:29

Hi Dirk,

all is fine now, thanks for the support!
 
giova77
Topic Author
Posts: 5
Joined: 10 Dec 2020, 20:25

Re: Unable to upgrading Node-RED

25 Dec 2020, 11:31

Hi,

as I wrote before I' ve been able to upgrade Node-RED, but now I can't work with the new version.

In particular after editing a node the program freezes (see the attached screenshot) and I have to reload the page.

I also noticed that in this updated version when I drag a node in the workspace a duplicate node is created as you see in the screenshot.

Thanks in advance
Attachments
workspace.PNG
workspace.PNG (230.14 KiB) Viewed 6065 times
 
User avatar
dirk
KUNBUS
Posts: 1667
Joined: 15 Dec 2016, 13:19
Answers: 1

Re: Unable to upgrading Node-RED

04 Jan 2021, 15:23

Hi giova77, I have moved your post here and I have written a message to the developers of the component. Thank you for your patience.
 
jgerlach-erminas
Official 3rd Party Support Erminas
Posts: 33
Joined: 22 Jan 2020, 14:31

Re: Unable to upgrading Node-RED

05 Jan 2021, 15:14

Hi giova77,

thanks for your bug report. I have opened an issue for you on our github page, there you can follow the further progess: https://github.com/erminas/node-red-con ... /issues/11.

As a first workaround: you can try using a different browser, the standard browser (epiphany-browser ) on the RevPi is a bit limited. My recommendation would be using Chrome or Firefox from a different computer on the same network, then calling eg. http://192.168.1.100:1880.

Greetings,
Jonas

Who is online

Users browsing this forum: No registered users and 0 guests