Running "certbot" failed - cannot find installed snap

Help
1

Heads-up: I'm sure i used the 'standard' process found on many google searches to get my SSL Cert up-and-running on the Raspberry Pi and it's been running fine for a couple of months, however seems like certbot side of things ain't playing the game ! :frowning:

My domain is:rivierafirepits.com

I ran this command: sudo certbot renew --dry-run

It produced this output:
internal error, please report: running "certbot" failed: cannot find installed snap "certbot" at revision 891: missing file /snap/certbot/891/meta/snap.yaml
My web server is (include version):
Apache2
The operating system my web server runs on is (include version):
Debian Buster
My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know):
yes
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
no
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
certbot --version ALSO produces:
internal error, please report: running "certbot" failed: cannot find installed snap "certbot" at revision 891: missing file /snap/certbot/891/meta/snap.yaml

1 Like
2

Welcome to the Let's Encrypt Community, Mark :slightly_smiling_face:

Sorry you're running into this.

@certbot-devs

Any thoughts here?

1 Like
3

Thanks griffin ! I'll keep my fingers crossed ... :slight_smile:

2 Likes
4

You're quite welcome. They're a pretty busy bunch, so it make take a bit to get a response. I appreciate your patience. :slightly_smiling_face:

1 Like
5

Eek. I don't think there's anything wrong with the published armhf snap, but something has gone wrong on your system.

Does the problem persist after a reboot of the Raspberry Pi?

2 Likes
6

@MarkTotnes

Simply for trust purposes to help you move forward, I want to let you know that _az is a certbot developer.

https://community.letsencrypt.org/g/certbot-devs

1 Like
7

Hi _az - Thanks very much for the reply. I have rebooted quite a few times with no luck.

FYI - It appears that the snap in question does not exist in the folder ?! Please see screenshot:

Screenshot

1 Like
8

That directory is supposed to automatically get mounted on boot (or on the installation of a snap) from a (squashfs) image (which you'll find in /var/lib/snapd/snaps/).

If the directory is empty, then something is going wrong with that mounting process.

If it's not being mounted even after a reboot, that's not good either. You might be able to find some useful diagnostic information in:

sudo journalctl -u snapd

Without knowing what's going wrong in snapd I can only suggest trying to re-install the snap:

sudo snap remove certbot
sudo snap install --classic certbot

Out of curiosity, does running this work?

/snap/bin/hello-world
1 Like
9

Hi again az.

The results I get when running /snap/bin/hello-world are as per the screenshot:

Screesnhot

..and sudo journalctl -u snapd

...produces:

Text File

1 Like
10

Oh !

After googling the stuff about missing files, i subsequently ran snap list which produced:

snap list

...obviously (as it states!) 'broken' !

:frowning:

1 Like
11

The problem is:

unknown filesystem type 'squashfs'

This is needed to make things work.

Do you remember what version of Raspbian you downloaded and from where? Raspbian Lite maybe?

1 Like
12

Hi (and thanks for taking the time with this!)

using cat /etc/os-release I get:
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster

1 Like
13

PS - I believe the Raspberry Pi image I started with was using the 'Raspberry Pi Imager' utility...

1 Like
14

Me too, on my Pi 4:

root@pi:~# cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

However, on my device squashfs is available in the provided kernel (so the snap works):

root@pi:~# grep squashfs /proc/filesystems
        squashfs

What kernel are you running?

uname -a
dpkg-query -l raspberrypi-kernel

For me:

root@pi:~# uname -a
Linux pi 5.4.83-v7l+ #1379 SMP Mon Dec 14 13:11:54 GMT 2020 armv7l GNU/Linux

root@pi:~# dpkg-query -l raspberrypi-kernel
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name               Version      Architecture Description
+++-==================-============-============-=================================
ii  raspberrypi-kernel 1.20210108-1 armhf        Raspberry Pi bootloader
1 Like
15

I get:
pi@raspberrypi:~ $ uname -a
Linux raspberrypi 5.4.72-v7l+ #1356 SMP Thu Oct 22 13:57:51 BST 2020 armv7l GNU/Linux
pi@raspberrypi:~ $ dpkg-query -l raspberrypi-kernel
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==================-============-============-===============================
ii raspberrypi-kernel 1.20210108-1 armhf Raspberry Pi bootloader

1 Like
16

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