Server Status

Hi Bill

I checked as suggested and everything is zimbra:zimbra including the containing folder so that bug is resolved.

Regards
Simon

can you please check if the zimbraLogHostname is set correct and run the binary as root

/opt/zimbra/libexec/zmsyslogsetup

it does the trick for me.

Hi

So the hostname appears to be correct but I think we might be getting somewhere. After I ran zmsyslogsetup I went to look in the /etc/rsyslog.conf file and saw this near the bottom:

daemon.*;mail.*;\
news.err;\
*.=debug;*.=info;\
*.=notice;*.=warn |/dev/xconsole
local0.* @mailsuth.saao.ac.za
local1.* @mailsuth.saao.ac.za
auth.* @mailsuth.saao.ac.za
local0.* -/var/log/zimbra.log
local1.* -/var/log/zimbra-stats.log
auth.* -/var/log/zimbra.log
mail.* @mailsuth.saao.ac.za
mail.* -/var/log/zimbra.log

We have 2 servers - one mailcape and the other mailsuth. Mailsuth has working stats. Mailcape does not. And now I see mailcape is not included in this config file.

So now to figure out why.

S

Quote:

---

Originally Posted by simonfishley

We have 2 servers - one mailcape and the other mailsuth. Mailsuth has working stats. Mailcape does not. And now I see mailcape is not included in this config file.

S

---

Which server has the logger service running? Set the zimbraLogHostname to the hostname of the logger server in both the servers, then run the binary again.

Hi again

Well in actual fact we have logger running on both servers. Could that possibly be the problem? Do we not need logger on both servers?

S

Have the same thing on a single server
logdirectory is zimbra:zimbra
also executed zmsyslogsetup as root no change

the status is fine after a reboot but after a while its stuck on not running

Quote:

---

Originally Posted by simonfishley

Hi again

Well in actual fact we have logger running on both servers. Could that possibly be the problem? Do we not need logger on both servers?

S

---

That would do it; Zimbra logger should be running on only one host, and that host's syslog daemon should be configured to accept syslog connections from others.

In turn, the remaining servers should be forwarding their data to the syslog (Zimbra logger) server.

On our SLES boxes, we add the following to /etc/syslog-ng/syslog-ng.conf at the bottom. I'll let you sort out from which server this came... :-)

Code:

---

# Begin Zimbra Syslog Section
#
# Line below commented out as it doesn't work; use SUSE's already-defined above source (src) instead.
#source zimbra_src { internal(); unix-stream("/dev/log" keep-alive(yes) max-connections(20)); }; # zimbra
# Next four lines mandatory for all Zimbra servers.
filter zimbra_local0 { facility(local0); }; # zimbra
filter zimbra_local1 { facility(local1); }; # zimbra
filter zimbra_auth { facility(auth); }; # zimbra
filter zimbra_mail { facility(mail); }; # zimbra
# Next four lines used on remote hosts; comment out on the logger server.
#destination zimbra_mail { udp("172.16.1.22" port(514) ); }; # zimbra
#destination zimbra_local1 { udp("172.16.1.22" port(514) ); }; # zimbra
#destination zimbra_local0 { udp("172.16.1.22" port(514) ); }; # zimbra
#destination zimbra_auth { udp("172.16.1.22" port(514) ); }; # zimbra
# Next four lines used only on the logger host; comment out on remote hosts.
destination zimbra_mail { file("/var/log/zimbra.log" owner("zimbra")); }; # zimbra
destination zimbra_local1 { file("/var/log/zimbra-stats.log" owner("zimbra")); }; # zimbra
destination zimbra_local0 { file("/var/log/zimbra.log" owner("zimbra")); }; # zimbra
destination zimbra_auth { file("/var/log/zimbra.log" owner("zimbra")); }; # zimbra
# Next four lines mandatory for all Zimbra servers.
log { source(src); filter(zimbra_mail); destination(zimbra_mail); }; # zimbra
log { source(src); filter(zimbra_local0); destination(zimbra_local0); }; # zimbra
log { source(src); filter(zimbra_local1); destination(zimbra_local1); }; # zimbra
log { source(src); filter(zimbra_auth); destination(zimbra_auth); }; # zimbra
# End Zimbra Syslog Section

---

Hope that helps,
Mark