Difference between Quota usage

Max_S

(@max_s)

Joined: 1 year ago

Posts: 81

Topic starter 08/27/2024 10:51

I have the following result from

zextras# zmprov gd domain.name | grep Quota

zimbraAggregateQuotaLastUsage: 27835172232
zimbraDomainAggregateQuota: 10737418240
zimbraDomainAggregateQuotaPolicy: ALLOWSENDRECEIVE
zimbraDomainAggregateQuotaWarnEmailRecipient: xxxxx@domain.name
zimbraDomainAggregateQuotaWarnPercent: 95

But if I add all the quota usage that results from the following command the usage for all accounts together is less then 10G

/opt/zextras/bin/zmprov gqu mail1.myserver.name

Where did the zimbraAggregateQuotaLastUsage: 27835172232 comes from and how to get the correct usage for all accounts

This topic was modified 3 months ago by Max_S

Quote

Md. Shariful Islam

(@sharif)

Admin

Joined: 3 years ago

Posts: 591

08/29/2024 07:31

@max_s

What is your Carbonio CE version ?

As per your shared data,

you domain has 10GB (Max mailbox quota for the mails) which is reflected on zimbraDomainAggregateQuota: 10737418240 per account.

This attribute (zimbraAggregateQuotaLastUsage: 27835172232) is suggesting total use of quota at certain point is 27GB.

It takes time to generate that data. If you see the crontab of zextras user, you will find:

# Invoke "ComputeAggregateQuotaUsageRequest" periodically
#
15 2 * * *      /opt/zextras/libexec/zmcomputequotausage > /dev/null 2>&1
#

you can run it manually, and check the current status of zimbraAggregateQuotaLastUsage:

zextras@mail:~$ /opt/zextras/libexec/zmcomputequotausage

Regards,

Sharif

ReplyQuote

Max_S

(@max_s)

Joined: 1 year ago

Posts: 81

Topic starter 08/30/2024 10:11

@sharif

Thanks, I am running Carbonio CE 24.7.1.

I am looking at the crontab for zextras user and I see several duplicate lines. It looks like at some point, probably during installation on a earlier version the crontabs are written multiple times.

I will have to cleanup some.

I see one part between the

# ZEXTRAS-START and # ZEXTRAS-END

but I see three parts with

# CARBONIO-START and # CARBONIO-END

Can you please advise which part to keep. Is it the "# ZEXTRAS-START and # ZEXTRAS-END" or the "# CARBONIO-START and # CARBONIO-END" ?

THIS is what I have in cron

