snapd storehelpers.go:413: cannot refresh:

Toadman · 06-14-2018, 09:25 AM

This error when automatically or manually refreshing snaps on my 16.04.4 LTS system seems to have started after the update to snapd 2.32.9.

Code:

apt-cache policy snapd
snapd:
  Installed: 2.32.9
  Candidate: 2.32.9

The complete refresh entries look like this:

Code:

Jun 14 00:22:34 localhost snapd[1112]: 2018/06/14 00:22:34.033377 storehelpers.go:413: cannot refresh:
Jun 14 00:22:34 localhost snapd[1112]: snap "nethack": snap has no updates available
Jun 14 00:22:34 localhost snapd[1112]: snap "snapweb": snap has no updates available
Jun 14 00:22:34 localhost snapd[1112]: snap "pubip": snap has no updates available
Jun 14 00:22:34 localhost snapd[1112]: snap "hello-world": snap has no updates available
Jun 14 00:22:34 localhost snapd[1112]: snap "core": snap has no updates available
Jun 14 00:22:34 localhost snapd[1112]: snap "wallpaperdownloader": snap has no updates available
Jun 14 00:22:34 localhost snapd[1112]: snap "speed-test": snap has no updates available
Jun 14 00:22:34 localhost snapd[1112]: snap "dwarf-fortress": snap has no updates available
Jun 14 00:22:34 localhost snapd[1112]: snap "snappy-debug": snap has no updates available

Here's snap version output

Code:

snap version
snap    2.33
snapd   2.33
series  16
ubuntu  16.04
kernel  4.13.0-45-generic

I've asked on the 'snapcraft.io' list over a week ago and haven't gotten any kind of response to this. Anyone have an idea as to what's going on? This is still going on after a reboot.

hydrurga · 06-15-2018, 07:11 PM

Have a look to see if the solution offered here is of any use:

https://askubuntu.com/questions/1042...h-erro/1042682

Toadman · 06-16-2018, 08:11 AM

Thanks, the link you referenced was a question I submitted.

Code:

systemctl status snapd.seeded.service
● snapd.seeded.service - Wait until snapd is fully seeded
   Loaded: loaded (/lib/systemd/system/snapd.seeded.service; enabled; vendor preset: enabled)
   Active: active (exited) since Sat 2018-06-16 07:48:35 CDT; 14min ago
  Process: 1362 ExecStart=/usr/bin/snap wait system seed.loaded (code=exited, status=0/SUCCESS)
 Main PID: 1362 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/snapd.seeded.service

Jun 16 07:48:35 localhost systemd[1]: Starting Wait until snapd is fully seeded...
Jun 16 07:48:35 localhost systemd[1]: Started Wait until snapd is fully seeded.

I also noticed this a bit ago in my syslog:

Code:

Jun 16 07:58:54 localhost snapd[1055]: 2018/06/16 07:58:54.812010 autorefresh.go:388: auto-refresh: all snaps are up-to-date
Jun 16 07:59:38 localhost snapd[1055]: 2018/06/16 07:59:38 Unsolicited response received on idle HTTP channel starting with "HTTP/1.0 408 Request Time-out\r\nCache-Control: no-cache\r\nConnection: close\r\nContent-Type: text/html\r\n\r\n<html><body><h1>408 Request Time-out</h1>\nYour browser didn't send a complete request in time.\n</body></html>\n"; err=<nil>

After going through the steps again that were referenced in the reply to me I still see

Code:

snapd[1055]: 2018/06/16 08:00:36.060035 storehelpers.go:413: cannot refresh:

ondoho · 06-17-2018, 01:17 AM

https://www.startpage.com/do/dsearch...cannot+refresh
the first two results seem to be yours, but the third (reddit) has some fresh info:
https://www.reddit.com/r/SolusProjec...running_snaps/

Toadman · 06-17-2018, 04:23 PM

Thanks for the link, it's somewhat like my issue. I set up an account there and asked in the Ubuntu forum. At the moment I'm not even sure what 'storehelpers.go' is or it's purpose. Google leads me to believe it's part of snap core.