we have installed the 4.5.9 Networkedition and worked 20 users for 4 weeks on it 2 LDAP, 2 SMTP and one Mailbox. after 4 weeks we think every is ok and make an upgrate to 5.0.1 ZCS, migrate our 450 Users from our old 4.0 GPL on debian to the 4.5.9 on Ubuntu 6.06 Networkedition. The complete solution is now running on a HA virtual enviroment.
After the useres are migratet, the performance of the SAN is very bad and we don't find the Problem at the moment. So i set up one more physical Mailbox Server and one more physical MTA and upgrate all servers to the 5.0.2 Version and want to enable imapProxy on the physical Mailbox Server. because i want to move the Mailboxes to the Physical machine, but here are the problems:
1. moving mailboxes created under 4.5.9 works fine. All others created under 5.0.1 is not working. the comes an error.
2. Proxy not work. At first i testet it direct after installation and by testing it via Telnet the connection resets after entering password
The i found this article and edit the nginx.conf.in directly with the entry on line 47
memcache_servers mailboxsrv1.mydomain.net:7072 mailboxsrv2.mydomain.net:7072;
and comment out the dynamic build string, because in the nginx.conf there is only one entry with the mailboxsrv2 without port.
After i restart the Proxyserver the connection was not reset but i can always not authenticate. here the outbut from the nginx.log:
-snip-
2008/02/11 09:15:32 [notice] 21070#0: channel myip2:7072 bad for (at least) 60000 msec, reconnecting
2008/02/11 09:15:32 [notice] 21070#0: attempted re-connection to memcached channel myip2:7072 (rc: -2)
2008/02/11 09:15:52 [notice] 21070#0: channel myip1:7072 bad for (at least) 60000 msec, reconnecting
2008/02/11 09:15:52 [notice] 21070#0: attempted re-connection to memcached channel myip1:7072 (rc: -2)
2008/02/11 09:16:02 [notice] 21070#0: no data on myip2:7072, channel is now bad
2008/02/11 09:16:02 [warn] 21070#0: channel myip2:7072 went bad, will reconnect in 60000 msec
2008/02/11 09:16:22 [notice] 21070#0: no data on myip1:7072, channel is now bad
2008/02/11 09:16:22 [warn] 21070#0: channel myip1:7072 went bad, will reconnect in 60000 msec
2008/02/11 09:17:02 [notice] 21070#0: channel myip2:7072 bad for (at least) 60000 msec, reconnecting
2008/02/11 09:17:02 [notice] 21070#0: attempted re-connection to memcached channel myip2:7072 (rc: -2)
2008/02/11 09:20:44 [info] 21072#0: *3591 client 192.168.100.188 connected to 0.0.0.0:110
2008/02/11 09:20:52 [notice] 21070#0: no data on myip1:7072, channel is now bad
2008/02/11 09:20:52 [warn] 21070#0: channel myip1:7072 went bad, will reconnect in 60000 msec
2008/02/11 09:21:09 [notice] 21072#0: no data on myip1:7072, channel is now bad
2008/02/11 09:21:09 [warn] 21072#0: channel myip1:7072 went bad, will reconnect in 60000 msec
2008/02/11 09:21:09 [info] 21072#0: *3591 client login failed: "Account information not available" while in http auth state, client: 192.168.100.188, server: 0.0.0.0:110, login: "alex@testdomain.de"
-snip-
telnet to port 7072 on both mailbox servers are ok.
Please help, because the zimbra support did not answer and our customers are bord.
regards Alex  |