search

homebridge / homebridge-config-ui-x

The Homebridge UI. Monitor, configure and backup Homebridge from a browser.
https://homebridge.io
MIT License
2.61k stars 373 forks source link

Not Able To Update #2195

Closed mikedbenton closed 4 days ago

mikedbenton commented 4 days ago

Current Situation

I have been running Homebridge for years without issue. I just have a simple install running on Raspberry Pi. As required, I update Homebridge/Homebridge UI/Plug-ins - a very vanilla implementation. Unfortunately, I get an error this time when updating Homebridge.

image

Logs

USER: pi DIR: /var/lib/homebridge CMD: npm install --save homebridge@1.8.4

Config

No response

Homebridge UI Version

4.58

Homebridge Version

1.7.0

Node.js Version

20.17.0

Operating System

Official Homebridge Raspberry Pi Image

Environment Info

None

Raspberry Pi Model

None

NorthernMan54 commented 4 days ago

Looking at the message, try

sudo rm -rf /home/pi/.npm/cacache/content-v2/sha512/35/
mikedbenton commented 4 days ago

Looking at the message, try

sudo rm -rf /home/pi/.npm/cacache/content-v2/sha512/35/

This command completed successfully, but the directory was still there. When I navigated to the 'sha512' directory and ran the same command against the '35' directory, it failed stating there were too many symbolic links.

I was able to remove the directory, and tried the update again. Now I am getting this same error, but with a different directory:

npm error code EEXIST npm error syscall mkdir npm error path /home/pi/.npm/_cacache/content-v2/sha512/05/a7 npm error errno EEXIST npm error Invalid response body while trying to fetch https://registry.npmjs.org/object.assign: ENOENT: no such file or directory, mkdir '/home/pi/.npm/_cacache/content-v2/sha512/05/a7' npm error File exists: /home/pi/.npm/_cacache/content-v2/sha512/05/a7 npm error Remove the existing file and try again, or run npm npm error with --force to overwrite files recklessly. npm error A complete log of this run can be found in: /home/pi/.npm/_logs/2024-09-30T13_02_39_882Z-debug-0.log

bwp91 commented 4 days ago

you could try removing the whole .npm folder

mikedbenton commented 4 days ago

you could try removing the whole .npm folder

Thank you for the help. Not knowing how things work, I'm very timid about removing folders from the system. I will give this a try....

mikedbenton commented 4 days ago

Issue is resolved after removing .npm