dont bother upgrading to 5.0.2

I've been playing with zimbra from early 4.0 builds and genearlly been quite happy with it, but something about 5.0.2, just doesnt work right. Quite honestly you may save your self a LOT of frustration stayin with 4.5 series.

1) Been through all the trouble shooting restarting/reconfiguring logger/repairing logger db, to complete delete and rebuild logger db... still doesnt work. Its jsut broke.

2) Random outages that prevent logins... (used to throw exceptions in mailbox log saying too many files beign used etc. but fixed that problem with ulimit) Now no error messages at all. Basically user sends password to pop, with OK+ response, then when trying to throw the password, it just times out etc. No errors to Mailboxd lgo, or /var/log/zimbra.

So, basically where everything stands, no stats no information no graphs or anything like that, and every few hours I have to restart zimbra services with nothing to hand devs to say this exception is occuring. Zimbra++

"The logger service and its presentation in the admin console has been unreliable and the source of many support cases"

It's really hit and miss. The reasons it can fail also vary from case to case. We have the bug, and may phase it out in future releases.

In the mean time, please feel free to search the forums, and we'll help.

Also, about #2, this may require more investigation. The things I hope you consider are:

1) We're working on #1
2) Very few people have had this type of error. Since we have well over 20 Million paid mailboxes, and many more FOSS edition mailboxes, you may need to consider any special circumstances that you might have.

This isn't to say that there isn't a Zimbra issue. There may well be a Zimbra issue, however, please consider that it also may be "The way you're doing things".

well PART of #2 is that I guess new jetty is very resource intensive or something, had well over the limit of the number of files debian was allowing... and while thats questionable as to whos fault that really was, I dont beleive the problem existed in pre 5.0 (which if it IS due to jetty being resource intensive, it would stand to reason)

Wouldnt necessarily consider it a bug, but more of looking at it to make sure things were done as efficient as they could have been.

as a followup as if it werent really that clear, zimbra was throwing exceptions like crazy saying too many files open, and changing ulimits and whatnot seemed to tempoarily remedy the situation for now.