I see this in your log, which is the first time I see this kind of issue:
2008-11-11 23:15:00,670 WARN [btpool0-2] [ip=127.0.0.1;] SoapEngine - handler exception
java.lang.RuntimeException: failure instantiating global Config
at com.zimbra.cs.account.offline.OfflineConfig.instan tiate(OfflineConfig.java:53)
at com.zimbra.cs.account.offline.OfflineProvisioning. reload(OfflineProvisioning.java:324)
at com.zimbra.cs.account.AuthTokenKey.refresh(AuthTok enKey.java:139)
at com.zimbra.cs.account.AuthTokenKey.getCurrentKey(A uthTokenKey.java:166)
at com.zimbra.cs.account.ZimbraAuthToken.getCurrentKe y(ZimbraAuthToken.java:110)
at com.zimbra.cs.account.ZimbraAuthToken.getEncoded(Z imbraAuthToken.java:329)
at com.zimbra.cs.account.ZimbraAuthToken.getOrigAuthD ata(ZimbraAuthToken.java:366)
at com.zimbra.cs.account.ZimbraAuthToken.encodeAuthRe sp(ZimbraAuthToken.java:407)
at com.zimbra.cs.service.admin.Auth.doResponse(Auth.j ava:165)
at com.zimbra.cs.service.admin.Auth.handle(Auth.java: 136)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:414)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:269)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:160)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:269)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:189)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:487)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:362)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:716)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:406)
at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:211)
at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
at org.mortbay.jetty.handler.RewriteHandler.handle(Re writeHandler.java:176)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:313)
at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:506)
at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:844)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:644)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:211)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:381)
at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:396)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:442)
Caused by: com.zimbra.cs.account.AccountServiceException: email address already exists: null
ExceptionId:btpool0-2:1226438100655:d03c6f4a36ee9dd0
Code:account.ACCOUNT_EXISTS
at com.zimbra.cs.account.AccountServiceException.ACCO UNT_EXISTS(AccountServiceException.java:219)
at com.zimbra.cs.db.DbOfflineDirectory.createDirector yEntry(DbOfflineDirectory.java:76)
at com.zimbra.cs.account.offline.OfflineConfig.instan tiate(OfflineConfig.java:41)
... 35 more  |