Results 1 to 9 of 9

Thread: Fresh install - Zmmailboxd.pid is missing

  1. #1
    athemiya is offline Intermediate Member
    Join Date
    Mar 2011
    Location
    Brighton
    Posts
    19
    Rep Power
    4

    Default Fresh install - Zmmailboxd.pid is missing

    Hello to you all in here, I'm a total newbie [to linux too]

    So, a fresh install of Zimbra on CentOS 5.5. Here is what I get in the zimbra.log:

    Code:
    stale pid 6833 found in /opt/zimbra/log/zmmailboxd_manager.pid: No such process
    Mar 15 21:18:03 mail zmmailboxdmgr[12345]: assuming no other instance is running
    Mar 15 21:18:03 mail zmmailboxdmgr[12345]: file /opt/zimbra/log/zmmailboxd.pid does not exist
    Mar 15 21:18:03 mail zmmailboxdmgr[12345]: assuming no other instance is running
    Mar 15 21:18:03 mail zmmailboxdmgr[12345]: no manager process is running
    Other errors also included two port conflicts with 80 & 443.

    Results from posting dig sussexsu.com any are:
    Code:
    ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_5.3 <<>> sussexsu.com any
    ;; global options:  printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5092
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
    
    ;; QUESTION SECTION:
    ;sussexsu.com.                  IN      ANY
    
    ;; ANSWER SECTION:
    sussexsu.com.           2592000 IN      SOA     sussexsu.com. hostmaster.sussexsu.com. 2011030801 43200 3600 3600000 2592000
    sussexsu.com.           2592000 IN      NS      95.131.69.xxx.sussexsu.com.
    sussexsu.com.           2592000 IN      MX      10 mail.sussexsu.com.
    
    ;; ADDITIONAL SECTION:
    mail.sussexsu.com.      2592000 IN      A       95.131.69.xxx
    
    ;; Query time: 0 msec
    ;; SERVER: 127.0.0.1#53(127.0.0.1)
    ;; WHEN: Tue Mar 15 22:21:15 2011
    ;; MSG SIZE  rcvd: 142
    So, at the moment I cannot access the web URL/GUI?

    Let me know what you would like me to post from the server

    Many thanks in advance,
    A
    Last edited by athemiya; 03-15-2011 at 02:25 PM.

  2. #2
    phoenix is online now Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,585
    Rep Power
    57

    Default

    Quote Originally Posted by athemiya View Post
    Hello to you all in here, I'm a total newbie [to linux too]

    So, a fresh install of Zimbra on CentOS 5.5. Here is what I get in the zimbra.log:

    Code:
    stale pid 6833 found in /opt/zimbra/log/zmmailboxd_manager.pid: No such process
    Mar 15 21:18:03 mail zmmailboxdmgr[12345]: assuming no other instance is running
    Mar 15 21:18:03 mail zmmailboxdmgr[12345]: file /opt/zimbra/log/zmmailboxd.pid does not exist
    Mar 15 21:18:03 mail zmmailboxdmgr[12345]: assuming no other instance is running
    Mar 15 21:18:03 mail zmmailboxdmgr[12345]: no manager process is running
    Other errors also included two port conflicts with 80 & 443.

    Results from posting dig sussexsu.com any are:
    Code:
    ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_5.3 <<>> sussexsu.com any
    ;; global options:  printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5092
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
    
    ;; QUESTION SECTION:
    ;sussexsu.com.                  IN      ANY
    
    ;; ANSWER SECTION:
    sussexsu.com.           2592000 IN      SOA     sussexsu.com. hostmaster.sussexsu.com. 2011030801 43200 3600 3600000 2592000
    sussexsu.com.           2592000 IN      NS      95.131.69.xxx.sussexsu.com.
    sussexsu.com.           2592000 IN      MX      10 mail.sussexsu.com.
    
    ;; ADDITIONAL SECTION:
    mail.sussexsu.com.      2592000 IN      A       95.131.69.xxx
    
    ;; Query time: 0 msec
    ;; SERVER: 127.0.0.1#53(127.0.0.1)
    ;; WHEN: Tue Mar 15 22:21:15 2011
    ;; MSG SIZE  rcvd: 142
    So, at the moment I cannot access the web URL/GUI?

    Let me know what you would like me to post from the server

    Many thanks in advance,
    A
    The line I've highlighted above is incorrect, it should look like this:

    Code:
    sussexsu.com.           2592000 IN      NS      95.131.69.xxx
    The problem with your server is that you have another web server running on it, you need to stop it and disable it from starting on boot. When you've done that restart zimbra with:

    Code:
    zmcontrol restart
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  3. #3
    athemiya is offline Intermediate Member
    Join Date
    Mar 2011
    Location
    Brighton
    Posts
    19
    Rep Power
    4

    Default

    Hi Bill,

    Thanks for the reply.. I managed to get the web/gui interface working by changing the ports to 81 and 444 respectively.

    However, I see your point about changing the line you mentioned -do I do this in:

    Code:
    /etc/named/chroot/var/named/
    and edit the db file I have?

    If so, my current file has the following within it:

    Code:
    ;       Addresses and other host information.
    ;
    @       IN      SOA     sussexsu.com. hostmaster.sussexsu.com. (
                                   2011030801 ; Serial
                                   43200      ; Refresh
                                   3600       ; Retry
                                   3600000    ; Expire
                                   2592000 )  ; Minimum
    
    ;       Define the nameservers and the mail servers
                   IN      NS      95.131.69.xxx
                   IN      MX      10 mail.sussexsu.com.
    mail           IN      A       95.131.69.xxx

  4. #4
    athemiya is offline Intermediate Member
    Join Date
    Mar 2011
    Location
    Brighton
    Posts
    19
    Rep Power
    4

    Default

    Hi again Bill,

    OK, I managed to get this right now -check it:

    Code:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46290
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
    
    ;; QUESTION SECTION:
    ;sussexsu.com.                  IN      ANY
    
    ;; ANSWER SECTION:
    sussexsu.com.           2592000 IN      SOA     sussexsu.com. hostmaster.sussexsu.com. 2011030801 43200 3600 3600000 2592000
    sussexsu.com.           2592000 IN      NS      sussexsu.com.
    sussexsu.com.           2592000 IN      MX      10 mail.sussexsu.com.
    
    ;; ADDITIONAL SECTION:
    mail.sussexsu.com.      2592000 IN      A       95.131.69.xxx
    
    ;; Query time: 0 msec
    ;; SERVER: 127.0.0.1#53(127.0.0.1)
    ;; WHEN: Fri Mar 18 09:58:03 2011
    ;; MSG SIZE  rcvd: 128
    However Bill, can I ask you another question? I seem to be getting lots of time-outs and errors when, for instance, I do the following:

    1. Log into an email account online
    2. Click new appointment
    3. Click for Attendees

    .......then I get a long wait and the following errors:

    Code:
    method: [unknown] 
    msg: system failure: ldap search failed 
    code: service.FAILURE 
    detail: soap:Receiver 
    trace: com.zimbra.common.service.ServiceException: system failure: ldap search failed ExceptionId:btpool0-13://mail.sussexsu.com:81/service/soap/SearchGalRequest:1300443019695:682a4cfa1b32f80c Code:service.FAILURE at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:248) at com.zimbra.cs.gal.GalSearchControl.ldapSearch(GalSearchControl.java:610) at com.zimbra.cs.gal.GalSearchControl.search(GalSearchControl.java:160) at com.zimbra.cs.service.account.SearchGal.handle(SearchGal.java:64) at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:406) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:281) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:158) at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:294) at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:215) at javax.servlet.http.HttpServlet.service(HttpServlet.java:725) at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:208) at javax.servlet.http.HttpServlet.service(HttpServlet.java:814) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166) at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(SetHeaderFilter.java:79) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) 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:1157) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:218) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.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(HandlerWrapper.java:152) at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.handler.DebugHandler.handle(DebugHandler.java:77) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:543) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:946) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451) Caused by: javax.naming.CommunicationException: sussex.ac.uk:3269 [Root exception is java.net.SocketTimeoutException: connect timed out] at com.sun.jndi.ldap.Connection.(Connection.java:200) at com.sun.jndi.ldap.LdapClient.(LdapClient.java:118) at com.sun.jndi.ldap.LdapClientFactory.createPooledConnection(LdapClientFactory.java:46) at com.sun.jndi.ldap.pool.Connections.(Connections.java:97) at com.sun.jndi.ldap.pool.Pool.getPooledConnection(Pool.java:114) at com.sun.jndi.ldap.LdapPoolManager.getLdapClient(LdapPoolManager.java:310) at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1572) at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2652) at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:293) at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175) at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193) at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136) at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288) at javax.naming.InitialContext.init(InitialContext.java:223) at javax.naming.ldap.InitialLdapContext.(InitialLdapContext.java:134) at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:497) at com.zimbra.cs.account.ldap.LdapUtil.doGalSearch(LdapUtil.java:936) at com.zimbra.cs.account.ldap.LdapUtil.galSearch(LdapUtil.java:923) at com.zimbra.cs.gal.GalSearchControl.ldapSearch(GalSearchControl.java:608) ... 37 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(PlainSocketImpl.java:213) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:529) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:559) at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.jndi.ldap.Connection.createSocket(Connection.java:300) at com.sun.jndi.ldap.Connection.(Connection.java:187) ... 57 more  
    request: Body: {
      SearchGalRequest: {
        _jsns: "urn:zimbraAccount",
        limit: 50,
        name: ".",
        needExp: 1,
        offset: 0,
        sortBy: "nameAsc",
        type: "account"
       }
     },
    Header: {
      context: {
        _jsns: "urn:zimbra",
        account: {
          _content: "hesan@sussexsu.com",
          by: "name"
         },
        authToken: "(removed)",
        session: {
          _content: 1242,
          id: 1242
         },
        userAgent: {
          name: "ZimbraWebClient - [unknown] (Win)",
          version: "7.0.1_GA_3105"
         }
       }
    and a message in the browser that states: "A network service error has occurred".

    This seems to happen all the time online. Its really prohibiting me testing the calendar appointments and resources etc...

    I appreciate any feedback you give

  5. #5
    phoenix is online now Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,585
    Rep Power
    57

    Default

    Quote Originally Posted by athemiya View Post
    OK, I managed to get this right now -check it:

    Code:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46290
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
    
    ;; QUESTION SECTION:
    ;sussexsu.com.                  IN      ANY
    
    ;; ANSWER SECTION:
    sussexsu.com.           2592000 IN      SOA     sussexsu.com. hostmaster.sussexsu.com. 2011030801 43200 3600 3600000 2592000
    sussexsu.com.           2592000 IN      NS      sussexsu.com.
    sussexsu.com.           2592000 IN      MX      10 mail.sussexsu.com.
    
    ;; ADDITIONAL SECTION:
    mail.sussexsu.com.      2592000 IN      A       95.131.69.xxx
    
    ;; Query time: 0 msec
    ;; SERVER: 127.0.0.1#53(127.0.0.1)
    ;; WHEN: Fri Mar 18 09:58:03 2011
    ;; MSG SIZE  rcvd: 128
    That highlighted line is still incorrect, you should have an IP address in there.

    Quote Originally Posted by athemiya View Post
    However Bill, can I ask you another question? I seem to be getting lots of time-outs and errors when, for instance, I do the following:

    1. Log into an email account online
    2. Click new appointment
    3. Click for Attendees

    .......then I get a long wait and the following errors:
    That would be because the above DNS configuration is incorrect.

    After you've made the above change, go to the Split DNS article and run all the commands in the 'Verify...' section of that article then post the output here.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  6. #6
    athemiya is offline Intermediate Member
    Join Date
    Mar 2011
    Location
    Brighton
    Posts
    19
    Rep Power
    4

    Default

    Hi Bill,

    Thanks for your reply. OK, so I have the following after running the commands in the verify section:

    cat /etc/resolv.conf

    Code:
    search sussexsu.com
    nameserver 127.0.0.1
    cat /etc/hosts

    Code:
    127.0.0.1 localhost.localdomain localhost
    95.131.69.xxx mail.sussexsu.com mail
    Oh and now my dig looks correct now I think:

    Code:
    ;; QUESTION SECTION:
    ;sussexsu.com.                  IN      ANY
    
    ;; ANSWER SECTION:
    sussexsu.com.           2592000 IN      SOA     sussexsu.com. hostmaster.sussexsu.com. 2011030801 43200 3600 3600000 2592000
    sussexsu.com.           2592000 IN      NS      95.131.69.xxx.
    sussexsu.com.           2592000 IN      MX      10 mail.sussexsu.com.
    
    ;; ADDITIONAL SECTION:
    mail.sussexsu.com.      2592000 IN      A       95.131.69.xxx

    What do you think Bill?

    Regards,
    Hesan

  7. #7
    phoenix is online now Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,585
    Rep Power
    57

    Default

    Those DNS records appear to be OK and both the bapge for the user and Admin UI show-up. I'd suggest you change the login for the use Web UI to use https rather than the (insecure) http, go to the wiki and search for zmtlsctl for details on what to do.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  8. #8
    athemiya is offline Intermediate Member
    Join Date
    Mar 2011
    Location
    Brighton
    Posts
    19
    Rep Power
    4

    Default

    Hi Bill,

    OK, I followed the directions here

    CLI zmtlsctl to set Web Server Mode - Zimbra :: Wiki (and set the mode to https) and it does not seem to have changed the fact that every time I log into an on-line mail account and set a new appointment in the calendar, it gives this error:

    Code:
    method: [unknown] 
    msg: system failure: ldap search failed 
    code: service.FAILURE 
    detail: soap:Receiver 
    trace: com.zimbra.common.service.ServiceException: system failure: ldap search failed ExceptionId:btpool0-12://mail.sussexsu.com:444/service/soap/SearchCalendarResourcesRequest:1300705120460:ca0abf1b99891bb9 Code:service.FAILURE at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:248) at com.zimbra.cs.gal.GalSearchControl.ldapSearch(GalSearchControl.java:610) at com.zimbra.cs.gal.GalSearchControl.search(GalSearchControl.java:160) at com.zimbra.cs.service.account.SearchCalendarResources.searchGal(SearchCalendarResources.java:98) at com.zimbra.cs.service.account.SearchCalendarResources.handle(SearchCalendarResources.java:59) at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:406) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:281) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:158) at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:294) at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:215) at javax.servlet.http.HttpServlet.service(HttpServlet.java:725) at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:208) at javax.servlet.http.HttpServlet.service(HttpServlet.java:814) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166) at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(SetHeaderFilter.java:79) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) 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:1157) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:218) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.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(HandlerWrapper.java:152) at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.handler.DebugHandler.handle(DebugHandler.java:77) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:543) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:946) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451) Caused by: javax.naming.CommunicationException: sussex.ac.uk:3269 [Root exception is java.net.SocketTimeoutException: connect timed out] at com.sun.jndi.ldap.Connection.(Connection.java:200) at com.sun.jndi.ldap.LdapClient.(LdapClient.java:118) at com.sun.jndi.ldap.LdapClientFactory.createPooledConnection(LdapClientFactory.java:46) at com.sun.jndi.ldap.pool.Connections.(Connections.java:97) at com.sun.jndi.ldap.pool.Pool.getPooledConnection(Pool.java:114) at com.sun.jndi.ldap.LdapPoolManager.getLdapClient(LdapPoolManager.java:310) at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1572) at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2652) at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:293) at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175) at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193) at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136) at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288) at javax.naming.InitialContext.init(InitialContext.java:223) at javax.naming.ldap.InitialLdapContext.(InitialLdapContext.java:134) at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:497) at com.zimbra.cs.account.ldap.LdapUtil.doGalSearch(LdapUtil.java:936) at com.zimbra.cs.account.ldap.LdapUtil.galSearch(LdapUtil.java:923) at com.zimbra.cs.gal.GalSearchControl.ldapSearch(GalSearchControl.java:608) ... 38 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(PlainSocketImpl.java:213) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:529) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:559) at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.jndi.ldap.Connection.createSocket(Connection.java:300) at com.sun.jndi.ldap.Connection.(Connection.java:187) ... 58 more  
    request: Body: {
      SearchCalendarResourcesRequest: {
        _jsns: "urn:zimbraAccount",
        attrs: "email,zimbraCalResLocationDisplayName,zimbraCalResCapacity,zimbraCalResContactEmail,notes,zimbraCalResType",
        limit: 50,
        offset: 0,
        searchFilter: {
          conds: {
            cond: [
              0: {
                attr: "zimbraCalResType",
                op: "eq",
                value: "Location"
               }
             ]
           }
         }
       }
     },
    Header: {
      context: {
        _jsns: "urn:zimbra",
        account: {
          _content: "hesan@sussexsu.com",
          by: "name"
         },
        authToken: "(removed)",
        session: {
          _content: 1220,
          id: 1220
         },
        userAgent: {
          name: "ZimbraWebClient - [unknown] (Win)",
          version: "7.0.1_GA_3105"
         }
       }
     }
    Really strange?
    Regards,
    Hesan

  9. #9
    athemiya is offline Intermediate Member
    Join Date
    Mar 2011
    Location
    Brighton
    Posts
    19
    Rep Power
    4

    Default

    Actually, I realised what it was... I had set the GAL in server settings incorrectly so it was constantly timing-out!

    Until I get the right GAL settings, I won't put them back in.

    Resolving this GAL problem has stopped the server from timing out ! Yeah!

    Finally Bill - do you recommend using Collab Server with Zimbra Desktop? IT does seem that the on-line webmail is actually a lot more advanced than Zimbra Desktop?

    Regards,
    Hesan

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Replies: 3
    Last Post: 11-03-2007, 10:55 PM
  2. fresh install (both OS and Zimbra) but zimbra-spell fails
    By xtremetoonz in forum Installation
    Replies: 14
    Last Post: 09-09-2007, 12:34 AM
  3. Traslation SVN tree status
    By meikka in forum I18N/L10N - Translations
    Replies: 7
    Last Post: 02-13-2007, 11:13 AM
  4. RedHat EL4 fresh install
    By richard.bessey in forum Installation
    Replies: 1
    Last Post: 10-24-2006, 08:47 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
  •