Server status data is not available

[mmgomess]

Dear friends, I have looked at several posts here in forum a solution to the problem "Server status data is not available. To see the server status, logger service must be installed." but none worked for me.

Please someone knows the solution that actually solves this problem?

Thanks

[phoenix]

You should update your forum profile with the output of the following command (do not post the output in this thread):

zmcontrol -v

Dear friends, I have looked at several posts here in forum a solution to the problem "Server status data is not available. To see the server status, logger service must be installed." but none worked for me.

Please someone knows the solution that actually solves this problem?

Do tell us what you've actually tried to fix this problem otherwise we'll be wasting time going over the same 'solutions'. Are all the services actually enabled? Is this a single server or multi-server installation? Do you have valid DNS A & MX records and a correct /etc/hosts file (you can check all that in the Split DNS wiki article 'Verify...' section)?

[LMStone]

Dear friends, I have looked at several posts here in forum a solution to the problem "Server status data is not available. To see the server status, logger service must be installed." but none worked for me.

Please someone knows the solution that actually solves this problem?

Thanks

As Bill pointed out we need more information to help, but to get you started it might be helpful to understand the chain of events that results in Server Status being visible in the Admin Console.

In the first instance, you need data in /var/log/zimbra.log and /var/log/zimbra-stats.log. If you run as root:

tail -f /var/log/zimbra-stats.log

you should see data being populated in the log file. If not, you likely have a syslog problem.

Once data is being populated in those log files, then the Zimbra logger service and its related components parse the data and make it available to be displayed in the Admin Console.

Errors generated by the Zimbra logger service will be deposited in /var/log/zimbra.log, so the first step is to make sure those log files are being generated correctly.

But we really need specifics as Bill mentioned to help you go the next step!

All the best,
Mark

[mmgomess]

Do tell us what you've actually tried to fix this problem otherwise we'll be wasting time going over the same 'solutions'. Are all the services actually enabled? Is this a single server or multi-server installation? Do you have valid DNS A & MX records and a correct /etc/hosts file (you can check all that in the Split DNS wiki article 'Verify...' section)?

Dear Phoenix, the version of Zimbra is the 6.0.6_GA_2330.UBUNTU8 UBUNTU8 FOSS edition.

I tried many things and I did not know could be solved in different ways.

It's a single server installation.
I have a valid DNS, MX records and /etc/hosts corrects.

I wonder if there is a solution that resolved for all versions of Zimbra.

Sorry my english.

[mmgomess]

Mark, thanks for the reply. The /var/log/zimbra.log and /var/log/zimbra-stats.log are with the content being generated normally as in the examples below:

zimbra-stats.log:
May 4 09:08:17 [private] zimbramon[13436]: 13436:info: zmstat vm.csv: timestamp, r, b, swpd, free, buff, cache, si, so, bi, bo, in, cs, us, sy, id, wa, MemTotal, MemFree, Buffers, Cached, SwapCached, Active, Inactive, HighTotal, HighFree, LowTotal, LowFree, SwapTotal, SwapFree, Dirty, Writeback, AnonPages, Mapped, Slab, SReclaimable, SUnreclaim, PageTables, NFS_Unstable, Bounce, CommitLimit, Committed_AS, VmallocTotal, VmallocUsed, VmallocChunk, HugePages_Total, HugePages_Free, HugePages_Rsvd, HugePages_Surp, Hugepagesize, loadavg:: 05/04/2011 09:08:17, 2, 2, 528800, 154848, 22056, 174456, 0, 0, 41, 1239, 346, 1354, 66, 25, 8, 1, 4148000, 154848, 22056, 174456, 378584, 3829700, 73488, 3276736, 3928, 871264, 150920, 915664, 386864, 2488, 0, 3706444, 52332, 43308, 25400, 17908, 12056, 0, 0, 2989664, 4891116, 118776, 3124, 115336, 0, 0, 0, 0, 204:::31CA6A04-7647-11E0-8E6C-1769EBCC4311:::
May 4 09:08:17 [private] zimbramon[13436]: :::31CA6A04-7647-11E0-8E6C-1769EBCC4311:::8, 5.57
May 4 09:08:20 [private] zimbramon[13869]: 13869:info: zmstat fd.csv: timestamp, fd_count, mailboxd_fd_count:: 05/04/2011 09:08:20, 5920, 1341
May 4 09:08:22 [private] zimbramon[13452]: 13452:info: zmstat mtaqueue.csv: timestamp, KBytes, requests:: 05/04/2011 09:08:22, 8681, 170
May 4 09:08:23 [private] zimbramon[4080]: 4080:info: 2011-05-04 09:08:02, STATUS: [private]: antispam: Running
May 4 09:08:23 [private] zimbramon[4080]: 4080:info: 2011-05-04 09:08:02, STATUS: [private]: ldap: Running
May 4 09:08:23 [private] zimbramon[4080]: 4080:info: 2011-05-04 09:08:02, STATUS: [private]: logger: Running
May 4 09:08:23 [private] zimbramon[4080]: 4080:info: 2011-05-04 09:08:02, STATUS: [private]: mailbox: Running
May 4 09:08:23 [private] zimbramon[4080]: 4080:info: 2011-05-04 09:08:02, STATUS: [private]: memcached: Running
May 4 09:08:23 [private] zimbramon[4080]: 4080:info: 2011-05-04 09:08:02, STATUS: [private]: mta: Running
May 4 09:08:23 [private] zimbramon[4080]: 4080:info: 2011-05-04 09:08:02, STATUS: [private]: snmp: Running
May 4 09:08:23 [private] zimbramon[4080]: 4080:info: 2011-05-04 09:08:02, STATUS: [private]: spell: Running
May 4 09:08:23 [private] zimbramon[4080]: 4080:info: 2011-05-04 09:08:02, STATUS: [private]: stats: Running

