Not sure what you mean by that. The problem described here is a problem with updating node red so how can it suddenly have started happening?
yes, sorry, it wasn't very clear. I got the same error as the original poster when I used the bash script to update node red on my pi3b. I last did this some time in January and it worked without any problems. While trying the suggested solutions I noticed the original post was a couple of years old, so has this issue resurfaced?
gary
Not that we are aware of. What does the log report ?
There is not much in the install log
'''***************************************
Started : Sat Mar 28 00:06:14 CET 2020
Running for user openhabian at /home/openhabian
Found global nodes: :
WARNING: apt does not have a stable CLI interface yet. 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 0 not upgraded.
Now install nodejs'''
I found nodejs was already installed when I did as suggested. I then installed nodered:
openhabian@openHABianPi:~$ sudo apt-get install nodejs
Reading package lists... Done
Building dependency tree
Reading state information... Done
nodejs is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[14:03:06] openhabian@openHABianPi:~$ sudo apt-get install nodered
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
nodejs-legacy
The following NEW packages will be installed:
nodejs-legacy nodered
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 5,372 kB of archives.
After this operation, 140 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://archive.raspberrypi.org/debian/ jessie/main nodered armhf 0.15.3-1 [5,292 kB]
Get:2 http://mirrordirector.raspbian.org/raspbian/ jessie/main nodejs-legacy all 0.10.29~dfsg-2 [80.4 kB]
Fetched 5,372 kB in 1s (3,777 kB/s)
On branch master
Changes not staged for commit:
modified: openhab2/scripts/njsTuya (modified content, untracked content)
modified: openhab2/scripts/openhab2_pub_001 (modified content, untracked content)
modified: openhab2/scripts/tuyapi (modified content)
no changes added to commit
warning: etckeeper failed to commit changes in /etc using git
Selecting previously unselected package nodejs-legacy.
(Reading database ... 52739 files and directories currently installed.)
Preparing to unpack .../nodejs-legacy_0.10.29~dfsg-2_all.deb ...
Unpacking nodejs-legacy (0.10.29~dfsg-2) ...
Selecting previously unselected package nodered.
Preparing to unpack .../nodered_0.15.3-1_armhf.deb ...
Unpacking nodered (0.15.3-1) ...
Processing triggers for man-db (2.7.5-1~bpo8+1) ...
Processing triggers for mime-support (3.58) ...
Setting up nodejs-legacy (0.10.29~dfsg-2) ...
Setting up nodered (0.15.3-1) ...
On branch master
Changes not staged for commit:
modified: openhab2/scripts/njsTuya (modified content, untracked content)
modified: openhab2/scripts/openhab2_pub_001 (modified content, untracked content)
modified: openhab2/scripts/tuyapi (modified content)
no changes added to commit
warning: etckeeper failed to commit changes in /etc using git
Updating FireMotD available updates count ... '''
When I run 'node -V' I get the following output:
node -V
node: /usr/lib/arm-linux-gnueabihf/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by node)
node: /usr/lib/arm-linux-gnueabihf/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by node)
I think this is probably the root cause of the problem but I have no idea what to do to correct this or what I could have done to cause this.
Thanks
gary
The 400 (Bad Request) status code indicates that the server cannot or will not process the request because the received syntax is invalid, nonsensical, or exceeds some limitation on what the server is willing to process. It means that the request itself has somehow incorrect or corrupted and the server couldn't understand it. The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method . Therefore, it prevents the website from being properly displayed. The main thing to understand is that the 400 Bad Request error is a client-side error.
The cause of 400 Bad Request error can be a wrongly written URL or a URL that contains unrecognizable characters. Another cause of the error might be an invalid or expired cookie. Also, if you try to upload a file that's too large. If the server is programmed with a file size limit, then you might encounter a 400 error.
Hi & welcome to the forum.
The post you responded to is from 3 years ago and I'm sure by now they either gave up or got things fixed.
The info you provided is appreciated but this thread is now too old to be relevant too today's version of node-red so to save further confusion, this thread will be closed.
Thanks for taking the time to respond.
