Upgraded Zimbra to 6.0.2 but still having same problem...

[axtran]

My users cannot connect using ajax. When I use Firefox, it hangs on login at "Loading" and clicking on HTML mode is the only way in (browser reports done). When I login using IE, it shows "Error on Page" and references some java applets that fail:

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2; Zune 4.0; Creative AutoUpdate v1.40.01)
Timestamp: Sat, 24 Oct 2009 09:49:13 UTC


Message: Expected '}'
Line: 5142
Char: 107
Code: 0
URI: https://eagles.cui.edu/zimbra/js/Sta...v=091020152818


Message: Syntax error
Line: 4847
Char: 112
Code: 0
URI: https://eagles.cui.edu/zimbra/js/Sta...v=091020152818


Message: 'AjxCore' is undefined
Line: 1546
Char: 5
Code: 0
URI: https://eagles.cui.edu/zimbra/


Message: 'AjxHistoryMgr' is undefined
Line: 1463
Char: 3
Code: 0
URI: https://eagles.cui.edu/zimbra/

Instead of saying "loading" it says "undefined." What is going on?

[phoenix]

Have you tried the obvious, clearing the browser cache?

[axtran]

I am receiving "Killed Process 8538 (java)" and "Out of memory: kill process 8536 (sh) score 1192184 or a child" errors on the console of the server, including a "Killed process 30640 (zmqueuelog)

[axtran]

It started to let me login though :-\

[phoenix]

How much RAM is on this server and is it in a VM?

[MaffooClock]

I am experiencing the exact problem; I was running 6.0.1 without any problems. After upgrading th 6.0.2, this is what's happening.

I originally reported this here:
http://www.zimbra.com/forums/install...ed-web-ui.html

After spending several hours re-applying the nginx proxy configuration, trying other themes, wasting time and getting nowhere, @jterhune's suggestion (comment #7) solved the problem for me.

chown -R zimbra:zimbra /opt/zimbra/nginx-0.5.37-zimbra/proxy_temp*

[axtran]

jterhune is my Network Engineer

Anyways, we also had to move zimbra logs onto its own drive (so that it wouldn't pack our MTA server's disk space). The server is a VM with 4GB of RAM, 4 CPU cores. It used to be 3GB of RAM. The server runs proxy, memcached, MTA, proxy, and snmp.