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

[kepp]

Same here again. Ran zmstatuslog and the admin page still shows everything is offline. I did notice this while reading through the ~/log folder. In ~/convertd.out it reads:

log4j:WARN No appenders could be found for logger (zimbra.misc).
log4j:WARN Please initialize the log4j system properly.
Sun Aug 30 12:28:00 CDT 2009: Starting convertd
Sun Aug 30 12:28:00 CDT 2009: convertd is ready

That seems suspicious.. From what I understand it is the logger service that would be updating the status, if log4j isn't working right that could cause problems I'd think.

[damiand]

First please let me say thanks for replying to this post.

Release 6.0.1_GA_1816.UBUNTU8 UBUNTU8 NETWORK edition.

I did not have crontab installed as the version of ubuntu I am running is 8.0.4 JEOS

Are there jobs that should have setup during install or even after? if so do you know what they are?

[ArcaneMagus]

Wow... you didn't have crontab installed? That would certainly be why the stats where all 'X' for you.. I wonder how Zimbra even let you install without it. Yes there are quite a few things that should be in the crontab for the zimbra user. Now that you have it installed does anything show up when you do `crontab -l` as the zimbra user? If not I can post mine, but it seems to have quite a few things in it from older installs that are commented out so a clean new one would be better.

[ArcaneMagus]

kepp convertd is I think a network edition only feature (for converting attachments to HTML), so somebody with that would have to say whether that is normal or not. My guess is that maybe they didn't updated convertd to the new logger setup in 6.0.x, but I could easily be wrong. But that also means that it isn't the root of your problem...

[damiand]

Once I installed it and checked for jobs nothing is in it. Yes, please post yours. This is a test server so I may just reinstalled it.

[NoDoze]

Uhmmm... did we loose focus here...?

Mine is 6.0.1 upgrade from 5.0.16...on a test server.

All the status in the admin web ui are red Xs....

the cron u mentioned executes ok.
in the cli status is ok and says running.
other then the status page everything works normal.

[ArcaneMagus]

Originally Posted by NoDoze

Uhmmm... did we loose focus here...?

Mine is 6.0.1 upgrade from 5.0.16...on a test server.

All the status in the admin web ui are red Xs....

the cron u mentioned executes ok.
in the cli status is ok and says running.
other then the status page everything works normal.

Does the following return anything for you?

grep STATUS /var/log/zimbra-stats.log

This should return a bunch of sets of lines that look like this

Oct  1 10:06:08 email zimbramon[7114]: 7114:info: 2009-10-01 10:06:01, STATUS: email.pyxislab.com: antispam: Running
Oct  1 10:06:08 email zimbramon[7114]: 7114:info: 2009-10-01 10:06:01, STATUS: email.pyxislab.com: antivirus: Running
Oct  1 10:06:08 email zimbramon[7114]: 7114:info: 2009-10-01 10:06:01, STATUS: email.pyxislab.com: ldap: Running
Oct  1 10:06:08 email zimbramon[7114]: 7114:info: 2009-10-01 10:06:01, STATUS: email.pyxislab.com: logger: Running
Oct  1 10:06:08 email zimbramon[7114]: 7114:info: 2009-10-01 10:06:01, STATUS: email.pyxislab.com: mailbox: Running
Oct  1 10:06:08 email zimbramon[7114]: 7114:info: 2009-10-01 10:06:01, STATUS: email.pyxislab.com: memcached: Running
Oct  1 10:06:08 email zimbramon[7114]: 7114:info: 2009-10-01 10:06:01, STATUS: email.pyxislab.com: mta: Running
Oct  1 10:06:08 email zimbramon[7114]: 7114:info: 2009-10-01 10:06:01, STATUS: email.pyxislab.com: snmp: Running
Oct  1 10:06:08 email zimbramon[7114]: 7114:info: 2009-10-01 10:06:01, STATUS: email.pyxislab.com: spell: Running
Oct  1 10:06:08 email zimbramon[7114]: 7114:info: 2009-10-01 10:06:01, STATUS: email.pyxislab.com: stats: Running

On 6.0.x this is what is parsed to give you the status screen's info.

damiand attatched is my crontab.

[kepp]

I rebooted the entire server last night, after making a few changes. It seems to be working correctly now.
The only thing that stands out to me about my changes were that I changed the zmstatuslog entry in my crontab.
I went from */60 * * * * /opt/zimbra/libexec/zmstatuslog to */10 * * * * /opt/zimbra/libexec/zmstatuslog
I also ran 'zmtlsctl redirect' to force people onto the https site.

Hopefully that helps you NoDoze.. good luck! I appreciate the help tracking down possibilities as well. Thanks everyone

[ArcaneMagus]

Wow they have new installs going to every 60 minutes? Mine is set to update every 2 minutes.

[kepp]

No, it was slowing down my server too much every 2 minutes. Every 60 minutes could be too slow, making it not display I guess. It was recommended in a thread on here about logger's high cpu load