Results 1 to 6 of 6

Thread: [SOLVED] Problem with addresses lookup after upgrade to 7

  1. #1
    Join Date
    Aug 2008
    Posts
    8
    Rep Power
    7

    Unhappy [SOLVED] Problem with addresses lookup after upgrade to 7

    Hi,

    I just upgraded my OS edition to 7. Looks great and the social tab is really nice.
    I have one (liitle) problem, whem composing a new mail, address lookups fail.
    When clicking the To button, the following error appears:
    method: [unknown]
    msg: system failure: Caught IOException opening index
    code: service.FAILURE
    detail: soap:Receiver
    trace: com.zimbra.common.service.ServiceException: system failure: Caught IOException opening index ExceptionId:btpool0-7://192.168.192.50/service/soap/SearchRequest:1297145453117:9351315b65c841fa Code:service.FAILURE at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:248) at com.zimbra.cs.index.LuceneIndex.expandWildcardToke n(LuceneIndex.java:459) at com.zimbra.cs.index.MailboxIndex.expandWildcardTok en(MailboxIndex.java:458) at com.zimbra.cs.index.query.TextQuery.(TextQuery.jav a:113) at com.zimbra.cs.index.query.TextQuery.(TextQuery.jav a:67) at com.zimbra.cs.index.query.parser.QueryParser.creat eContactQuery(QueryParser.java:660) at com.zimbra.cs.index.query.parser.QueryParser.creat eQuery(QueryParser.java:606) at com.zimbra.cs.index.query.parser.QueryParser.toDef aultClause(QueryParser.java:331) at com.zimbra.cs.index.query.parser.QueryParser.toCla use(QueryParser.java:300) at com.zimbra.cs.index.query.parser.QueryParser.toQue ry(QueryParser.java:265) at com.zimbra.cs.index.query.parser.QueryParser.parse (QueryParser.java:235) at com.zimbra.cs.index.ZimbraQuery.(ZimbraQuery.java: 439) at com.zimbra.cs.index.MailboxIndex.search(MailboxInd ex.java:143) at com.zimbra.cs.mailbox.IndexHelper.search(IndexHelp er.java:129) at com.zimbra.cs.mailbox.Mailbox.search(Mailbox.java: 3743) at com.zimbra.cs.service.mail.Search.doSearch(Search. java:134) at com.zimbra.cs.service.mail.Search.handle(Search.ja va:114) at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:401) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:276) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:157) 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:727) at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:208) at javax.servlet.http.HttpServlet.service(HttpServlet .java:820) 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:218) 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: java.io.FileNotFoundException: /opt/zimbra/index/0/5/index/0/_16p_2.del (No such file or directory) at java.io.RandomAccessFile.open(Native Method) at java.io.RandomAccessFile.(RandomAccessFile.java:21 2) at org.apache.lucene.store.SimpleFSDirectory$SimpleFS IndexInput$Descriptor.(SimpleFSDirectory.java:76) at org.apache.lucene.store.SimpleFSDirectory$SimpleFS IndexInput.(SimpleFSDirectory.java:97) at org.apache.lucene.store.NIOFSDirectory$NIOFSIndexI nput.(NIOFSDirectory.java:98) at org.apache.lucene.store.NIOFSDirectory.openInput(N IOFSDirectory.java:78) at org.apache.lucene.store.FSDirectory.openInput(FSDi rectory.java:347) at com.zimbra.cs.index.LuceneDirectory.openInput(Luce neDirectory.java:135) at org.apache.lucene.util.BitVector.(BitVector.java:2 19) at org.apache.lucene.index.SegmentReader.loadDeletedD ocs(SegmentReader.java:649) at org.apache.lucene.index.SegmentReader.get(SegmentR eader.java:609) at org.apache.lucene.index.SegmentReader.get(SegmentR eader.java:583) at org.apache.lucene.index.DirectoryReader.(Directory Reader.java:109) at org.apache.lucene.index.ReadOnlyDirectoryReader.(R eadOnlyDirectoryReader.java:27) at org.apache.lucene.index.DirectoryReader$1.doBody(D irectoryReader.java:79) at org.apache.lucene.index.SegmentInfos$FindSegmentsF ile.run(SegmentInfos.java:677) at org.apache.lucene.index.DirectoryReader.open(Direc toryReader.java:73) at org.apache.lucene.index.IndexReader.open(IndexRead er.java:316) at org.apache.lucene.index.IndexReader.open(IndexRead er.java:262) at com.zimbra.cs.index.LuceneIndex.openIndexReader(Lu ceneIndex.java:696) at com.zimbra.cs.index.LuceneIndex.getIndexReaderRef( LuceneIndex.java:785) at com.zimbra.cs.index.LuceneIndex.getIndexSearcherRe f(LuceneIndex.java:527) at com.zimbra.cs.index.LuceneIndex.expandWildcardToke n(LuceneIndex.java:423) ... 50 more
    request:

    Body: {
    SearchRequest: {
    _jsns: "urn:zimbraMail",
    field: "contact",
    limit: 50,
    locale: {
    _content: "nl"
    },
    offset: 0,
    query: ""." (is:local)",
    sortBy: "nameAsc",
    types: "contact",
    tz: {
    id: "Europe/Berlin"
    }
    }
    },
    Header: {
    context: {
    _jsns: "urn:zimbra",
    account: {
    _content: "martijn@mmoret.com",
    by: "name"
    },
    authToken: "(removed)",
    notify: {
    seq: 2
    },
    session: {
    _content: 11,
    id: 11
    },
    userAgent: {
    name: "ZimbraWebClient - FF3.0 (Mac)",
    version: "7.0.0_GA_3077"
    }
    }
    }

    A reboot did not work.
    I am running Zimbra on Ubuntu 10.04 LTS 64-bit.

    TIA
    Martijn

  2. #2
    Join Date
    Aug 2005
    Location
    San Mateo, CA
    Posts
    4,789
    Rep Power
    19

    Default

    Please file a bug in bugzilla and attach the mailbox.log with as much detail as possible.

    It looks like an index issue. Did you try to re-index the mailbox from the cmd line or the admin console?
    Looking for new beta users -> Co-Founder of Acompli. Previously worked at Zimbra (and Yahoo! & VMware) since 2005.

  3. #3
    Join Date
    Dec 2008
    Posts
    13
    Rep Power
    6

    Default

    I'm seeing this problem as well. Was a bug ever opened on this issue?

  4. #4
    Join Date
    Aug 2008
    Posts
    8
    Rep Power
    7

    Default

    I'm first trying the re-index optionIf that does not work, I will open a bug.

    Regards
    Martijn
    PS, re-index is running.....

  5. #5
    Join Date
    Aug 2008
    Posts
    8
    Rep Power
    7

    Smile

    Hi,

    Re-indexing finished and solved the problem!
    I did it from the command-line as I do not know how to run it from the admin interface ;-).

    Here is the command I used:
    zmprov rim user@domain.com start
    Follow the progress with:
    zmprov rim user@domain.com status

    Thanks to KevinH!

    regards
    Martijn

  6. #6
    Join Date
    Dec 2008
    Posts
    13
    Rep Power
    6

    Default

    Cool, thanks for the update. Glad to hear it solved the problem.

Similar Threads

  1. [SOLVED] Amavisd-Postfix RCPT TO Takes a long time
    By samuraii in forum Administrators
    Replies: 8
    Last Post: 02-11-2009, 02:34 PM
  2. Problem after upgrade to 5.0
    By bmannella in forum Installation
    Replies: 6
    Last Post: 01-26-2008, 12:35 AM
  3. upgrade problem
    By skak in forum Installation
    Replies: 2
    Last Post: 09-26-2007, 12:56 AM
  4. smtp table lookup problem
    By s_c_johnson in forum Installation
    Replies: 5
    Last Post: 09-21-2007, 05:46 AM
  5. 4.01 to 4.02 upgrade problem (with solution)
    By criley in forum Migration
    Replies: 2
    Last Post: 09-28-2006, 11:36 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •