I have a Raspberry Pi (3b with Raspian Buster) running Node-Red.
Some Nodes which I use in my flows need an update.
However Node.js is still on version 12.22.12 and to update these Nodes to latest version I need Node.js >14.
So I performed a command which I already used succesfully on my other Pi (3B+ with Raspian Buster):
You should use full-upgrade, but usually it doesn't make any difference.
Did you check that both the update and the upgrade worked without error?
If they did succeed then there may be more information in the install log that is mentioned at the end of the install, /var/log/nodered-install.log. See if there are any errors in that. If you can't see the problem then post the log here. When pasting it in use the </> button at the top of the forum entry window to stop the forum from interpreting the text as markdown.
I am now performing the Pi update/upgrade using your command.
But this is the LOG before your command. It is (sadly) in Dutch
I guess there are errors, but my knowledge is to poor to figure out what the errors mean.
The log is too large to post as HTML text, therefor I have uploaded the TXT file
These messages in the LOG suggest that node 16 is not properly installed:
dpkg: waarschuwing: verzoek om nodejs te verwijderen wordt genegeerd omdat het niet geĂŻnstalleerd is
dpkg: waarschuwing: verzoek om node te verwijderen wordt genegeerd omdat het niet geĂŻnstalleerd is
Translation to english:
dpkg: warning: request to remove nodejs ignored because it is not installed
dpkg: warning: request to remove node ignored because it is not installed
+ apt-get update
Ophalen:1 http://raspbian.raspberrypi.org/raspbian buster InRelease [15,0 kB]
Geraakt:2 https://deb.nodesource.com/node_12.x buster InRelease
Ophalen:3 http://archive.raspberrypi.org/debian buster InRelease [32,6 kB]
Pakketlijsten worden ingelezen...
E: Bij pakketbron 'http://raspbian.raspberrypi.org/raspbian buster InRelease' is de 'Suite'-waarde gewijzigd van 'stable' naar 'oldstable'
E: Bij pakketbron 'http://archive.raspberrypi.org/debian buster InRelease' is de 'Suite'-waarde gewijzigd van 'testing' naar 'oldstable'
Error executing command, exiting
The Pi is still updating (17%) the command: sudo apt update && sudo apt full-upgrade
So I have to wait untill I can run the possible fix in the link you send me: sudo apt-get update --allow-releaseinfo-change
And then re-run sudo apt update && sudo apt full-upgrade again I guess?
I am surprised the full-upgrade part of the command is running if the update part failed. Also you said you had run it but using upgrade rather than full-upgrade, and there should be no or very little difference in what is done, so I am surprised it is now updating. The difference between using ; and && is just that using && prevents the upgrade from running if the update failed, but using just ; tells it to run the second part even if the first fails, which is pointless.
Did the update part of that command work without showing the errors that were in the log?
I can't see that part anymore, can't scroll back this far....still unzipping packages 48%
Is there also a log when sudo apt update && sudo apt full-upgrade is performed?
I have not looked lately Colin, as soon as I have time again i'll let you know. I used ssh to connect and I didnt wait till it was finished.
Thanx for the interest.
I found last week the large files in /var/log/
the deamon.log and syslog were huge together 6gb.
Today I looked again and there was a 6.1Gb deamon.log.1 file and the deamon.log was already 1.9Gb.
So I removed the deamon.log.1 file (last date was 3 days ago)
I encounter this issue since I updated node.js to v16
But I wonder why these log files grow so large and are not automatically deleted?
With crontab -e, I reset this Raspberry Pi (Buster) every day at 4.00 AM (but that is already running a few years). I thought that after a reboot the log files would automatically be deleted?
daemon.log already went from 1.9Gb to 2.1Gb in 1 hour
I have downloaded the file to my WIN10 PC to view with a text editor but 2gb is running out of mem.
