Quote:
Originally Posted by pfnguyen  First, do not run zmlogger from the commandline. if you wish to start and stop logger, you must call zmloggerctl stop/start. killall zmlogger to make sure all processes are stopped from your incorrect invocation (ps ax | grep zmlogger to make sure they are gone).
Secondly, you appear not to receive any data in /var/log/zimbra-stats.log (please verify that your configuration is correct in that syslog data is being sent there [tail /var/log/zimbra-stats.log] anything?)
No data in /var/log/zimbra-stats.log = no data in logger |
I understand.
Actually I came to where to begin my problem.
After these operations (as "root"), statistics earned:
Code:
/etc/init.d/zimbra stop
/opt/zimbra/bin/zmsyslogsetup
/etc/init.d/rsyslog restart
/opt/zimbra/libexec/zmfixperms
/etc/init.d/zimbra start
In the file "/etc/rsyslog.conf", add the following lines:
Code:
daemon.*;mail.*;\
news.err;\
*.=debug;*.=info;\
*.=notice;*.=warn |/dev/xconsole
local0.* -/var/log/zimbra.log
local1.* -/var/log/zimbra-stats.log
auth.* -/var/log/zimbra.log
mail.* -/var/log/zimbra.log
and in the log "/var/log/zimbra-stats.log" began to receive data.
The directory "/opt/zimbra/ logger" AK is beginning to fill with data (before she ever took 44kb).
But the statistics still show stops at exactly 6:24 am Moscow time:
Quote:
Message: system failure: Unable to read logger stats
Error: service.FAILURE Method: GetLoggerStatsRequest
Details: soap: Receive
|
It is not critical, but not pleasant.