Snap-store snap: Constant "GrpcError: gRPC Error (code: 14, codeName: UNAVAILABLE" in logs

Support and Help
1

Ubuntu Support Template

Ubuntu Version: 26.04

Desktop Environment (if applicable): Gnome

Problem Description:
when launching snap-store snap im getting connection errors spam like these:

mei 28 19:24:30 r00tb0x snap-store_snap-store.desktop[3514391]: ERROR error_observer: Provider ratingsModelProvider:RatingsModelProvider#afa52(null) failed
mei 28 19:24:30 r00tb0x snap-store_snap-store.desktop[3514391]: GrpcError: gRPC Error (code: 14, codeName: UNAVAILABLE, message: Error connecting: SocketException: Connection refused (OS Error: Connection refused, errno = 111), address = ratings.ubuntu.com, port = 51362, details: null, rawResponse: null, trailers:

i can reprodruce this on every launch of snap-store

Filed the bug downstream + upstream

https://bugs.launchpad.net/snap-store-desktop/+bug/2154497

2

Not sure the team reads the LP bugs, officially you should use:

ogra@styx:~$ snap info --verbose snap-store|grep -A0 issues
  issues:
    - https://github.com/ubuntu/app-center/issues
3

FYI, Lotus also filed upstream at that issues location as well. (So the need to state to send this to upstream is not relevant)

4

Note that as of May 29 you received a response to your bug upstream:

“Seems the rating api is down:”

This endpoint is still down (at least, here at my location) so your issue is ongoing until the ratings API is back up or the Snap Store stops using the ratings endpoint. However, it seems that in your Launchpad bug, others are unable to reproduce this.

Note that because the Snap Store / App Store components are coded to require the ratings API endpoints, you will not be able to really get around this issue if the ratings API is either down or otherwise unreachable at your location (due to any issues that might exist). This isn’t really a bug in the software nor is this an issue in the code, but rather a dependent endpoint not working.

(This is akin to using the Discord snap or Discord client, which has underlying dependence on the Discord API backend endpoints, which if they are not working the Discord client doesn’t work - though that’s a much more clear example of such cases, this is essentially the same kind of issue.)

4 Likes