[SOLVED] Problems after upgrading 5.0.16 - 6.0.0

[tolaini]

Hi, we tried upgrading 5.0.16 FOSS to 6.0.0 FOSS. After running the upgrade script without errors, we ended up having the following problems:

* Web interfaces hangs loading after login (AJAX and HTML versions), both the standard user interface and the admin one.

* The zmmailboxdmgr java process eats up 100% CPU everytime.

A clean installation of Zimbra 6 on Ubuntu 8.04 LTS in the same configuration works ok, so I guess this is a problem generated by the upgrade. Any suggestion?

[LebPekin]

I have EXACTLY the same problem...

Upgrade from OSE 6.0 RC1 (up) -> 6.0 GA (down).

I can check my mail thru IMAP but I can't use the web application... Nothing appears after the login...

[tolaini]

I can check my mail thru IMAP but I can't use the web application... Nothing appears after the login...

Yes, same here: POP3 and IMAP are functional, web interface is stuck.

[LebPekin]

A clue :

In /var/log/zimbra.log, when I register with my mail and password, I have these lines :
Sep 8 10:48:57 mail slapd[16003]: conn=317 op=3 do_abandon: get_ctrls failed

I don't know how to fix that... I have never customized the Zimbra LDAP server

[LebPekin]

New clue : the web interface WORKS for all users EXCEPT admin users (blank page) !

I still doesn't know why...

[LebPekin]

New clues :

1/ If I create a new admin user thru SSH, I can check emails of this user

2/ If I change my rights from admin to user, I'm still not available to check my email thru the web interface...

[tolaini]

New clue : the web interface WORKS for all users EXCEPT admin users (blank page) !

Can confirm this. And the java process starts eating up CPU only when an admin account tries to log in. If I log in as a normal user, CPU usage is fine.

[tolaini]

More testing: I have modified a migrated admin account (using zmprov ma) mostly equal to a newly created admin account (except for username/email/id) and it still hangs the java process.

Is there some sort of user data cache (something outside LDAP) that is incorrecly migrated from 5.0 to 6.0?

[tolaini]

Even more findings: I can successfully login as a migrated admin user who has never logged in before upgrade. Something wrong got placed in mysql DB?

If that can matter, we enabled the (beta) Zimbra IM service in 5.0.

[tolaini]

I tried to remove the admin flag from a migrated admin account, but this won't fix the problem. So I think I nailed down the anomaly to admin accounts that have logged in at least 1 time in Zimbra 5.