Closed gogglespisano closed 2 months ago
can you please paste your "df -h" output and also are you using sysadmin module?
It's the letsencrypt snap certbot using the /dev/loopX devices. The certbot (may/probably) was on the Debian before installing FreePBX Beta, as it had several base features already installed.
Filesystem Size Used Avail Use% Mounted on
udev 2.4G 0 2.4G 0% /dev
tmpfs 492M 888K 491M 1% /run
/dev/sda1 62G 18G 41G 31% /
tmpfs 2.5G 216K 2.5G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/loop0 46M 46M 0 100% /snap/certbot/3700
/dev/loop4 64M 64M 0 100% /snap/core20/2264
/dev/loop1 45M 45M 0 100% /snap/certbot/3834
/dev/loop2 106M 106M 0 100% /snap/core/16574
/dev/loop3 104M 104M 0 100% /snap/core/16928
/dev/loop5 64M 64M 0 100% /snap/core20/2318
tmpfs 492M 52K 492M 1% /run/user/114
tmpfs 492M 44K 492M 1% /run/user/0
please update to the latest sysadmin and framework where we have added configuration option to choose the drive to get the storage notification alert.
FreePBX Version
FreePBX 17
Issue Description
In the Debian install, the devices /dev/loopX are always going to be 100% full.
FrePBX sends an alert email every hour saying they are full.
These devices should be ignored when checking for storage space alerts.
Operating Environment
Relevant log output