# ZEXTRAS-START -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZEXTRAS-END
SHELL=/bin/bash
#
# Log pruning
#
30 2 * * * find /opt/zextras/log/ ! -name 'zmsetup*.log' -type f -name '*.log?*' -mtime +8 -exec rm {} \; >/dev/null 2>&1
35 2 * * * find /opt/zextras/log/ -type f -name '*.out.????????????' -mtime +8 -exec rm {} \; >/dev/null 2>&1
#
# compress logs manually to avoid application pauses when
# handled through the log4j thread
#
50 2 * * * /opt/zextras/libexec/zmcompresslogs >/dev/null 2>&1
#
# tmp dir cleaning
#
40 2 * * * /opt/zextras/libexec/zmcleantmp
#
# Stats Cleanup
#
20 2 5 * * /opt/zextras/libexec/zmstat-cleanup >/dev/null 2>&1
#
# Status logging
#
*/2 * * * * /opt/zextras/libexec/zmstatuslog >/dev/null 2>&1
#*/10 * * * * /opt/zextras/libexec/zmdisklog > /dev/null 2>&1
#
# SSL Certificate Expiration Checks
#
0 0 1 * * /opt/zextras/libexec/zmcheckexpiredcerts -days 30 -email
#
#
# crontab.ldap
#
# Monitor MDB database size
*/30 * * * * /opt/zextras/libexec/zmldapmonitordb > /dev/null 2>&1
#
#
# crontab.store
#
# Log pruning
#
30 2 * * * find /opt/zextras/mailboxd/logs/ -type f -name \*log\* -mtime +8 -exec rm {} \; > /dev/null 2>&1
30 2 * * * find /opt/zextras/log/ -type f -name stacktrace.\* -mtime +8 -exec rm {} \; > /dev/null 2>&1
#
# Report on any database inconsistencies
#
0 23 * * 7 /opt/zextras/libexec/zmdbintegrityreport -m
#
# Invoke "ComputeAggregateQuotaUsageRequest" periodically
#
15 2 * * * /opt/zextras/libexec/zmcomputequotausage > /dev/null 2>&1
#
# crontab.mta
#
#
# Queue logging
#
0,10,20,30,40,50 * * * * /opt/zextras/libexec/zmqueuelog
#
# Spam training
#
0 22 * * * /opt/zextras/bin/zmtrainsa >> /opt/zextras/log/spamtrain.log 2>&1
#
# Spam training cleanup
#
45 23 * * * /opt/zextras/bin/zmtrainsa --cleanup >> /opt/zextras/log/spamtrain.log 2>&1
#
# Spam rule updates
#
45 0 * * * . /opt/zextras/.bashrc; /opt/zextras/libexec/zmsaupdate
#
# Spam Bayes auto-expiry
#
20 23 * * * /opt/zextras/common/bin/sa-learn --dbpath /opt/zextras/data/amavisd/.spamassassin --force-expire --sync > /dev/null 2>&1
#
# Clean up amavisd/tmp
#
15 5,20 * * * find /opt/zextras/data/amavisd/tmp -maxdepth 1 -type d -name 'amavis-*' -mtime +1 -exec rm -rf {} \; > /dev/null 2>&1
#
# Clean up the quarantine dir
#
0 1 * * * find /opt/zextras/data/amavisd/quarantine -type f -mtime +7 -exec rm -f {} \; > /dev/null 2>&1
#
#
#
35 3 * * * /opt/zextras/bin/zmcbpadmin --cleanup >/dev/null 2>&1

