Cannot search or add appointments to calendar

[fieryprophet]

Anytime I try to do a search in the web client through the search bar, I get a "network service error" with the details below:
A network service error has occurred. msg: system failure: java.lang.NullPointerException

code: service.FAILURE

method: SearchRequest

detail: soap:Receiver
/var/log/zimbra.log does not mention anything wrong. This is Zimbra 5.0.1 running on Ubuntu LTS 6.06
Trying to add an appointment gives me this:
msg: system failure: java.lang.NullPointerException

code: service.FAILURE

method: CreateAppointmentRequest

detail: soap:Receiver

[fieryprophet]

This is the open source edition, as well.
has no one run into this kind of problem before? I'm willing to research whatever solution necessary, I just need someone to point me in the right direction.

[tim brennan]

Look in /opt/zimbra/log/mailbox.log and paste the full exception trace here

[fieryprophet]

2008-04-29 08:27:56,480 WARN [btpool0-18] [name=admin@customcomputinginc.net;mid=1;ip=71.54.141.199;ua=ZimbraWebClient - [unknown] (Win)/5.0.1_GA_1902.UBUNTU6;] SoapEngine - handler exception

java.lang.NullPointerException

at com.zimbra.cs.index.ZimbraQuery$TextQuery.getQueryOperation(ZimbraQuery.java:1644)

at com.zimbra.cs.index.ZimbraQuery$ParseTree$ThingNode.getQueryOperation(ZimbraQuery.java:2165)

at com.zimbra.cs.index.ZimbraQuery$ParseTree$OperatorNode.getQueryOperation(ZimbraQuery.java:2110)

at com.zimbra.cs.index.ZimbraQuery.(ZimbraQuery.java:2389)

at com.zimbra.cs.index.MailboxIndex.search(MailboxIndex.java:147)

at com.zimbra.cs.mailbox.Mailbox.search(Mailbox.java:3128)

at com.zimbra.cs.service.mail.Search.doSearch(Search.java:100)

at com.zimbra.cs.service.mail.Search.handle(Search.java:72)

at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:342)

at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:208)

at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:113)

at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:272)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)

at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:174)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)

at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1093)

at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)

at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:132)

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)

at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)

at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)

at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)

at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:716)

at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.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(HandlerWrapper.java:139)

at org.mortbay.jetty.handler.RewriteHandler.handle(RewriteHandler.java:176)

at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)

at org.mortbay.jetty.Server.handle(Server.java:313)

at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506)

at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:844)

at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:644)

at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)

at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)

at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396)

at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)

[fieryprophet]

Is this not the right information?

[mmorse]

Could you update to 5.0.5 and see if this situation persists? We've had lots of changes since then, while this doesn't strike my memory as having been a problem on 5.0.1 - I don't see it on current releases, and it's also easier for us to diagnose and address if you're hitting it on a newer build.
http://www.zimbra.com/forums/announcements/17360-5-0-5-released.html

-Please don't forget to make a backup!

[tim brennan]

Doesn't ring a bell at all -- the NPE is in a strange place, not exactly sure what would cause it to happen. Have you done anything strange to the account, like tried to disable the index from config or something like that? Have you tried restarting the service to see if the error goes away?
Next step is to turn on index debugging and see what search is doing when the NPE happens:
Open up /opt/zimbra/conf/log4j.properties and add the following lines to the END of the file:

log4j.logger.com.zimbra.cs.index=DEBUG

log4j.logger.zimbra.index=DEBUG

Restart your server, or wait 5 minutes for the change to take -- then repro the problem. Cut out the time period with the repro from your mailbox.log and post it here or PM it to me.
If your server is very busy, it will be easier to reproduce this during an off time, to lessen the noise in the log.

[tim brennan]

I've Seen a few more reports of this -- there's definitely a server bug here. Restarting the server will get the account unstuck.
Bug 27726 has been filed.

[fieryprophet]

I will attempt to replicate the bug, which is appearing across all of the server's accounts.
I'll post back shortly.

[fieryprophet]

Upgrading to version 5.05 OSE resolved my problem.