Admin console server status page show stopped services

[greggy]

About hostname
------------------

Before setup ZCS I configure my zone(somehostname.org) on bind DNS server, all installer check's passed well. Trough install time hostname didn't change, zimbra daemons(slapd, postfix, etc) uses somehostname.org to bind and it works well.

# su - zimbra -c "zmprov gcf zimbraLogHostname"
zimbraLogHostname: somehostname.org
# nslookup somehostname.org
Server: 10.0.7.44
Address: 10.0.7.44#53

Name: somehostname.org
Address: 10.0.7.55

# ping -c 1 somehostname.org
PING somehostname.org (10.0.7.55) 56(84) bytes of data.
64 bytes from somehostname.org (10.0.7.55): icmp_seq=1 ttl=64 time=0.017 ms

--- somehostname.org ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.017/0.017/0.017/0.000 ms

# ip a show eth0
2: eth0: mtu 1500 qdisc pfifo_fast qlen 100
link/ether 55:55:55:55:55:55 brd ff:ff:ff:ff:ff:ff
inet 10.0.7.55/8 brd 10.255.255.255 scope global eth0
inet6 fe80::6ab5:99ff:fec9:20be/64 scope link
valid_lft forever preferred_lft forever

# zmprov mcf zimbraLogHostname somehostname.org
Doesn't help.

But zimbra parse logfiles with perl:

# lsof /var/log/zimbra*
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
perl 12341 zimbra 3r REG 104,5 15793676 130632 /var/log/zimbra-stats.log
perl 13026 zimbra 3r REG 104,5 58044 130670 /var/log/zimbra.log

# ps aux | grep -E "12341|13026" | grep -v grep
zimbra 12341 0.0 0.1 42856 10956 ? Ss 11:01 0:00 /opt/zimbra/libexec/logswatch --config-file=/opt/zimbra/conf/logswatchrc --use-cpan-file-tail --pid-file=/opt/zimbra/log/logswatch.pid --daemon --script-dir=/opt/zimbra/data/tmp -t /var/log/zimbra-stats.log
zimbra 13026 0.0 0.1 42856 11748 ? S 11:01 0:00 /usr/bin/perl /opt/zimbra/data/tmp/.swatch_script.12994

About /opt/zimbra/libexec/zmsyslogsetup
----------------------------------------------
Already used and that script changed my /etc/syslog-ng/syslog-ng.conf after what /var/log/zimbra-stats.log /var/log/zimbra.log files appeared and syslog-ng writes msg from zimbra to it.

Any ideas?

[lmerrill]

Hi all,

I am experiencing the same problem as most of the other people in this thread -- when I go to the Zimbra Web Administration Console all of the items on the "Server Status" page have a red X next to them, even though all Zimbra services are running.

I'm running Zimbra 7.0.1 GA open source edition on my CentOS 5.5 dedicated server (I ran --platform-override during installation as I had downloaded the RHEL5 installer). Everything else in Zimbra is running perfectly except this.

i've tried some suggestions found on other threads in this forum, including re-generating SSH keys, deplying the new keys, running zmsyslogsetup, etc. All of those things worked but there has been no change to the "Server Status" page. The "Sever Statistics" page reports an error about being unable to read data from logger.

I've heard about some invalid configuration entries in syslog-ng.conf being the cause of the problem, but I don't have syslog-ng anywhere on my system so can't verify that. I don't know what Zimbra uses for logging on my server, but it's certainly not syslog-ng (although I do have both rsyslog and syslog).

I would really appreciate it if anyone has found a fix for this, or if anyone can provide me with suggestions on how I might be able to fix the problem. It's really annoying seeing all the servers being down when you know they're running smoothly (a "zmcontrol status" as the zimbra user confirms this).

Thanks for any help provided!

[carlswart]

Hi All,

Since there is no CentOS install, I used the --platform-override switch on install.sh with the RHEL5 distro.

It seems somehow the installer detected that I have rsyslog installed and proceeded to configure /etc/rsyslog.conf for me.

To fix, I did:

su - zimbra
zmcontrol stop
exit

vi /etc/syslog

Then I added: (from /etc/rsyslog.conf)

# Zimbra logs
local0.* -/var/log/zimbra.log
local1.* -/var/log/zimbra-stats.log
auth.* -/var/log/zimbra.log
mail.* -/var/log/zimbra.log

service syslog restart

su - zimbra
zmcontrol start
exit

Hope this helps.

[mowglie]

i already have these log entries in my log files & still get the errors/problems/issues posted earlier in this thread.

i also have the same entries but w/ @mail.domain.com instead of the /var/log parts. thats not an issue is it? it was automatically there after install.

[berjos]

We had a simular problem as carlswart, when the server was fresh and did the same as him. Worked as a charm.

Would also advice anyone that are having problems with services showing stopped, and/or logging not happening to see if the "zimbra" file in /var/spool/cron/ exists and that its not empty.

This file was for some reason empty on our server, so ones we restored it from backup services showed as running in admin console and logging/graphs etc worked as normal..

[heiko h.]

Hi,

I had exactly the same problem -> Server status and statistics

[ericortego]

Ran into this with an ldap slave. The issue for me was that the logs were getting to the zmlog server but the entries weren't being picked up by the parser due to a duplicate field not being logged by syslog servers.

The fix for me was to sed out the duplicate entries of the log file every so often.


in my case zcs0 is the host's name and my log entries looked like this:
Aug 18 23:53:34 zcs0 zcs0 zimbramon[5322]: 5322:info: zmstat convertd.csv: timestamp, utime, stime, cputime, rchar, wchar, read_bytes, write_bytes, rss, processes, threads:: 08/18/2011 23:53:34, 0, 0, 0, 0, 0, 0, 0, 10472, 6, 6

So my sed script does: 'sed -i -e 's/zcs0\ zcs0/zcs0/g' /var/log/zimbra-stats.log'

and now my check boxes are no longer red X's

[rojoblandino]

Same problem but i solved it:

1) I am using debian lenny using following zimbra version: Release 7.1.1_GA_3196.DEBIAN5 DEBIAN5 FOSS edition.
2) After moving to another clean server installation, averything work fine but gui admin status all green stop buttons.
3) I followed the /opt/zimbra/libexec/zmsyslogsetup procedure
4) I followed the /opt/zimbra/libexec/zmfixperms procedure

Then nothing happened, but then i got an idea like a light and i did following check:

5) ls -l /var/spool/cron/crontabs/
founding something like this:
-rw------- 1 10254 crontab 3151 ago 27 03:17 zimbra

6) I doubt about this perms and then i check my old server and found this file under zimbra user authority so i run as root of course:
chown zimbra /var/spool/cron/crontabs/zimbra

7) Then for any doubt i run again the crontab and syslog, i think were not necesary but i did it anyway:
/etc/init.d/cron restart
/etc/init.d/rsyslog restart

Sorry my english is not so good, hope it work for somebody here.

[sjangra]

hey man

run /opt/zimbra/libexec/zmsyslogsetup

[r1fle]

Dear colleagues,

For the new installations please check a sudoers file (run visudo) and change a line:
Defaults requiretty
to
#Defaults requiretty

Hope it helps!

Regards,
Andrey