Quote:
|
Originally Posted by marcmac What do you get from
zmprov gacf | grep -i loghost
Should match the hostname of the server running the logger service.
If the hostname resolves to a public IP on a FW box, can the webmail server access that box at port 7307? (Verify that zmlocalconfig logger_mysql_port matches the port in /opt/zimbra/conf/my.logger.cnf) |
[zimbra@mail ~]$ zmprov gacf | grep -i loghost
zimbraLogHostname: mail.hostager.com
zmlocalconfig shows:
logger_mysql_port = 3307
my.logger.cnf contains:
[mysqld]
basedir = /opt/zimbra/logger/mysql
datadir = /opt/zimbra/logger/db/data
socket = /opt/zimbra/logger/db/mysql.sock
pid-file = /opt/zimbra/logger/db/mysql.pid
bind-address = localhost
port = 7307
skip-external-locking
log-slow-queries = /opt/zimbra/log/logger_myslow.log
long-query-time = 1
log-long-format
log-queries-not-using-indexes
log-bin
thread_cache = 10
max_connections = 10
# We do a lot of writes, query cache turns out to be not useful.
query_cache_type = 0
[mysqld_safe]
err-log = /opt/zimbra/log/logger_mysqld.log
Looks like they do not match. I did the following:
zmlocalconfig -e logger_mysql_port=7307
to fix this and restarted the server. It works now!
Thanks... You guys are great!
- Rob
FYI -- This was an M1 installation upgraded to M2 with the script and then later upgraded to M3. The Server status showed nothing from M1 on. The errors did not display until M3. With your fix the server staus now works properly with no errors.