Zimbra 5.0.18 Upgrade to 6.0.4 - Some Issues

[LMStone]

Now that we got multi-server syslog-ng working on 6.0.4, we found we were missing data in the Daily Admin Report (the new format is terrific BTW, thanks Zimbra!)

This was the same problem another user noticed here: Daily Mail Report - missing data

So, I replied on that post and filed a bug with a proposed fix method here: Bug 43847 – Incorrect Log File Rotation Method Causing Missing Data in Daily Admin Report and Admin Console Stats Pages

Please vote for the bug if you are seeing this same issue.

In the interim, we just set the "DAILY_TIME" to 23:55 (the zimbra crontab generates the daily mail report at 23:30 each night and does spam training at 23:45) and see what happens. I'll report back tomorrow...

Hope that helps,
Mark

[quanah]

Hi Mark,

It was already reopened since 6.0.4 was released, and then fixed (which is why it is now resolved/fixed rather than verified/fixed). I've specifically asked QA to make sure they test SLES10 and SLES11 with syslog-ng for this bug.

--Quanah

[LMStone]

Originally Posted by quanah

Hi Mark,

It was already reopened since 6.0.4 was released, and then fixed (which is why it is now resolved/fixed rather than verified/fixed). I've specifically asked QA to make sure they test SLES10 and SLES11 with syslog-ng for this bug.

--Quanah

Thanks Quanah.

Anything we can do on our end to help with this issue?

All the best,
Mark

[mailman.33]

Hi Mark,

First of all, thanks a lot for sharing your experience with us. This thread has come a long way, way too much effort. I appreciate your helping hand.

I recently upgraded 3 of my servers from 6.0.5 to 6.0.7 and it went well, really happy with the result. But I also had to face some issues like broken mailqueue display and certs not being displayed in admin interface, which I could correct with wonderful help from mmorse and phoenix. What's left is server status not updating in admin interface. I run zimbra on RHEL and syslogd is what works on it. To my surprise '/var/log/zimbra-stats.log' is working fine and stats are being populated but somehow it just won't show up in front end.

Can you guide me with this? I am sure there is just a small missing piece I should figure out, hope you can help me with it. Please let me know if should get more details. Good luck Mark!

[LMStone]

Originally Posted by mailman.33

Hi Mark,

First of all, thanks a lot for sharing your experience with us. This thread has come a long way, way too much effort. I appreciate your helping hand.

I recently upgraded 3 of my servers from 6.0.5 to 6.0.7 and it went well, really happy with the result. But I also had to face some issues like broken mailqueue display and certs not being displayed in admin interface, which I could correct with wonderful help from mmorse and phoenix. What's left is server status not updating in admin interface. I run zimbra on RHEL and syslogd is what works on it. To my surprise '/var/log/zimbra-stats.log' is working fine and stats are being populated but somehow it just won't show up in front end.

Can you guide me with this? I am sure there is just a small missing piece I should figure out, hope you can help me with it. Please let me know if should get more details. Good luck Mark!

Hmmm...

Please check the following and let us know what you find:

1. Are all of the hourly slots in the Daily Mail Report populated with activity?
2. On the syslog server, are there entries from all three servers in /var/log/zimbra-stats.log?
3. At what time of days does RHEL restart the syslog daemon?

All the best,
Mark

[mailman.33]

Mark,

I managed to fix the stats issue by issuing /opt/zimbra/libexec/zmsyslogsetup on the logger server. Before the status was logging for just the proxy server. Now it's neatly populating the mailbox servers. Thanks for your help.

However, one thing I found was that the binary for zmsyslogsetup on logger host with 6.0.7 was safe in /opt/zimbra/libexec instead of /opt/zimbra/bin. All these while I was looking for it to update the logger host to reset it and get the stats populating. No regrets, got working into lot of areas

Before the /var/log/zimbrastats.log had no entries for mailbox servers even though the daily mail reports were properly working. And I could find /etc/syslog.conf a bit scrambled up which could have also caused it. Syslogd was set to restart everyday around 15.00. Anyway thanks for your time Mark

PS. Since the latest version 6.0.7, zmsyslogsetup resides in /opt/zimbra/libexec!

[mailman.33]

Mark,

I hope you fixed this too, the 403 error with Jetty while accessing Social Zimlet. Could you update the status and how you happen to do it? Thanks.
--------
Problem accessing /service/proxy. Reason:

FORBIDDEN
--------

[LMStone]

Glad things are coming along for you!

We should be cognizant of thread drift here, :-) but perhaps this will help with your Zimbra Social issues:

[SOLVED] Zimbra Social Zimlet and Jetty 403 Errors

All the best,
Mark

[mailman.33]

Mark,

Didn't bother to search on this issue, I knew you would be up to something so straight away bumped this thread. Anyway thanks a bunch for getting back. I will work on it. Take care, wishin you the best!