# ZEXTRAS-END -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZEXTRAS-START
# CARBONIO-START -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND CARBONIO-END
SHELL=/bin/bash
#
# Log pruning
#
30 2 * * * find /opt/zextras/log/ ! -name 'zmsetup*.log' -type f -name '*.log?*' -mtime +8 -exec rm {} \; > /dev/null 2>&1
35 2 * * * find /opt/zextras/log/ -type f -name '*.out.????????????' -mtime +8 -exec rm {} \; > /dev/null 2>&1
#
# compress logs manually to avoid application pauses when
# handled through the log4j thread
#
50 2 * * * /opt/zextras/libexec/zmcompresslogs > /dev/null 2>&1
#
# tmp dir cleaning
#
40 2 * * * /opt/zextras/libexec/zmcleantmp
#
# Stats Cleanup
#
20 2 5 * * /opt/zextras/libexec/zmstat-cleanup > /dev/null 2>&1
#
# Status logging
#
*/2 * * * * /opt/zextras/libexec/zmstatuslog > /dev/null 2>&1
#*/10 * * * * /opt/zextras/libexec/zmdisklog > /dev/null 2>&1
#
# SSL Certificate Expiration Checks
#
0 0 1 * * /opt/zextras/libexec/zmcheckexpiredcerts -days 30 -email
#
#
# crontab.ldap
#
# Monitor MDB database size
*/30 * * * * /opt/zextras/libexec/zmldapmonitordb > /dev/null 2>&1
#
#
# crontab.store
#
# Log pruning
#
30 2 * * * find /opt/zextras/mailboxd/logs/ -type f -name \*log\* -mtime +8 -exec rm {} \; > /dev/null 2>&1
30 2 * * * find /opt/zextras/log/ -type f -name stacktrace.\* -mtime +8 -exec rm {} \; > /dev/null 2>&1
#
# Report on any database inconsistencies
#
0 23 * * 7 /opt/zextras/libexec/zmdbintegrityreport -m
#
# Invoke "ComputeAggregateQuotaUsageRequest" periodically
#
15 2 * * * /opt/zextras/libexec/zmcomputequotausage > /dev/null 2>&1
#
# crontab.mta
#
#
# Queue logging
#
0,10,20,30,40,50 * * * * /opt/zextras/libexec/zmqueuelog
#
# Spam training
#
0 22 * * * /opt/zextras/bin/zmtrainsa >> /opt/zextras/log/spamtrain.log 2>&1
#
# Spam training cleanup
#
45 23 * * * /opt/zextras/bin/zmtrainsa --cleanup >> /opt/zextras/log/spamtrain.log 2>&1
#
# Spam rule updates
#
45 0 * * * . /opt/zextras/.bashrc; /opt/zextras/libexec/zmsaupdate
#
# Spam Bayes auto-expiry
#
20 23 * * * /opt/zextras/common/bin/sa-learn --dbpath /opt/zextras/data/amavisd/.spamassassin --force-expire --sync > /dev/null 2>&1
#
# Clean up amavisd/tmp
#
15 5,20 * * * find /opt/zextras/data/amavisd/tmp -maxdepth 1 -type d -name 'amavis-*' -mtime +1 -exec rm -rf {} \; > /dev/null 2>&1
#
# Clean up the quarantine dir
#
0 1 * * * find /opt/zextras/data/amavisd/quarantine -type f -mtime +7 -exec rm -f {} \; > /dev/null 2>&1
#
#
#
35 3 * * * /opt/zextras/bin/zmcbpadmin --cleanup >/dev/null 2>&1

# ZEXTRAS-END -- DO NOT EDIT ANYTHING BETWEEN THIS LINE AND ZEXTRAS-START

ReplyQuote

Max_S

(@max_s)

Joined: 1 year ago

Posts: 81

Topic starter 08/30/2024 10:39

@sharif

So what I think is because my crontab for user zextras is messed up, process is starting 4 times now at 2:15 and therefore is taking to long and never ends.. ?

What could have happend that messed up the cron ? Same problem I have with the cron for root user.

Is it an option to supply me the correct latest and complet cron for zextras and root user for Carbonio CE 24.7.1 ?

15 2 * * *      /opt/zextras/libexec/zmcomputequotausage > /dev/null 2>&1

This post was modified 3 months ago by Max_S

ReplyQuote

Max_S

(@max_s)

Joined: 1 year ago

Posts: 81

Topic starter 08/30/2024 11:15

@sharif

Sorry I was a bit off topic for the crons. But now with the actual problem.

So I executed

 /opt/zextras/libexec/zmcomputequotausage

For a specific domain it comes with output

So I also run "zmprov gqu $hostname" and when I added all the accounts for that domain I get 13954865538

I noticed the zmcomputequotausage is almost the double of the zmprov gqu output

So I tried it with other domain.

zmcomputequotausage comes with 3940535714

and the outcome of "zmprov gqu $hostname" for all accounts of that domain added together is 1970267857 which is exactly the double.

What am I overlooking ?

ReplyQuote

Md. Shariful Islam

(@sharif)

Admin

Joined: 3 years ago

Posts: 591

09/07/2024 07:39

@max_s

Hi,

I agree with you and I observed the same behavior. I will report it to the devs.

Thanks for your time and contribution.

Regards,

Sharif

ReplyQuote

Max_S

(@max_s)

Joined: 1 year ago

Posts: 81

Topic starter 09/10/2024 12:59

Hi @sharif

Thanks for your help.

Regards,

Max

ReplyQuote

Difference between Quota usage

Super Globals

Options and Features