Zimbra: Disk /var/lib/snapd/snap/core/… at 100% on mail.example.com

Zimbra: Disk /var/lib/snapd/snap/core/… at 100% on mail.example.com

When you have Snap installed on Zimbra instance (while installing Certbot) you may get tons of e-mail from Zimbra monitoring tools with warnings saying:

Mar  9 23:40:24 mail zimbramon[689]: 689:crit: Disk warning: mail.example.com: /var/lib/snapd/snap/snap/1042 on device /dev/loop4 at 100% 

This is normal, since all /dev/loopX are read-only and automatically created by Snap. You may see them by executing df -h:

[root@mail ~]# df -h
Filesystem                    Size  Used Avail Use% Mounted on
devtmpfs                      1.9G     0  1.9G   0% /dev
tmpfs                         1.9G     0  1.9G   0% /dev/shm
tmpfs                         1.9G  215M  1.7G  12% /run
tmpfs                         1.9G     0  1.9G   0% /sys/fs/cgroup
/dev/mapper/centos_mail-root   96G   22G   75G  23% /
/dev/sda1                    1014M  193M  822M  19% /boot
tmpfs                         379M     0  379M   0% /run/user/0
/dev/loop1                     62M   62M     0 100% /var/lib/snapd/snap/core20/904
/dev/loop5                     50M   50M     0 100% /var/lib/snapd/snap/certbot/952
/dev/loop2                     99M   99M     0 100% /var/lib/snapd/snap/core/10823
/dev/loop0                    100M  100M     0 100% /var/lib/snapd/snap/core/10859
/dev/loop4                     50M   50M     0 100% /var/lib/snapd/snap/certbot/1042

You may want to exclude these devices from Zimbra’s monitoring by executing zmlocalconfig -e zmstat_df_excludes=’/dev/loop0:/dev/loop1:/dev/loop2:/dev/loop3:/dev/loop4:/dev/loop5:/dev/loopX’ as Zimbra user:

[root@mail ~]# su – zimbra
[zimbra@mail ~]$ zmlocalconfig -e zmstat_df_excludes=’/dev/loop0:/dev/loop1:/dev/loop2:/dev/loop3:/dev/loop4:/dev/loop5’
[zimbra@mail ~]$ zmstatctl restart

답글 남기기

이메일 주소는 공개되지 않습니다. 필수 필드는 *로 표시됩니다