/var/log/zimbra.log
May 4 09:12:35 [private] amavis[8438]: (08438-03) ESMTP::10024 /opt/zimbra/data/amavisd/tmp/amavis-20110504T091202-08438: -> SIZE=18829 BODY=8BITMIME ENVID=2002-285-4304227-5825516-36382-0-2-0-5825516-1304459191-2 Received: from [private] ([127.0.0.1]) by localhost ([private] [127.0.0.1]) (amavisd-new, port 10024) with ESMTP for ; Wed, 4 May 2011 09:12:35 -0300 (BRT)
May 4 09:12:35 [private] amavis[31749]: (31749-15) ESMTP::10024 /opt/zimbra/data/amavisd/tmp/amavis-20110504T090336-31749: -> SIZE=18732 BODY=8BITMIME ENVID=2002-285-2572475-5825516-26450-0-2-0-5825516-1304459191-2 Received: from [private] ([127.0.0.1]) by localhost ([private] [127.0.0.1]) (amavisd-new, port 10024) with ESMTP for ; Wed, 4 May 2011 09:12:35 -0300 (BRT)
May 4 09:12:35 [private] amavis[8438]: (08438-03) Checking: fqVNnKdw6tQf [187.61.34.208] ->
May 4 09:12:35 [private] amavis[31749]: (31749-15) Checking: pSfVhd0zXAoB [187.61.36.246] ->
May 4 09:12:35 [private] postfix/lmtp[23419]: 66F0FD1C019: to=, relay=[private][172.16.0.96]:7025, delay=0.24, delays=0.04/0.01/0.01/0.18, dsn=2.1.5, status=sent (250 2.1.5 Delivery OK)
May 4 09:12:35 [private] postfix/qmgr[30762]: 66F0FD1C019: removed
May 4 09:12:36 [private] postfix/smtpd[11062]: 77CC2D1C00A: client=localhost[127.0.0.1]
May 4 09:12:36 [private] postfix/cleanup[7434]: 77CC2D1C00A: message-id=<006101cc0a55$0f936e80$2eba4b80$@minasplanempreendi mentos.com.br>
May 4 09:12:36 [private] postfix/smtpd[11062]: disconnect from localhost[127.0.0.1]
May 4 09:12:36 [private] postfix/qmgr[30762]: 77CC2D1C00A: from=, size=3541, nrcpt=2 (queue active)
May 4 09:12:36 [private] amavis[5268]: (05268-06) FWD via SMTP: -> ,,BODY=7BIT 250 2.0.0 Ok, id=05268-06, from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as 77CC2D1C00A
May 4 09:12:36 [private] amavis[5268]: (05268-06) Passed CLEAN, [75.126.195.13] [::ffff:187.104.50.77] -> ,, Message-ID: <006101cc0a55$0f936e80$2eba4b80$@minasplanempreendi mentos.com.br>, mail_id: 6DG+8fnIvRDb, Hits: -3.558, size: 2792, queued_as: 77CC2D1C00A, 4039 ms
May 4 09:12:36 [private] postfix/smtp[3301]: 47F04D1C013: to=, orig_to=, relay=127.0.0.1[127.0.0.1]:10024, delay=5.6, delays=1.6/0/0.01/4, dsn=2.0.0, status=sent (250 2.0.0 Ok, id=05268-06, from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as 77CC2D1C00A)
May 4 09:12:36 [private] postfix/smtp[3301]: 47F04D1C013: to=, relay=127.0.0.1[127.0.0.1]:10024, delay=5.6, delays=1.6/0/0.01/4, dsn=2.0.0, status=sent (250 2.0.0 Ok, id=05268-06, from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as 77CC2D1C00A)
May 4 09:12:36 [private] postfix/qmgr[30762]: 47F04D1C013: removed

[ZimGuy]

All the status in the web interface are marked with red cross ?

[mmgomess]

No. Only the message: "Server status data is not available. To see the server status, logger service must be installed."

[ZimGuy]

is-it a mono or multi server installation ?

[mmgomess]

Single server installation.

[ZimGuy]

When you go to the server page status, do you get any error into the logs ?
May be an update could solved the problem.