[SOLVED] Web Admin UI Server Status...offline?

[ArcaneMagus]

Well since the LDAP replica server wouldn't be running the mailbox service which handles SOAP requests, it makes sense that it gets a connection refused error...

The question remains though if you are getting "the expected results" on the main server how in the world is it not showing as online?!? The admin UI simply runs that SOAP request and then parses the output into the page.


Hmmm.... just had a thought. Is the date/time returned by this recent?

date -d @`zmsoap -z GetServiceStatusRequest | grep status | head -n1 | cut -f2 -d"\""`

[mackoftrack]

Originally Posted by ArcaneMagus

Well since the LDAP replica server wouldn't be running the mailbox service which handles SOAP requests, it makes sense that it gets a connection refused error...

The question remains though if you are getting "the expected results" on the main server how in the world is it not showing as online?!? The admin UI simply runs that SOAP request and then parses the output into the page.


Hmmm.... just had a thought. Is the date/time returned by this recent?

date -d @`zmsoap -z GetServiceStatusRequest | grep status | head -n1 | cut -f2 -d"\""`

My main server *is* showing online. It is the LDAP replica server that is showing as offline.

The dates/times are fine.

[mackoftrack]

So, ArcaneMagus, any ideas?

[odeleon]

Hi,
check to see if syslog is running. if it is, is the server listening on port 514/udp? check your firewall settings too.

To get it to listen for remote syslog events you need to edit /etc/sysconfig/syslog and modify the line for SYSLOGD_OPTIONS so it looks something like:

SYSLOGD_OPTIONS="-r -m 0"

-r sets it to listen to remote events. The script for syslog sets up everything else, just leaves this minor detail out.

Then restart the logger service (or perhaps the whole zimbra service) and you should be all set.

[sergiumartin]

Originally Posted by odeleon

Hi,
check to see if syslog is running. if it is, is the server listening on port 514/udp? check your firewall settings too.

To get it to listen for remote syslog events you need to edit /etc/sysconfig/syslog and modify the line for SYSLOGD_OPTIONS so it looks something like:

SYSLOGD_OPTIONS="-r -m 0"

-r sets it to listen to remote events. The script for syslog sets up everything else, just leaves this minor detail out.

Then restart the logger service (or perhaps the whole zimbra service) and you should be all set.

This fixed it for all you guys out there? Cause on our server we still have the "red X" on all services Any other ideas on this one?

[blazeking]

Originally Posted by sergiumartin

This fixed it for all you guys out there? Cause on our server we still have the "red X" on all services Any other ideas on this one?

Not for me. I just upgraded from 5.0.18 to 6.0.4, and I'm still having this issue.

[sergiumartin]

Originally Posted by blazeking

Not for me. I just upgraded from 5.0.18 to 6.0.4, and I'm still having this issue.

yeap..same here (we upgraded from 6.0.2 to 6.0.4)..we had this issue before the upgrade and it's still here after the upgrade..

[msonen]

Originally Posted by sergiumartin

This fixed it for all you guys out there? Cause on our server we still have the "red X" on all services Any other ideas on this one?

Same issue for us. After the upgrade from 5.0.18 to 6.0.4 we are getting the same issue...

[redhate]

#Zimbra: Wrong status in Server Status (RESOLVIDO) – redhate.me - solved

[iniazi]

Ok, I was having the same problem. zmcontrol status etc showed all running but of course zmsoap said 0 (since thats what the gui is looking at also). And /var/log/zimbra-stats.log showed stuff running.

Anyway, so I had changed zmstatuslog initially from every 2 minutes to every 30 minutes. when I changed it back to 2 minutes, everything went all green. So there must be a check somewhere that verifies that the status is being run every 2 minutes (or possibly makes sure its not too old... in this case 30 minutes was probably too long). I wonder if we can change that other threshold. I'm going to experiment with every 5 minutes to see if that works. I've roughly checked every minute for about 15 minutes and haven't seen an 'X' yet.