Page 1 of 1

Zimbra Administration Server Status all turned red

Posted: Sun Sep 29, 2013 9:06 am
by chengcsw
I have read all posts in the forum but none of them work
Here's what I have checked
The hostname should be correct...
[zimbra@zimbra root]$ zmprov gacf | grep zimbraLogHostname

zimbraLogHostname: zimbra.mydomain.com

To make sure the log is written, I execute it manually
[root@zimbra log]# su zimbra -c /opt/zimbra/libexec/zmstatuslog



The status is written to the log and the format should be correct with rsyslog
[root@zimbra log]# tail zimbra-stats.log | grep STATUS

Sep 29 20:53:19 zimbra zimbramon[8971]: 8971:info: 2013-09-29 20:53:03, STATUS: zimbra.mydomain.com: logger: Running

Sep 29 20:53:19 zimbra zimbramon[8971]: 8971:info: 2013-09-29 20:53:03, STATUS: zimbra.mydomain.com: mailbox: Running

Sep 29 20:53:19 zimbra zimbramon[8971]: 8971:info: 2013-09-29 20:53:03, STATUS: zimbra.mydomain.com: memcached: Running

Sep 29 20:53:19 zimbra zimbramon[8971]: 8971:info: 2013-09-29 20:53:03, STATUS: zimbra.mydomain.com: mta: Running

Sep 29 20:53:19 zimbra zimbramon[8971]: 8971:info: 2013-09-29 20:53:03, STATUS: zimbra.mydomain.com: opendkim: Running

Sep 29 20:53:19 zimbra zimbramon[8971]: 8971:info: 2013-09-29 20:53:03, STATUS: zimbra.mydomain.com: proxy: Running

Sep 29 20:53:19 zimbra zimbramon[8971]: 8971:info: 2013-09-29 20:53:03, STATUS: zimbra.mydomain.com: snmp: Running

Sep 29 20:53:19 zimbra zimbramon[8971]: 8971:info: 2013-09-29 20:53:03, STATUS: zimbra.mydomain.com: spell: Running

Sep 29 20:53:19 zimbra zimbramon[8971]: 8971:info: 2013-09-29 20:53:03, STATUS: zimbra.mydomain.com: stats: Running

Sep 29 20:53:19 zimbra zimbramon[8971]: 8971:info: 2013-09-29 20:53:03, STATUS: zimbra.mydomain.com: zmconfigd: Running



Make sure logswatch is running
[zimbra@zimbra root]$ /opt/zimbra/libexec/zmloggerinit

cp: cannot stat `/opt/zimbra/logger/db/work/*.gif': No such file or directory

Stopping logswatch...done.

Starting logswatch...done.



Yet, zmsoap returns status as 0...
[root@zimbra ~]# /opt/zimbra/bin/zmsoap -z GetServiceStatusRequest





0

0

0

0

0

0

0

0

0

0

0

0


Zimbra Administration Server Status all turned red

Posted: Mon Sep 30, 2013 9:08 am
by L. Mark Stone
Have the red X marks been there from day one or is this new? If new, have you done anything like Zimbra or operating system updates recently? Any other changes?
Basically to get the green check marks you need the service statuses to make it into /var/log/zimbra.log and then to have the Zimbra logger service be able to parse them. Sounds like the first part is working but not the second part... SOmetimes the logger service just dies and Zimbra is unable to restart it by itself.
What happens if you do as the zimbra user? :
zmloggerctl stop; zmloggerctl start; zmloggerctl status

If the service starts up with no errors then within ten minutes the red X's should change to the green checkmarks.
Let us know!

Mark

Re: Zimbra Administration Server Status all turned red

Posted: Tue Sep 20, 2016 3:45 am
by azam
How can i Solved this RED Mark error ?

Re: Zimbra Administration Server Status all turned red

Posted: Sat Nov 12, 2016 1:44 am
by huuphan
azam wrote:How can i Solved this RED Mark error ?

Hi azam! solve problem "RED" . you can run command line all zimbra server as bellow:
1. update /etc/rsyslog.conf /opt/zimbra/libexec/zmsyslogsetup ( as root account)
2. zmupdateauthkeys command to update and fetching key between zimbra server. ( as zimbra account)

Link below help to you:
http://www.huuphan.com/2016/11/zimbra-s ... nning.html

Re: Zimbra Administration Server Status all turned red

Posted: Tue Apr 25, 2017 5:25 am
by linuradu
I followed this post viewtopic.php?t=60723 and did the following:

I had a similar issue and I've tried what you described here but didn't worked for me.

I analysed the file "zmstatuslog" from (/opt/zimbra/libexec/zmstatuslog) and found there that there is a TIMEOUT set for 60 seconds;
The time executaion of "/opt/zimbra/bin/zmcontrol status" took around 90 seconds; Because of that, the code from this file was not executed properly
and this is the reason of "not sync status".

My solution was:
1. open and edit the file: #nano /opt/zimbra/libexec/zmstatuslog
2. change the line: "my $TIMEOUT=60;" to "my $TIMEOUT=360;"
3. Save the file and wait around 5 minutes.

This worked for me; Hopefully will work also for other people :)

If you type: "tail -f /var/log/zimbra-stats.log" you should see the status like, in the log:
Apr 24 11:41:07 mail zimbramon[28337]: 28337:info: 2017-04-24 11:40:02, STATUS: mail.test.com: antispam: Running
Apr 24 11:41:07 mail zimbramon[28337]: 28337:info: 2017-04-24 11:40:02, STATUS: mail.test.com: antivirus: Running
Apr 24 11:41:07 mail zimbramon[28337]: 28337:info: 2017-04-24 11:40:02, STATUS: mail.test.com: dnscache: Running
Apr 24 11:41:07 mail zimbramon[28337]: 28337:info: 2017-04-24 11:40:02, STATUS: mail.test.com: ldap: Running
....

Re: Zimbra Administration Server Status all turned red

Posted: Tue Jul 24, 2018 4:43 am
by mastermindkhan
Dear friends,

This is quite an old post, but i had to reply to it, because this issue just made me NUTS :shock: and I looked for a solution for the whole night but could not find it till finally i came across this and I want to share it to make someone's life easier. Just execute the following command and everything will be OK.

zmsoap -v -a <admin@domain.com> -p <password> GetServiceStatusRequest

Please keep in mind, that this solution is for the actual post which began this thread, not for any other related issue. This works when nothing else works. First you need to try the other methods and if all fail just type the above command and check your admin console. All will be well from then on. :D

Regards,

Bilal

Re: Zimbra Administration Server Status all turned red

Posted: Tue Jul 24, 2018 7:46 am
by gabrieles
mastermindkhan wrote:Just execute the following command and everything will be OK.
zmsoap -v -a <admin@domain.com> -p <password> GetServiceStatusRequest

Does not work for me. Keep in mind that GetServiceStatusRequest is a soap get api. It does not modify anything, maybe you fixed it in another way, and now GetServiceStatusRequest gives you correct results.