Zimbra Not Working After Changing IP(Help Pls)

[mkhurram92]

hello,

I change the IP of my Zimbra Server. After reboot i check no one can able to open anything in browser not even zimbra desktop.

Services are just working fine

/etc/init.d/zimbra status
Host mailserver.nasrinefactory.com.sa
antispam Running
antivirus Running
ldap Running
logger Running
mailbox Running
mta Running
snmp Running
spell Running
stats Running
zmconfigd Running

But when i check logs of Mailbox it is showing some error that is under

tail -f /opt/zimbra/log/mailbox.log
at sun.reflect.GeneratedMethodAccessor11.invoke(Unkno wn Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.jndi.ldap.Connection.createSocket(Connecti on.java:339)
at com.sun.jndi.ldap.Connection.<init>(Connection.jav a:187)
... 56 more
2011-10-13 13:05:38,981 INFO [btpool0-0://localhost:7071/service/admin/soap/GetDomainInfoRequest] [ip=127.0.0.1;ua=ZCS/7.0.1_GA_3105;] soap - GetDomainInfoRequest
2011-10-13 13:10:07,204 INFO [btpool0-1://localhost:7071/service/admin/soap/AuthRequest] [ip=127.0.0.1;ua=zmprov/7.0.1_GA_3105;] soap - AuthRequest
2011-10-13 13:10:07,367 INFO [btpool0-1://localhost:7071/service/admin/soap/GetAllServersRequest] [name=zimbra;ip=127.0.0.1;ua=zmprov/7.0.1_GA_3105;] soap - GetAllServersRequest
2011-10-13 13:10:07,384 INFO [btpool0-1://localhost:7071/service/admin/soap/GetAllServersRequest] [name=zimbra;ip=127.0.0.1;ua=zmprov/7.0.1_GA_3105;] account - Initialized access manager: com.zimbra.cs.account.accesscontrol.ACLAccessManag er


What type of error it is and what i have to do to troubleshoot it

Plssssssssssss guide

I am using Zimbra Open Source 7.0.1 on CentOS5.5

Thanks

[phoenix]

Originally Posted by mkhurram92

I change the IP of my Zimbra Server. After reboot i check no one can able to open anything in browser not even zimbra desktop.

Did you actually change your DNS records to point to the new server IP?

Originally Posted by mkhurram92

What type of error it is and what i have to do to troubleshoot it

Did you search and try some of the solutions in the forums?

Originally Posted by mkhurram92

Plssssssssssss guide

Is the "s" key stuck on your keyboard?

[mkhurram92]

Originally Posted by phoenix

Did you actually change your DNS records to point to the new server IP?

Yes i delete DNS and MX record and create a new.

Originally Posted by phoenix

Did you search and try some of the solutions in the forums?

Yes i do but can't find anything

Originally Posted by phoenix

Is the "s" key stuck on your keyboard?

When U Feel Problems everything Stucks

[gvillari]

Hi,

have you update the /etc/hosts file with the new IP address?

Regards

[mkhurram92]

Originally Posted by gvillari

have you update the /etc/hosts file with the new IP address?

Thanks for replying, Yes i update that file also

[gvillari]

Could you show us the output of these commands?

cat /etc/hosts
cat /etc/resolv.conf
dig yourdomain mx
dig yourdomain any
host `hostname` <- note backticks and not single quotes

[mkhurram92]

The output of these command is under

Originally Posted by gvillari

cat /etc/hosts

cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
192.168.20.252 mailserver.abc.com mailserver

cat /etc/resolv.conf

cat /etc/resolv.conf
search abc.com
nameserver 192.168.20.2
nameserver 192.168.20.4

dig yourdomain mx

dig abc.com mx

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> abc.com mx
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23634
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2

;; QUESTION SECTION:
;abc.com. IN MX

;; ANSWER SECTION:
abc.com. 3600 IN MX 10 mailserver.abc.com

;; ADDITIONAL SECTION:
mailserver.abc.com. 3600 IN A 192.168.20.252

;; Query time: 1 msec
;; SERVER: 192.168.20.2#53(192.168.20.2)
;; WHEN: Thu Oct 13 19:03:56 2011
;; MSG SIZE rcvd: 119

dig yourdomain any

dig abc.com any

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> abc.com any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11288
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 7, AUTHORITY: 0, ADDITIONAL: 5

;; QUESTION SECTION:
;abc.com. IN ANY

;; ANSWER SECTION:
abc.com. 600 IN A 192.168.20.4
abc.com. 600 IN A 192.168.20.2
abc.com. 3600 IN NS sdc.abc.com.
abc.com. 3600 IN NS dc-1.abc.com.
abc.com. 3600 IN SOA dc-1.abc.com. hostmaster. 2644 900 600 86400 3600
abc.com. 3600 IN MX 10 mailserver.abc.com.

;; ADDITIONAL SECTION:
sdc.abc.com. 3600 IN A 192.168.20.4
dc-1.abc.com. 3600 IN A 192.168.20.81
dc-1.abc.com. 3600 IN A 192.168.20.2
mailserver.abc.com. 3600 IN A 192.168.20.252

;; Query time: 1 msec
;; SERVER: 192.168.20.2#53(192.168.20.2)
;; WHEN: Thu Oct 13 19:06:16 2011
;; MSG SIZE rcvd: 282

host `hostname` <- note backticks and not single quotes

host `hostname`
mailserver.abc.com has address 192.168.20.252

[mkhurram92]

Well i am able to get zimbra administrator login page and i was authenticating users with Active Directory. Now when i am monitoring logs of mailbox it is showing error like this

com.zimbra.common.service.ServiceException: system failure: 192.168.100.2:3268
ExceptionId:btpool0-2://192.168.20.252:7071/service/admin/soap/AuthRequest:1318522892288:1e6a3b2783c89ba3
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:248)
at com.zimbra.cs.account.ldap.LdapProvisioning.extern alLdapAuth(LdapProvisioning.java:3637)
at com.zimbra.cs.account.auth.AuthMechanism$LdapAuth. doAuth(AuthMechanism.java:165)
at com.zimbra.cs.account.ldap.LdapProvisioning.verify PasswordInternal(LdapProvisioning.java:3683)
at com.zimbra.cs.account.ldap.LdapProvisioning.verify Password(LdapProvisioning.java:3656)
at com.zimbra.cs.account.ldap.LdapProvisioning.authAc count(LdapProvisioning.java:3522)
at com.zimbra.cs.account.ldap.LdapProvisioning.authAc count(LdapProvisioning.java:3504)
at com.zimbra.cs.service.admin.Auth.handle(Auth.java: 145)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:406)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:281)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:158)
at com.zimbra.soap.SoapServlet.doWork(SoapServlet.jav a:294)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:215)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:725)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:208)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:814)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1166)
at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(Set HeaderFilter.java:79)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:132)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:388)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:218)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:422)
at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:230)
at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.handler.rewrite.RewriteHandler.h andle(RewriteHandler.java:230)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.handler.DebugHandler.handle(Debu gHandler.java:77)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:543)
at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:946)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:756)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:405)
at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:410)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:451)
Caused by: javax.naming.CommunicationException: 192.168.100.2:3268 [Root exception is java.net.SocketTimeoutException: connect timed out]
at com.sun.jndi.ldap.Connection.<init>(Connection.jav a:200)
at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.jav a:118)
at com.sun.jndi.ldap.LdapClient.getInstance(LdapClien t.java:1580)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:265 2)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:293)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapC txFactory.java:175)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(Ldap CtxFactory.java:193)
at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstanc e(LdapCtxFactory.java:136)
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext (LdapCtxFactory.java:66)
at javax.naming.spi.NamingManager.getInitialContext(N amingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(Init ialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.ja va:223)
at javax.naming.ldap.InitialLdapContext.<init>(Initia lLdapContext.java:134)
at com.zimbra.cs.account.ldap.ZimbraLdapContext.ldapA uthenticate(ZimbraLdapContext.java:573)
at com.zimbra.cs.account.ldap.LdapUtil.ldapAuthentica te(LdapUtil.java:92)
at com.zimbra.cs.account.ldap.LdapProvisioning.extern alLdapAuth(LdapProvisioning.java:3628)
... 41 more
Caused by: java.net.SocketTimeoutException: connect timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl .java:351)
at java.net.PlainSocketImpl.connectToAddress(PlainSoc ketImpl.java:213)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.j ava:200)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.j ava:366)
at java.net.Socket.connect(Socket.java:529)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknow n Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.jndi.ldap.Connection.createSocket(Connecti on.java:339)
at com.sun.jndi.ldap.Connection.<init>(Connection.jav a:187)
... 56 more
2011-10-13 19:21:32,289 INFO [btpool0-2://192.168.20.252:7071/service/admin/soap/AuthRequest] [name=administrator@nasrinefactory.com.sa;ip=192.16 8.20.83;ua=ZimbraWebClient - SAF3 (Win);] SoapEngine - handler exception: authentication failed for administrator, invalid password

[mkhurram92]

I Got the solution in this post.

http://www.zimbra.com/forums/adminis...tml#post229150

Thanks all for helping