kopano-monitor doesn't seem to be doing anything.

tiredofit

I’m running through some tests to understand how all the KC components are working and have now reached the point of looking at kopano-monitor.

I have a user which I have set a very low quota for and was expecting to get a notification from kopano-monitor at least once to show that I was going over the limit.

When I look at the logs (either sending to a file, or console) the only output is:

[=======] Starting kopano-monitor version 10.0.6 (pid 25946 uid 0)
[=======] Starting kopano-monitor version 10.0.6 (pid 25946 uid 998)

My configuration file looks like so:

server_socket = https://server:237
sslkey_file = /certs/core/monitor.pem
coredump_enabled = no
log_level = 6
log_file = /logs/kopano/monitor.log
log_timestamp = yes
quota_check_interval = 15
mailquota_resend_interval = 1
userquota_warning_template = /data/templates/quotas/companywarning.mail
companyquota_warning_template = /data/templates/quotas/companywarning.mail

I have also tried using a socket instead of the TCP connection with no success.

I’m using KC compiled from master branch within the past 3 days.

tiredofit

Can someone provide me with some sample logs to what Kopano Monitor usually outputs? I am still seeing this issue with kopano-monitor not doing anything with mailboxes that are over quota.

jacsa

@tiredofit Hello, I have the same problem with KC 11.0.2 : it runs, but nothing in the log, it doesn’t send out quota warning e-mails. Did you find any solution? Thanks.

tiredofit

@jacsa I did not find the solution after many installations and attempts.
I had someone write a bash script that does the same thing, yet allows for excluding some users, and sends a report to an administrator daily.

jacsa

@tiredofit Yes I I’ll do the same. Thank you for the answer.

Solidus

@tiredofit Hi! Thanks for reporting this issue. I am currently investigating it and will update when I have news

Solidus

@tiredofit Hello!

I have found the issue and fixed it. It has just been merged to master and also backported to older versions. You should now get proper logging and also get the right warnings when the set limits are passed. Please let me know if something else is still not working for you.