zimbramon Disk warning

[sangamc]

Oct 20 06:40:00 zmail zimbramon[25507]: 25507:err: Disk warning: zmail.millennium-mgt.com: / on device /dev/sda5 at 87%
I am getting the above message 20 times in a row several times a day. It is an old error that has since been corrected. But after searching similar posts on the forums i can not find a way to fix it. Most users solved this by upgrading. but i am on the latest version (7.1.3 with CPU spike patch) and even after runing the install again the messages wont stop
What can i do to stop this?
Thanks

If you need any additional information from me, feel free to ask

[FritzBrause]

You can configure Disk Monitoring settings. The default warning level is 85% on each partition. This Wiki article may be helpful: Setting Thresholds for Disk Monitoring - Zimbra :: Wiki
Best regards
Andreas

[sangamc]

Thanks for the reply.
The problem is my disk space issue was resolved already. I had set the backup to create a tar in /tmp instead of /backup/tmp simply deleting the tar file got me back on track
Filesystem Size Used Avail Use% Mounted on

/dev/sda5 8.0G 5.3G 2.4G 69% /

proc 0 0 0 - /proc

sysfs 0 0 0 - /sys

devpts 0 0 0 - /dev/pts

/dev/sda2 95G 60G 30G 67% /opt

/dev/sda1 99M 34M 61M 36% /boot

/dev/sdb1 99G 14G 80G 15% /backup

tmpfs 1.5G 0 1.5G 0% /dev/shm

none 0 0 0 - /proc/sys/fs/binfmt_misc

sunrpc 0 0 0 - /var/lib/nfs/rpc_pipefs
sda5 is only using 69%
but i still get the email messages from the day the actual error occured. (Oct 20th) its almost a month later

[sangamc]

ANy other ideas to solve this issue?

[sangamc]

THe reason i get these messages is because my log were not rotating since the day that the drive got full. I found the problem in /etc/logrotate.d/zimbra inside the file the statement for creating the new log file was wrong ( i think this is caused by partial or bad re-install) it said


create 0644 USER GROUP
it should say
create 0644 zimbra zimbra
once i fixed this i manually ran the log rotate using
logrotate -v /etc/logrotate.conf
the logs all shrank from 4+GB back to normal and i stopped getting the message from 4 months ago that my drive was full.
How do i mark this as solved?

[onur]

THe reason i get these messages is because my log were not rotating since the day that the drive got full. I found the problem in /etc/logrotate.d/zimbra inside the file the statement for creating the new log file was wrong ( i think this is caused by partial or bad re-install) it said


create 0644 USER GROUP
it should say
create 0644 zimbra zimbra
once i fixed this i manually ran the log rotate using
logrotate -v /etc/logrotate.conf
the logs all shrank from 4+GB back to normal and i stopped getting the message from 4 months ago that my drive was full.
How do i mark this as solved?

I got the same storage and annoying & repeating mail , I logged as zimbra user and run the command, I hope it works. I am wondering why zimbra do not check this?
thank you

[marvinfs]

after setting this up
zimbra@mail:~$ zmlocalconfig zmstat_df_excludes
zmstat_df_excludes = /dev/loop0:/dev/loop1:/dev/loop2:/dev/loop3:/dev/loop4:/dev/loop5:/dev/loop6:/dev/loop7:/dev/loop8:/dev/loop9

according to https://wiki.zimbra.com/wiki/Disable_Di ... op_Devices

during restart I'm still getting about 200-600 such messages
9.0 patch 21

2021-12-02_16-44-24.png (42.81 KiB) Viewed 7754 times

any suggestings? snapd is required for other unrelated things...

like maybe exclude squashfs from monitoring somehow?

[L. Mark Stone]

There's a localconfig setting you'll need to set, so like:

Code: Select all

zimbra@my:~$ df -h | grep "Used\|loop"
Filesystem      Size  Used Avail Use% Mounted on
/dev/loop0      100M  100M     0 100% /snap/core/11420
/dev/loop1      100M  100M     0 100% /snap/core/11316
/dev/loop2       11M   11M     0 100% /snap/canonical-livepatch/102
/dev/loop3       11M   11M     0 100% /snap/canonical-livepatch/104
zimbra@my:~$ zmlocalconfig | grep loop
zmstat_df_excludes = /dev/loop0:/dev/loop1:/dev/loop2:/dev/loop3:/dev/loop4:/dev/loop5
zimbra@my:~$ 

After you edit the LC value be sure to do a zmstatctl restart. Ubuntu adds snap disks all the time, so I added a few extra entries so I don't have to worry about getting those errors for a year or so.

Hope that helps,
Mark

[marvinfs]

Dear Mark,

Thank you for prompt reply, that's what I have now:

root@mail:/var/log# su - zimbra
zimbra@mail:~$ zmlocalconfig | grep loop
zmstat_df_excludes = /dev/loop0:/dev/loop1:/dev/loop2:/dev/loop3:/dev/loop4:/dev/loop5:/dev/loop6:/dev/loop7:/dev/loop8:/dev/loop9
zimbra@mail:~$ zmcontrol -v
Release 9.0.0.GA.4178.UBUNTU20.64 UBUNTU20_64 NETWORK edition, Patch 9.0.0_P21.

that doesn't help and obviously I've restarted like 100 times already

[L. Mark Stone]

If you did a zmstatctl restart and you still have the issue, I'd open a Support Case with Zimbra.

Please keep us posted, especially if Zimbra Support reports this as a regression, and/or provides a different solution.

All the best,
Mark