# This can't be good - Updating nodes
**URL:** https://discourse.nodered.org/t/this-cant-be-good-updating-nodes/47610
**Category:** General
**Created:** [25 June 2021 00:40 UTC](https://discourse.nodered.org/t/this-cant-be-good-updating-nodes/47610 "2021-06-25T00:40:51Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [25 June 2021 00:40 UTC](https://discourse.nodered.org/t/this-cant-be-good-updating-nodes/47610/1 "2021-06-25T00:40:51Z")
Running:
RasPi 2 B Buster
NR 1.3.5
Node.js 12.22.1
I thought I would update a few nodes to more recent ones.
This is what I see:
Going to `/var/log` no activity on anything with `node-red` in its name.
Where do I look?
Oh, the _obvious_ way of clicking on the `view log` button gives me this.
Not exactly helpful in this situation.
Digging a bit deeper, and finding the log file `.npm/_logs/... filename`
Yikes!
`silly current tree` gets a big mention.
`silly ideal tree` comes in second.
`silly diffTrees add` then really gets a good run.
adding stuff I have never heard of.
`silly decompressActions`
and gee `@serialport` gets a lot of attention.
That command gets about 1200 lines of mentionings.
`silly extract` then starts up.
`silly tarball`
`silly extract`
`silly tarball`
`silly extract`
a few times over and over.
```auto
1853 info lifecycle node-red-contrib-ui-time-scheduler@0.4.8~postuninstall: node-red-contrib-ui-time-scheduler@0.4.8
1854 timing action:unbuild Completed in 18ms
1855 silly doSerial remove 1210
1856 silly remove /home/pi/.node-red/node_modules/node-red-contrib-ui-time-scheduler
1857 timing action:remove Completed in 58ms
1858 silly doSerial move 1210
1859 silly doSerial finalize 1210
```
`doSerial`!!!!????
`silly finalise`
`silly refresh-package-json`
It goes on for about 3259 lines.
What gremlin have I released?
Ok, at the bottom of the file:
```auto
3252 verbose argv "/usr/bin/node" "/usr/bin/npm" "install" "--no-audit" "--no-update-notifier" "--no-fund" "--save" "--save-prefix=~" "--production" "node-red-contrib-ui-time-scheduler@1.11.0"
3253 verbose node v12.22.1
3254 verbose npm v6.14.12
3255 error code ELIFECYCLE
3256 error errno 1
3257 error serialport@6.2.2 install: `prebuild-install || node-gyp rebuild`
3257 error Exit status 1
3258 error Failed at the serialport@6.2.2 install script.
3258 error This is probably not a problem with npm. There is likely additional logging output above.
3259 verbose exit [1, true]
```
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [25 June 2021 00:57 UTC](https://discourse.nodered.org/t/this-cant-be-good-updating-nodes/47610/2 "2021-06-25T00:57:48Z")
Oh and something else I just saw on a page:
```auto
2021-06-25T00:36:59.068Z [err] 1
2021-06-25T00:36:59.107Z [err] npm
2021-06-25T00:36:59.107Z [err] ERR! serialport@6.2.2 install: `prebuild-install || node-gyp rebuild`
2021-06-25T00:36:59.107Z [err] npm ERR!
2021-06-25T00:36:59.108Z [err] Exit status 1
2021-06-25T00:36:59.108Z [err] npm
2021-06-25T00:36:59.108Z [err] ERR!
2021-06-25T00:36:59.108Z [err]
2021-06-25T00:36:59.108Z [err] npm
2021-06-25T00:36:59.108Z [err] ERR!
2021-06-25T00:36:59.108Z [err] Failed at the serialport@6.2.2 install script.
2021-06-25T00:36:59.108Z [err] npm
2021-06-25T00:36:59.109Z [err] ERR! This is probably not a problem with npm. There is likely additional logging output above.
2021-06-25T00:36:59.270Z [err]
2021-06-25T00:36:59.270Z [err] npm ERR!
2021-06-25T00:36:59.270Z [err] A complete log of this run can be found in:
2021-06-25T00:36:59.270Z [err] npm ERR!
2021-06-25T00:36:59.271Z [err] /home/pi/.npm/_logs/2021-06-25T00_36_59_226Z-debug.log
2021-06-25T00:36:59.314Z rc=1
```
# serialport@6.2.2
AFAIK I have removed it because it was causing problems when installed.
I didn't think it would cause problems when NOT installed too!
Oh and P.S
NR 1.3.5
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [25 June 2021 01:28 UTC](https://discourse.nodered.org/t/this-cant-be-good-updating-nodes/47610/3 "2021-06-25T01:28:22Z")
(The log file is too big to attach)
This is a link to it.
[This is the npm log file](https://anonfiles.com/H5tdX924u5/2021-06-25T00_36_59_226Z-debug_log)
There are two - I was updating a few nodes.
Both about the same size. (BIG) 😉
For now this is the first one.
---
### Author:  [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [25 June 2021 07:43 UTC](https://discourse.nodered.org/t/this-cant-be-good-updating-nodes/47610/4 "2021-06-25T07:43:14Z")
Well if it's still compiling t then it is still installed... maybe go into your `~/.node-red` directory and manually uninstall - `npm uninstall node-red-node-serialport serialport`
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [25 June 2021 07:46 UTC](https://discourse.nodered.org/t/this-cant-be-good-updating-nodes/47610/5 "2021-06-25T07:46:14Z")
Thanks.
Doing it now.
But just to show, this is a screen shot of the `modules` directory on said machine.
No sign of any `serial` anything.
This is what happens/d:
```auto
pi@BedPi:~/.node-red/node_modules $ cd ..
pi@BedPi:~/.node-red $ npm uninstall node-red-node-serialport serialport
npm WARN ts-lib-utils@2.2.0 requires a peer of typescript@2 || 3 but none is installed. You must install peer dependencies yourself.
npm WARN tsutils@3.17.1 requires a peer of typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none is installed. You must install peer dependencies yourself.
npm WARN type-coverage-core@2.4.1 requires a peer of typescript@2 || 3 but none is installed. You must install peer dependencies yourself.
npm WARN node-red-project@0.0.1 No repository field.
npm WARN node-red-project@0.0.1 No license field.
removed 23 packages, updated 1 package and audited 335 packages in 28.003s
8 packages are looking for funding
run `npm fund` for details
found 22 vulnerabilities (4 low, 8 moderate, 8 high, 2 critical)
run `npm audit fix` to fix them, or `npm audit` for details
pi@BedPi:~/.node-red $
```
It said a lot of nodes were removed. 23 of them as it says.
`node-red-ui_led` (correct spelling?) was mentioned.
What gives?
---
### Author:  [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [25 June 2021 08:14 UTC](https://discourse.nodered.org/t/this-cant-be-good-updating-nodes/47610/6 "2021-06-25T08:14:31Z")
After all that I can now upgrade other nodes.
Not 100% sure if the command @dceejay said was **the** problem.
But it did help.
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [9 July 2021 08:15 UTC](https://discourse.nodered.org/t/this-cant-be-good-updating-nodes/47610/7 "2021-07-09T08:15:04Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.