Cannot update from Appstore

[Lazzz]

Just recently I have been unable to install any updates or new apps from the Appstore - Always get the Failed message. 

It shows that it's installing, like usual, but then shows it "Failed".

Anyone else??

The only thing I've done different is to not install any updates since the bad one a while back where everything crashed. Could this, possibly, have anything to do with it??

[SoakinJoe]

Just recently I have been unable to install any updates or new apps from the Appstore - Always get the Failed message. 

It shows that it's installing, like usual, but then shows it "Failed".

Anyone else??

The only thing I've done different is to not install any updates since the bad one a while back where everything crashed. Could this, possibly, have anything to do with it??

I also get the same issue, same here with not installing anything since the last bad crash. Although I then did update and I still get the same "failed" error. 

I posted elsewhere in the forum (how do I do it) and have had no replies, I see from your thread that you have had no feedback either......

Fully updated RPi OS, OP S/W updated, OP installer 4.2.2 and Signal K 2.13.5 version

[Lazzz]

I couldn't be sure but there may be a limit to the number of Apps you can have!!
I deleted a couple & then it was all back to normal.

[PaddyB]

Anything in the server log?

[SoakinJoe]

Anything in the server log?

This is what I just pulled off:

May 25 08:24:36 TcpProvider:connect EHOSTUNREACH 192.168.1.166:10110
May 25 08:24:44 TcpProvider:connect EHOSTUNREACH 192.168.1.166:10110
May 25 08:24:52 TcpProvider:connect EHOSTUNREACH 192.168.1.166:10110
May 25 08:25:00 stderr: npm WARN deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
May 25 08:25:00 stderr: npm
May 25 08:25:00 stderr: WARN deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs
May 25 08:25:00 stderr: npm WARN deprecated npmlog@5.0.1: This package is no longer supported.
May 25 08:25:00 TcpProvider:connect EHOSTUNREACH 192.168.1.166:10110
May 25 08:25:00 stderr: npm
May 25 08:25:00 stderr: WARN deprecated npmlog@6.0.2: This package is no longer supported.
May 25 08:25:00 stderr: npm
May 25 08:25:00 stderr: WARN deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
May 25 08:25:00 stderr: npm WARN deprecated are-we-there-yet@2.0.0: This package is no longer supported.
May 25 08:25:00 stderr: npm WARN deprecated are-we-there-yet@3.0.1: This package is no longer supported.
May 25 08:25:00 stderr: npm WARN deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
May 25 08:25:00 stderr: npm WARN
May 25 08:25:00 stderr: deprecated multer@1.4.5-lts.1: Multer 1.x is impacted by a number of vulnerabilities, which have been patched in 2.x. You should upgrade to the latest 2.x version.
May 25 08:25:00 stderr: npm
May 25 08:25:00 stderr: WARN deprecated abstract-socket@2.1.1: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
May 25 08:25:00 stderr: npm WARN deprecated signalk-to-nfl@0.1.5: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
May 25 08:25:00 stderr: npm WARN deprecated gauge@3.0.2: This package is no longer supported.
May 25 08:25:01 stderr: npm WARN deprecated
May 25 08:25:01 stderr: boolean@3.2.0: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
May 25 08:25:01 stderr: npm
May 25 08:25:01 stderr: WARN
May 25 08:25:01 stderr: deprecated gauge@4.0.4: This package is no longer supported.
May 25 08:25:01 stderr: npm
May 25 08:25:01 stderr: WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
May 25 08:25:08 TcpProvider:connect EHOSTUNREACH 192.168.1.166:10110
May 25 08:25:16 TcpProvider:connect EHOSTUNREACH 192.168.1.166:10110
May 25 08:25:24 TcpProvider:connect EHOSTUNREACH 192.168.1.166:10110

I read the Signal FAQs that was suggested by someone else, but I am not too technical and I do not want to mess up my system that I am depending on.

If someone could kindly help it would be appreciated.

[SoakinJoe]

I got time to look at this again. I tried deleting apps from signal k but I am getting the same "failed" error. I'll try reinstalling signal k as per the FAQ and update my status.

[PaddyB]

Signalk discord server would be a better place to ask, sorry don't know enough to be much help looking at the log. This looks a bit odd though..
TcpProvider:connect EHOSTUNREACH 192.168.1.166:10110

[aywwa]

I know this is a bit old but I had the same problem and this  fixed it. I don't have WiFi, only distant and fragile iPhone cellular, so updating signalk apps had crashed downloading. As you can see from earlier posts, that seems to be the common issue. This script helped by clearing out the debris from node_modules, purging the npm cache and clearing package-lock.json to reset dependency locks. I know its very basic, but that is my level. Ive posted it because no one else has posted a solution.

#!/bin/bash 
SIGNALK_DIR="$HOME/.signalk"
echo "Navigating to $SIGNALK_DIR" 
cd "$SIGNALK_DIR" || { echo "Could not enter $SIGNALK_DIR"; exit 1; }
echo "Removing node_modules directory..." 
rm -rf "$SIGNALK_DIR/node_modules" 
echo "Removing package-lock.json if it exists..." 
rm -f "$SIGNALK_DIR/package-lock.json" 
echo "Flushing npm cache..." 
npm cache clean --force 
echo "Cleanup complete. You can now retry your plugin install." 

Hopefully someone much more experienced can veto it or comment if it isnt something you should do, but it fixed my system, it has loaded signalk apps without difficulty since, and hasn't crashed  anything else.

[aywwa]

Perhaps do not do this. It worked on the corrupted system on my boat but on another system with wifi does what the script said it would do and wiped off most of the signalk apps. It was easy to return what I needed from a backup, and re install, and runs ok after that, but there are probably better ways.

[JeniferD03]

That script is a really good idea for clearing out the corrupted files from a failed update! Even with the warning in the next post, it's a solid diagnostic step for when nothing else works.