Hi All,
has any body has an issues with the av/ spam graph stopped in admin console
it was workin' fine for a couple of days after the initial install, and then stopped. The logger is
running.
i updated:
Kill percent: 66
Tag percent: 20
because the spam volume was so large the spam filter is working well:)
but no graph
thanks for any replies
av/ spam graph stopped in admin console
av/ spam graph stopped in admin console
By stopped do you mean that the service stopped, or that the graphs stopped,
ergo-is the service running?
ergo-is the service running?
av/ spam graph stopped in admin console
Hi, The logger service is running ( it did stop at one stage due to the 2.30am issue see:
http://www.zimbra.com/forums/showthread ... 569&page=2)
and all other graphs are fine apart from the as/av which seems to be updating with blank data?
http://www.zimbra.com/forums/showthread ... 569&page=2)
and all other graphs are fine apart from the as/av which seems to be updating with blank data?
av/ spam graph stopped in admin console
Hi, I have the same issue where all the services are running, and spam and av is working fine, but the graphs in the admin interface show no data after about a month of use.
Anyone know where to start looking for the cause of this problem?
Cheers.
Anyone know where to start looking for the cause of this problem?
Cheers.
av/ spam graph stopped in admin console
take a look at the logger db file
/opt/zimbra/logger/db/data/hostname.err
/opt/zimbra/logger/db/data/hostname.err
av/ spam graph stopped in admin console
Thanks.. after a bit of poking and proding i discovered I had a corrupt table in zimbra_logger.
After running the following command it started to work again.
/opt/zimbra/logger/mysql/bin/mysqlcheck --socket=/opt/zimbra/logger/db/mysql.sock -p -uroot zimbra_logger --repair
You can get the root mysql password for the logger using this command:
zmlocalconfig -s | grep mysql_logger
After running the following command it started to work again.
/opt/zimbra/logger/mysql/bin/mysqlcheck --socket=/opt/zimbra/logger/db/mysql.sock -p -uroot zimbra_logger --repair
You can get the root mysql password for the logger using this command:
zmlocalconfig -s | grep mysql_logger
av/ spam graph stopped in admin console
Im now not sure this was my only problem.
After re enabling a filter in the postfix master.cf, the logs stopped working again.
If i have:
465 inet n - n - - smtpd
-o smtpd_tls_wrappermode=yes -o smtpd_sasl_auth_enable=yes
-o content_filter=dfilt:
the AV/AS graphs stop working.. they display, but no data.
If i remove the -o content_filter=dfilt: it starts working again.
"dfilt" just adds a Privacy Statement to the end of outgoing emails.
Any ideas why it stops it working?
Thanks.
After re enabling a filter in the postfix master.cf, the logs stopped working again.
If i have:
465 inet n - n - - smtpd
-o smtpd_tls_wrappermode=yes -o smtpd_sasl_auth_enable=yes
-o content_filter=dfilt:
the AV/AS graphs stop working.. they display, but no data.
If i remove the -o content_filter=dfilt: it starts working again.
"dfilt" just adds a Privacy Statement to the end of outgoing emails.
Any ideas why it stops it working?
Thanks.
av/ spam graph stopped in admin console
OK, I found the cause of my problem.
Altering master.cf was a bad move. I found I can only have 1 content filter per server. When i removed the last content_filter=dfilt i noticed the zimbra config setting returned. content_filter=smtp-amavis:[127.0.0.1]:10024
The graphs now work.
Altering master.cf was a bad move. I found I can only have 1 content filter per server. When i removed the last content_filter=dfilt i noticed the zimbra config setting returned. content_filter=smtp-amavis:[127.0.0.1]:10024
The graphs now work.
av/ spam graph stopped in admin console
I had this problem too. The error I get from the logprocess.out is
Table './zimbra_logger/mta' is marked as crashed and last (automatic?) repair failed
I repair the table it it works again. For a while at least. It seems like everytime the database stops and starts that table needs to be repaired again.
Anyone know why?
I could start a new thread if this isnt related
Table './zimbra_logger/mta' is marked as crashed and last (automatic?) repair failed
I repair the table it it works again. For a while at least. It seems like everytime the database stops and starts that table needs to be repaired again.
Anyone know why?
I could start a new thread if this isnt related