Message Count/Volume all ZERO since day of 8.6 upgrade/server name change

[liverpoolfcfan]

In the Admin console, all the Message Count, Message Volume, SPAM/Anti-virus activity all show ZERO ever since the day I upgraded to 8.6

Is there something that needs to be done post-upgrade to restart these counters? 

Edit: In order to push through the upgrade I had to rename the server as our commercial certificate was for the external name, and the server had been using an internal name.

I now suspect that there is a setting somewhere that is telling the Admin Console to report on messages/etc for the OLD server name. Hence all the figures since then would be zero. 

Does anyone know where zimbra stores the name of the server to be reported on?

[Fabio S. Schmidt]

Hi livepoolfcfan,



Plese take a look at this wiki page: https://wiki.zimbra.com/wiki/Mail_Queue_Monitoring



"The authentication method assumes that sshd on the mta is running on port 22, and that RSA Authentication is enabled. You can test the ssh command with:



ssh -i .ssh/zimbra_identity -o strictHostKeyChecking=no zimbra@MAIL.DOMAIN.COM

(Swap MAIL.DOMAIN.COM for your hostname, as it appears in the error).



You should NOT be prompted for a password; if you are, recreate the ssh keys and retry the test."

[liverpoolfcfan]

Thanks Fabio.



In my case it looks like the "Zimbra account has been disabled" is the possible culprit. I have unlocked it and can now ssh correctly.



When running the first of the ssh tests, it prompted that it was permanently adding the host to the identity file (I think). When upgrading to 8.6 I was forced to rename my server so the internal name (hostname) matched the external MX name (and commercial certificate) Perhaps renaming the server meant that zimbra user was not authorized to connect to the server by the new name - and this caused the issue?



I will monitor to see if I start to get data collected.



Vincent

[liverpoolfcfan]

Still no data in the Admin Console displays this morning. Note the Queue monitor is working correctly - it is the historical displays that are not populating.



Anybody got any other ideas?

[liverpoolfcfan]

Bump.

Still no data available in the Admin Console -> Monitor -> Message Volume since the upgrade to 8.6.

Does anyone have an idea why the data collection would have stopped? Or where to look for error(s) that might give a clue?

EDIT: As far as  I can tell zmstat files are all getting populated/rolled over correctly. 

EDIT: Another thought - Could the charts be filtering/displaying data for the old server name?  I had to rename the server from zimbra.mydomain.com to mail.mydomain.com to match with our commercial server in order for 8.6 to install. Could some part of the monitoring/charting configuration still be telling it to display data for zimbra.mydomain.com ...  this would explain why numbers existed up until the switchover. Where does zimbra look for the name of the server for the stats displays?

 

[liverpoolfcfan]

Added more data to original post.

[jorgedlcruz]

Hi Liverpool,

Did you check the next Wiki? I hope can help you:

• https://wiki.zimbra.com/wiki/ZmSetServerName#Clean_the_zmloggerhostmap

Best regards

[liverpoolfcfan]

Thanks Jorge. I will try that.



I have 5 entries - 2 for the old hostname, two for the new hostname, and one for localhost.



I have removed the 2 for the old hostname. Should I also get rid of localhost?



Thanks

[jorgedlcruz]

I just had the ones for the hostname, not localhost.



Best regards

[liverpoolfcfan]

Thanks .

The old stats do not show any more. I now have none whatsoever. Let's see if they start populating tomorrow.  Do you know if there is a tool to reprocess the stats files ?

On another note, it might be worth adding the 3 items I found that did not get updated to the new name to either the ZmSetServerName tool, or at least to the wiki page.  

I found that the following two settings were still showing the old name
zimbraReverseProxyAvailableLookupTargets: zimbra.mydomain.com
zimbraReverseProxyUpstreamLoginServers: zimbra.mydomain.com

and the ssh key generated by sshkeygen and deployed by zmupdateauthkeys was still referencing the old name. I regenerated and redeployed it.

See post on thread  http://community.zimbra.com/collaboration/f/1886/t/1139570#pi33863=2  for details