[SOLVED] Find account by UUID

[MobiusNZ]

Hi there,

I'm noticing this in my mailbox.log. How can I find out who the ID "be6f5d0f-a825-481f-af7b-7cedc98fc8f6" belongs to?

2011-06-13 11:05:06,591 WARN [btpool0-17://server.example.com/service/soap/SyncRequest] [ip=192.168.132.254;] SoapEngine - unable to construct SOAP context
com.zimbra.common.service.ServiceException: permission denied: can not access account be6f5d0f-a825-481f-af7b-7cedc98fc8f6
ExceptionId:btpool0-17://server.example.com/service/soap/SyncRequest:1307919906591:5f23acd8459b279f
Code:service.PERM_DENIED
at com.zimbra.common.service.ServiceException.PERM_DE NIED(ServiceException.java:278)
at com.zimbra.common.service.ServiceException.DEFEND_ ACCOUNT_HARVEST(ServiceException.java:287)
at com.zimbra.soap.ZimbraSoapContext.<init>(ZimbraSoa pContext.java:235)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:203)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:158)
at com.zimbra.soap.SoapServlet.doWork(SoapServlet.jav a:291)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:212)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:725)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:181)
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:155)
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)

[Krishopper]

You can use

zmprov ga be6f5d0f-a825-481f-af7b-7cedc98fc8f6

from the command line

[MobiusNZ]

Thanks.

I get

ERROR: account.NO_SUCH_ACCOUNT (no such account: be6f5d0f-a825-481f-af7b-7cedc98fc8f6)

Any ideas on how I can track down what/who/where is attempting this logon?

[fyd]

Originally Posted by MobiusNZ

Thanks.

I get

Any ideas on how I can track down what/who/where is attempting this logon?

It turns out that, the exception is generated about a non-existing account or deleted account. I am seeing a lot of these on my mailbox.log after upgrading to 6.0.13 from .10.

Krishopper's command will give results if it exists, and yes it gave me your result. Account doesn't exist.

[fyd]

imho the subject line doesn't go with the issue we are facing. Maybe this should be addressed with a new thread or subject line should be changed.

[LMStone]

Any chance the mailbox existed at one time, was moved to another mailbox server, but never purged from the original server?

Just trying to think of a scenario where Zimbra would have a UID for a mailbox which technically no longer exists.

Hope that helps,
Mark

[MobiusNZ]

No, we've only got the one Zimbra server (we cluster using DRBD)

[LMStone]

Originally Posted by MobiusNZ

No, we've only got the one Zimbra server (we cluster using DRBD)

Any cluster failovers recently? Any chance you have a split brain (in your cluster that is...)?

Can you gracefully failover the cluster and see if the mailbox exists on the other cluster member?

Mark

[MobiusNZ]

Nope - no failovers recently, and definitely not split brain.

The way we have DRBD set up its impossible for the account to exist on one node and not the other - the filesystems are sync'd atomically.

[fyd]

Originally Posted by LMStone

Any chance the mailbox existed at one time, was moved to another mailbox server, but never purged from the original server?

Just trying to think of a scenario where Zimbra would have a UID for a mailbox which technically no longer exists.

Hope that helps,
Mark

Hi Mark, thanks. Good to see you.

Mine is an ldap/mta/proxy along with two mailstore servers. I guess you are right, I've moved some accounts from one mailstore to another, through the standard mailbox move with zmmailbox. I then make sure it doesn't exist there(make sure the account shows the new mailstore as location)
But that was some long time back, and never seen those errors on my previous 6 versions.

So do you think this can happen as the ids were cached by ldap, and now querying it?