Update buffer parser -> fail

I´m using NR 2.0.5 with Node.JS 12.x
today I wanted to update contrib-buffer-parser and contrib-modbus from palette, but an error always occurs:

> 2021-08-19T05:33:08.943Z Installieren : node-red-contrib-buffer-parser 3.1.7
> 2021-08-19T05:33:09.558Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-contrib-buffer-parser@3.1.7
> 2021-08-19T05:33:16.014Z [err] npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!
> 2021-08-19T05:33:22.495Z [err] npm
> 2021-08-19T05:33:22.496Z [err]  ERR! Error while executing:
> 2021-08-19T05:33:22.496Z [err] npm ERR! /usr/bin/git ls-remote -h -t ssh://git@github.com/anerdins/nibepi.git
> 2021-08-19T05:33:22.496Z [err] npm
> 2021-08-19T05:33:22.496Z [err]  ERR! 
> 2021-08-19T05:33:22.496Z [err] npm
> 2021-08-19T05:33:22.496Z [err]  ERR! git@github.com: Permission denied (publickey).
> 2021-08-19T05:33:22.496Z [err] npm ERR! fatal: Konnte nicht vom Remote-Repository lesen.
> 2021-08-19T05:33:22.497Z [err] npm ERR! 
> 2021-08-19T05:33:22.497Z [err] npm ERR!
> 2021-08-19T05:33:22.497Z [err]  Bitte stellen Sie sicher, dass die korrekten Zugriffsberechtigungen bestehen
> 2021-08-19T05:33:22.497Z [err] npm ERR!
> 2021-08-19T05:33:22.497Z [err]  und das Repository existiert.
> 2021-08-19T05:33:22.497Z [err] npm ERR!
> 2021-08-19T05:33:22.497Z [err]  
> 2021-08-19T05:33:22.497Z [err] npm ERR!
> 2021-08-19T05:33:22.497Z [err]  exited with error code: 128
> 2021-08-19T05:33:22.528Z [err] 
> 2021-08-19T05:33:22.528Z [err] npm ERR! A complete log of this run can be found in:
> 2021-08-19T05:33:22.528Z [err] npm ERR!
> 2021-08-19T05:33:22.529Z [err]      /home/pi/.npm/_logs/2021-08-19T05_33_22_510Z-debug.log
> 2021-08-19T05:33:22.551Z rc=1

I need Node.JS 12 for NibePi Node, it doesn´t work with Node.JS 14 or 16.

A quick search of git@github.com: Permission denied (publickey). reveals...

GitHub isn't able to authenticate you. So, either you aren't setup with an SSH key, because you haven't set one up on your machine, or your key isn't associated with your GitHub account.

You can also use the HTTPS URL instead of the SSH/git URL to avoid having to deal with SSH keys. This is GitHub's recommended method.

The error is occurring due to ERR! /usr/bin/git ls-remote -h -t ssh://git@github.com/anerdins/nibepi.git

What does "NibePi Master" have to do with the update of the buffer parser? I do not understand sry.

I think I have to format my micro-SD Card :worried:

It has nothing to do with it - it's because you chose to update buffer-perser.

You will find any npm node you attempt to update, this will happen.

The point is GitHub have changed the way you clone repos. This other node you mention has a dependency to a GitHub resource. It's failing to access it.

See here: node-red-contrib-nibepi/package.json at f903f1a273e2995648a67daa9d5642671843c12d · anerdins/node-red-contrib-nibepi · GitHub

To prove this point, try updating a different node, you will see the same problem.

So even if you reformat and start again you will get this problem when you attempt to install NibePi once more.

1 Like

thank you, but how can I fix it / solve the problem ?

Hello ..

im guessing, because you were experimenting with newer versions of nodejs / npm
at some point your package-lock.json got updated to a newer version.
when you reverted back to nodejs 12 the lock file stayed with v2 causing that error message.

i dont know much about npm but if it was me i would take a chance **
and rename the package-lock.json to package-lock.old and
run npm install from .node-red folder to re-install and recreate it with a correct version.

** dont take my word for it. get a second opinion :wink:

1 Like

I formated my SD-Card, now I can do updates with NibePi installed.
thanks anyway.
I´ll not try Node.JS 14 again :frowning:

Mr. Anerdin doesn´t answere about Node.JS 14, so I have to stay at Node.JS 12.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.