Server status data is not available

[marcw]

I've got a new 4.5.4 installation on a new Ubuntu Dapper Xen guest. Installation went fine (thanks for the Ubuntu DNS thread!) using the Ubuntu binary and everything works absolutely great! Except for one thing...

When I choose Server Status in the Admin console, I receive this message:

Server status data is not available.  To see the server status, logger service must be installed.

But zmcontrol status returns this:

zimbra@mail:~$ zmcontrol status
Host mail.onlymooo.com
        antispam                Running
        antivirus               Running
        ldap                    Running
        logger                  Running
        mailbox                 Running
        mta                     Running
        snmp                    Running
        spell                   Running

I'm not sure how to troubleshoot this. I've found a couple other threads here with similar issues but they seem to be for older versions because they reference dirs that don't even exist on my system.

Can anyone offer a suggestion or two? Thanks! (And thanks for a great product!)

[jholder]

I'm looking into a bug on this, but I'm not sure if it's a bug on our internal test server, or if it affects you as well.

[marcw]

Originally Posted by jholder

I'm looking into a bug on this, but I'm not sure if it's a bug on our internal test server, or if it affects you as well.

Thanks. I'll anxiously await your results. And if it's not a bug, I'll await any suggestions. :-)

[JHill]

I'm seeing this on a newly upgraded 4.5.5, too.

[illc0mm]

Same issue here RHEL4

[marcw]

Originally Posted by marcw

When I choose Server Status in the Admin console, I receive this message:

Server status data is not available.  To see the server status, logger service must be installed.

I found the answer to my problem. I've discovered that when I installed Zimbra there was no cron installed and by extension, no crontab. It seems Zimbra needs cron for the logger, at least.

(I installed Zimbra on Ubuntu Dapper that had been installed on an LV via debootstrap. debootstrap evidently installs only a minimal OS that didn't include quite a few files that Zimbra needs - including crontab).

For whatever reason, Zimbra chose not to complain about the lack of cron during installation and so I didn't even know about it until I looked into things a bit more. apt-get installed cron just fine but Zimbra was still complaining about the logger service needing to be installed. Further digging resulted in the realization that zimbra (the user) didn't have its own crontab but needed one. Mucking around in the perl installation scripts yielded the contents of what should be "crontab -u zimbra -l".

It seems to be working now. At least I no longer have my original issue.

[phoenix]

I'd appreciate it if you could file a report in bugzilla about there being no complaint of a missing cron during install?

[marcw]

Originally Posted by phoenix

I'd appreciate it if you could file a report in bugzilla about there being no complaint of a missing cron during install?

Ok, I'll do that. But just a heads up to anyone else that might use debootstrap for their Ubuntu installation; there are other files you're likely going to need that don't get installed by default. Here's a list I made pretty much by accident. There might be more that I haven't stumbled across yet:

1) cron
2) psmisc
3) file
4) perl-modules
5) logrotate
6) man
7) openssh-server
8) slocate

I'm pretty certain that Zimbra needs the first 3. I'm less certain about 4-5. And 6-8 you just need because I don't know how you'd function without them. I think all of them are installed on a "normal" Ubuntu installation but are missing from debootstrap. Retreive them all with apt-get.

[jholder]

We think that bug 16377 affects 4.5.5>

This may or may not be part of the issue, still a little unclear on that.

[Stergil]

I have the same problem. However, cron is installed and functioning.

Ubuntu 6.06.1-server
zcs-4.5.5_GA_838.DEBIAN3.1.tgz