Configuring-Logger-Host: Difference between revisions
(6.l) |
No edit summary |
||
Line 1: | Line 1: | ||
== Below are the steps to configure logger monitor host in ZCS multi-server setup == | {{WIP}}== Below are the steps to configure logger monitor host in ZCS multi-server setup == | ||
'''Note: run below steps in non-peak hours during scheduled downtime.''' | '''Note: run below steps in non-peak hours during scheduled downtime.''' |
Revision as of 14:33, 30 March 2015
Below are the steps to configure logger monitor host in ZCS multi-server setup
Note: run below steps in non-peak hours during scheduled downtime.
Run on logger monitor Host:
su - zimbra zmcontrol stop ; exit
Run as root user
/opt/zimbra/libexec/zmfixperms -e -v
On the logger monitor host, you must enable syslog to log statistics from remote machines
a. Edit the /etc/sysconfig/syslog file (if using rsyslog, then Edit the /etc/sysconfig/rsyslog file), add -r to the SYSLOGD_OPTIONS setting, SYSLOGD_options=”-r -m 0”
b. /opt/zimbra/libexec/zmsyslogsetup
b. Stop the syslog daemon. Type /etc/init.d/syslogd stop.
c. Start the syslog daemon. Type /etc/init.d/syslogd start.
If You are using rsyslog instead of syslog, then you will need below change in rsyslog config.
we need to enable a module for remote logging in logger host, below changes fixes this issue.
We need to edit the rsyslog config file "/etc/rsyslog.conf" and enable "imudp" module by uncommenting the same.
$ModLoad imudp $UDPServerRun 514
After the above change restart rsyslog service.
su - zimbra zmcontrol start
/opt/zimbra/libexec/zmloggerinit
/opt/zimbra/bin/zmsshkeygen
/opt/zimbra/bin/zmupdateauthkeys
Verify the LogHostname using below commands. (it should be set to name of logger monitor host on all servers)
zmprov gacf |grep zimbraLogHostname
If its different, change the same to logger monitor hostname using below command.
zmprov mcf zimbraLogHostname <Logger monitor Hostname>
On all other servers: (if you have multiple zimbra servers in your setup)
Verify the LogHostname using below commands. (it should be set to name of logger monitor host on all servers)
su - zimbra zmprov gacf |grep zimbraLogHostname
If its different, change the same to Logger monitor Host using below command.
zmprov mcf zimbraLogHostname <Logger monitor Hostname>
/opt/zimbra/bin/zmsshkeygen /opt/zimbra/bin/zmupdateauthkeys ; exit /opt/zimbra/libexec/zmsyslogsetup (run as root user) service syslog restart service rsyslog restart su - zimbra zmcontrol restart
If the above steps didn't help you to resolve the issue, then try deleting old logger host map & create a new logger host map using below script.
/opt/zimbra/bin/zmloggerhostmap -h
Usage: zmloggerhostmap [-adh] <dns_hostname> <zm_hostname>
-a - create a new host mapping -d - delete a host mapping (specify both names to prevent accidents) -h - show this help
Example:
[zimbra@zcs8 ~]$ hostname -f zcs8.zcsvin.com [zimbra@zcs8 ~]$ zmhostname zcs8.zcsvin.com [zimbra@zcs8 ~]$ /opt/zimbra/bin/zmloggerhostmap -a zcs8.zcsvin.com zcs8.zcsvin.com 2>&1 Added mapping for zcs8.zcsvin.com to zcs8.zcsvin.com [zimbra@zcs8 ~]$