Page 1 of 2 12 LastLast
Results 1 to 10 of 15

Thread: Zimbra generates large mailbox.log files

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

    Default Zimbra generates large mailbox.log files

    Hello all,

    Since a few months we have a Zimbra 5.05 mailserver on Ubuntu 6.06. The partition where Zimbra is installed is 15 GB. Now we have the problem that Zimbra is generating mailbox.log files with random sizes. A summary of the files with date and file size:

    November, 14: 498KB
    November, 15: 4.7MB
    November, 16: 21MB
    November, 17: 7.5MB
    November, 18: 297MB
    November, 19: 1.1MB
    November, 20: 4 (!!!!) GB

    I can't explain the difference between the file sizes. Why does the last mailbox.log file have the file size of 4 GB? The loglevel is set to INFO witch is the standard loglevel in Zimbra. Can anyone explain this to me? How can I fix the generating of these (abnormal) large files?

  2. #2
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    Some idea of what error messages are in the file might go some way to explaining it.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  3. #3
    Join Date
    Nov 2008
    Posts
    8
    Rep Power
    7

    Default

    Here is the directory listing:
    Code:
    -rw-r-----  1 zimbra zimbra 7.8G Nov 25 09:16 mailbox.log
    -rw-r-----  1 zimbra zimbra  21M Nov 16 23:59 mailbox.log.2008-11-16
    -rw-r-----  1 zimbra zimbra 7.5M Nov 17 23:59 mailbox.log.2008-11-17
    -rw-r-----  1 zimbra zimbra 297M Nov 18 23:59 mailbox.log.2008-11-18
    -rw-r-----  1 zimbra zimbra 1.1M Nov 19 23:59 mailbox.log.2008-11-19
    -rw-r-----  1 zimbra zimbra 1.8G Nov 21 23:59 mailbox.log.2008-11-21
    -rw-r-----  1 zimbra zimbra 999K Nov 22 23:59 mailbox.log.2008-11-22
    -rw-r-----  1 zimbra zimbra 2.0M Nov 23 23:59 mailbox.log.2008-11-23
    -rw-r-----  1 zimbra zimbra 2.5M Nov 24 23:59 mailbox.log.2008-11-24
    And here the tail of the mailbox.log file:
    Code:
    	... 7 more
    Caused by: java.net.ConnectException: Connection refused
    	at java.net.PlainSocketImpl.socketConnect(Native Method)
    	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
    	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
    	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
    	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
    	at java.net.Socket.connect(Socket.java:519)
    	at sun.reflect.GeneratedMethodAccessor106.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:336)
    	at com.sun.jndi.ldap.Connection.<init>(Connection.java:184)
    	... 24 more
    2008-11-25 07:40:36,601 WARN  [MailboxPurge] [name=e.****@****.nl;mid=22;] purge - Unable to get mailbox id's
    com.zimbra.common.service.ServiceException: system failure: getDirectContext
    ExceptionId:MailboxPurge:1227595236601:73f3acbf3ecbade8
    Code:service.FAILURE
    	at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:253)
    	at com.zimbra.cs.account.ldap.LdapUtil.getDirContext(LdapUtil.java:253)
    	at com.zimbra.cs.account.ldap.LdapUtil.getDirContext(LdapUtil.java:238)
    	at com.zimbra.cs.account.ldap.LdapUtil.getDirContext(LdapUtil.java:229)
    	at com.zimbra.cs.account.ldap.LdapProvisioning.getServerByName(LdapProvisioning.java:2196)
    	at com.zimbra.cs.account.ldap.LdapProvisioning.getServerByName(LdapProvisioning.java:2185)
    	at com.zimbra.cs.account.ldap.LdapProvisioning.getLocalServer(LdapProvisioning.java:2569)
    	at com.zimbra.cs.mailbox.PurgeThread.getMailboxIds(PurgeThread.java:222)
    	at com.zimbra.cs.mailbox.PurgeThread.run(PurgeThread.java:117)
    Caused by: javax.naming.CommunicationException: zimbra.peperzaken.nl:389 [Root exception is java.net.ConnectException: Connection refused]
    	at com.sun.jndi.ldap.Connection.<init>(Connection.java:197)
    	at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:118)
    	at com.sun.jndi.ldap.LdapClientFactory.createPooledConnection(LdapClientFactory.java:46)
    	at com.sun.jndi.ldap.pool.Connections.<init>(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:2616)
    	at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:287)
    	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.<init>(InitialLdapContext.java:134)
    	at com.zimbra.cs.account.ldap.LdapUtil.getDirContext(LdapUtil.java:246)
    	... 7 more
    Caused by: java.net.ConnectException: Connection refused
    	at java.net.PlainSocketImpl.socketConnect(Native Method)
    	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
    	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
    	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
    	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
    	at java.net.Socket.connect(Socket.java:519)
    	at sun.reflect.GeneratedMethodAccessor106.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:336)
    	at com.sun.jndi.ldap.Connection.<init>(Connection.java:184)
    	... 24 more
    2008-11-25 07:40:36,601 WARN  [MailboxPurge] [name=e.***@***.nl;mid=22;] purge - Unable to determine value of zimbraMailPurgeSleepInterval
    com.zimbra.common.service.ServiceException: system failure: getDirectContext
    ExceptionId:MailboxPurge:1227595236601:73f3acbf3ecbade8
    Code:service.FAILURE
    	at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:253)
    	at com.zimbra.cs.account.ldap.LdapUtil.getDirContext(LdapUtil.java:253)
    	at com.zimbra.cs.account.ldap.LdapUtil.getDirContext(LdapUtil.java:238)
    	at com.zimbra.cs.account.ldap.LdapUtil.getDirContext(LdapUtil.java:229)
    	at com.zimbra.cs.account.ldap.LdapProvisioning.getServerByName(LdapProvisioning.java:2196)
    	at com.zimbra.cs.account.ldap.LdapProvisioning.getServerByName(LdapProvisioning.java:2185)
    	at com.zimbra.cs.account.ldap.LdapProvisioning.getLocalServer(LdapProvisioning.java:2569)
    	at com.zimbra.cs.mailbox.PurgeThread.getSleepInterval(PurgeThread.java:187)
    	at com.zimbra.cs.mailbox.PurgeThread.run(PurgeThread.java:167)
    Caused by: javax.naming.CommunicationException: zimbra.peperzaken.nl:389 [Root exception is java.net.ConnectException: Connection refused]
    	at com.sun.jndi.ldap.Connection.<init>(Connection.java:197)
    	at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:118)
    	at com.sun.jndi.ldap.LdapClientFactory.createPooledConnection(LdapClientFactory.java:46)
    	at com.sun.jndi.ldap.pool.Connections.<init>(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:2616)
    	at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:287)
    	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.<init>(InitialLdapContext.java:134)
    	at com.zimbra.cs.account.ldap.LdapUtil.getDirContext(LdapUtil.java:246)
    	... 7 more
    Caused by: java.net.ConnectException: Connection refused
    	at java.net.PlainSocketImpl.socketConnect(Native Method)
    	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
    	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
    	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
    	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
    I can see the warnings, but what is the problem. When i tail with 1000 lines i can see a repeating pattern:

    Code:
    2008-11-25 07:40:36,601 WARN  [MailboxPurge] [name=e.***@***.nl;mid=22;] purge - Unable to get mailbox id's
    com.zimbra.common.service.ServiceException: system failure: getDirectContext
    ExceptionId:MailboxPurge:1227595236601:73f3acbf3ecbade8
    And then:
    Code:
    2008-11-25 07:40:36,601 WARN  [MailboxPurge] [name=e.***@***.nl;mid=22;] purge - Unable to determine value of zimbraMailPurgeSleepInterval
    com.zimbra.common.service.ServiceException: system failure: getDirectContext
    ExceptionId:MailboxPurge:1227595236601:73f3acbf3ecbade8
    Last edited by Peperzaken; 11-25-2008 at 01:26 AM. Reason: I replaced the email address of one of our employees.

  4. #4
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    Quote Originally Posted by Peperzaken View Post
    And here the tail of the mailbox.log file:
    Code:
    	... 7 more
    Caused by: java.net.ConnectException: Connection refused
    	at java.net.PlainSocketImpl.socketConnect(Native Method)
    	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
    	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
    	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
    	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
    	at java.net.Socket.connect(Socket.java:519)
    	at sun.reflect.GeneratedMethodAccessor106.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:336)
    	at com.sun.jndi.ldap.Connection.<init>(Connection.java:184)
    	... 24 more
    2008-11-25 07:40:36,601 WARN  [MailboxPurge] [name=e.****@****.nl;mid=22;] purge - Unable to get mailbox id's
    com.zimbra.common.service.ServiceException: system failure: getDirectContext
    ExceptionId:MailboxPurge:1227595236601:73f3acbf3ecbade8
    Code:service.FAILURE
    	at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:253)
    	at com.zimbra.cs.account.ldap.LdapUtil.getDirContext(LdapUtil.java:253)
    	at com.zimbra.cs.account.ldap.LdapUtil.getDirContext(LdapUtil.java:238)
    	at com.zimbra.cs.account.ldap.LdapUtil.getDirContext(LdapUtil.java:229)
    	at com.zimbra.cs.account.ldap.LdapProvisioning.getServerByName(LdapProvisioning.java:2196)
    	at com.zimbra.cs.account.ldap.LdapProvisioning.getServerByName(LdapProvisioning.java:2185)
    	at com.zimbra.cs.account.ldap.LdapProvisioning.getLocalServer(LdapProvisioning.java:2569)
    	at com.zimbra.cs.mailbox.PurgeThread.getMailboxIds(PurgeThread.java:222)
    	at com.zimbra.cs.mailbox.PurgeThread.run(PurgeThread.java:117)
    Caused by: javax.naming.CommunicationException: zimbra.peperzaken.nl:389 [Root exception is java.net.ConnectException: Connection refused]
    	at com.sun.jndi.ldap.Connection.<init>(Connection.java:197)
    	at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:118)
    	at com.sun.jndi.ldap.LdapClientFactory.createPooledConnection(LdapClientFactory.java:46)
    	at com.sun.jndi.ldap.pool.Connections.<init>(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:2616)
    	at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:287)
    	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.<init>(InitialLdapContext.java:134)
    	at com.zimbra.cs.account.ldap.LdapUtil.getDirContext(LdapUtil.java:246)
    	... 7 more
    Caused by: java.net.ConnectException: Connection refused
    	at java.net.PlainSocketImpl.socketConnect(Native Method)
    	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
    	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
    	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
    	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
    	at java.net.Socket.connect(Socket.java:519)
    	at sun.reflect.GeneratedMethodAccessor106.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:336)
    	at com.sun.jndi.ldap.Connection.<init>(Connection.java:184)
    	... 24 more
    2008-11-25 07:40:36,601 WARN  [MailboxPurge] [name=e.***@***.nl;mid=22;] purge - Unable to determine value of zimbraMailPurgeSleepInterval
    com.zimbra.common.service.ServiceException: system failure: getDirectContext
    ExceptionId:MailboxPurge:1227595236601:73f3acbf3ecbade8
    Code:service.FAILURE
    	at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:253)
    	at com.zimbra.cs.account.ldap.LdapUtil.getDirContext(LdapUtil.java:253)
    	at com.zimbra.cs.account.ldap.LdapUtil.getDirContext(LdapUtil.java:238)
    	at com.zimbra.cs.account.ldap.LdapUtil.getDirContext(LdapUtil.java:229)
    	at com.zimbra.cs.account.ldap.LdapProvisioning.getServerByName(LdapProvisioning.java:2196)
    	at com.zimbra.cs.account.ldap.LdapProvisioning.getServerByName(LdapProvisioning.java:2185)
    	at com.zimbra.cs.account.ldap.LdapProvisioning.getLocalServer(LdapProvisioning.java:2569)
    	at com.zimbra.cs.mailbox.PurgeThread.getSleepInterval(PurgeThread.java:187)
    	at com.zimbra.cs.mailbox.PurgeThread.run(PurgeThread.java:167)
    Caused by: javax.naming.CommunicationException: zimbra.peperzaken.nl:389 [Root exception is java.net.ConnectException: Connection refused]
    	at com.sun.jndi.ldap.Connection.<init>(Connection.java:197)
    	at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:118)
    	at com.sun.jndi.ldap.LdapClientFactory.createPooledConnection(LdapClientFactory.java:46)
    	at com.sun.jndi.ldap.pool.Connections.<init>(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:2616)
    	at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:287)
    	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.<init>(InitialLdapContext.java:134)
    	at com.zimbra.cs.account.ldap.LdapUtil.getDirContext(LdapUtil.java:246)
    	... 7 more
    Caused by: java.net.ConnectException: Connection refused
    	at java.net.PlainSocketImpl.socketConnect(Native Method)
    	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
    	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
    	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
    	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
    The problem would appear to be the inability to retrieve certain attributes from LDAP as evidenced by this message:

    Code:
    Caused by: javax.naming.CommunicationException: zimbra.peperzaken.nl:389 [Root exception is java.net.ConnectException: Connection refused]
    You either have a firewall problem, SElinux is enabled or there's a DNS problem.

    Run the following commands on the Zimbra server:
    Code:
    cat /etc/hosts
    cat /etc/resolv.conf
    host `hostname`  <-- use backticks not single quotes
    dig yourdomain.com mx 
    dig yourdomain.com any
    and post the output here.

    Are you behind a NAT router? If you are, make sure that SElinux is disabled (or AppArmor) and the firewall on the Zimbra server is disabled. Do you have a local DNS server set-up? Have you always had this problem?
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

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

    Default

    Thanks Phoenix for your help!

    Here's the output.

    cat /etc/hosts
    Code:
    127.0.0.1	localhost
    10.0.0.175	zimbra.peperzaken.nl	zimbra
    # 10.0.0.175	mail.peperzaken.nl	mail
    cat /etc/resolv.conf
    Code:
    nameserver 10.0.0.175
    nameserver 10.0.0.1
    // nameserver 193.74.208.65
    // nameserver 213.51.129.37
    // nameserver 213.51.144.37
    host `hostname`
    Code:
    Host zimbra.peperzaken.nl not found: 2(SERVFAIL)
    dig peperzaken.nl mx
    Code:
    ; <<>> DiG 9.3.2 <<>> peperzaken.nl mx
    ;; global options:  printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 6540
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
    
    ;; QUESTION SECTION:
    ;peperzaken.nl.			IN	MX
    
    ;; Query time: 18 msec
    ;; SERVER: 10.0.0.175#53(10.0.0.175)
    ;; WHEN: Tue Nov 25 11:40:38 2008
    ;; MSG SIZE  rcvd: 31
    dig peperzaken.nl any
    Code:
    ; <<>> DiG 9.3.2 <<>> peperzaken.nl any
    ;; global options:  printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 65049
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
    
    ;; QUESTION SECTION:
    ;peperzaken.nl.			IN	ANY
    
    ;; Query time: 2 msec
    ;; SERVER: 10.0.0.175#53(10.0.0.175)
    ;; WHEN: Tue Nov 25 11:41:11 2008
    ;; MSG SIZE  rcvd: 31
    The only thing that seems to be wrong is the `hostname`part. Is that causing al this trouble?

  6. #6
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    25

    Default

    And that your DNS is not returning any records for your domain. As you are behind a firewall on a private LAN you will need to setup a Split DNS - Zimbra :: Wiki architecture.

  7. #7
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    Quote Originally Posted by Peperzaken View Post
    cat /etc/hosts
    Code:
    127.0.0.1	localhost
    10.0.0.175	zimbra.peperzaken.nl	zimbra
    # 10.0.0.175	mail.peperzaken.nl	mail
    The only thing that seems to be wrong is the `hostname`part. Is that causing al this trouble?
    There are two things wrong, your DNS isn't returning a valid IP address (more accurately no IP address at all) and your hosts file is incorrect. Fix the DNS with the details in the link Uxbod has provided and fix the hosts file with the detail from the Quick Start Installation Guide.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  8. #8
    Join Date
    Nov 2008
    Posts
    8
    Rep Power
    7

    Default

    Okay, think we solved the DNS errors.

    Code:
    zimbra@zimbra:/$ cat /etc/hosts
    127.0.0.1	localhost
    10.0.0.175	zimbra.peperzaken.nl
    # 10.0.0.175	mail.peperzaken.nl	mail
    
    # The following lines are desirable for IPv6 capable hosts
    ::1     ip6-localhost ip6-loopback
    fe00::0 ip6-localnet
    ff00::0 ip6-mcastprefix
    ff02::1 ip6-allnodes
    ff02::2 ip6-allrouters
    ff02::3 ip6-allhosts
    Code:
    zimbra@zimbra:/$ host `hostname`
    zimbra.peperzaken.nl has address 91.194.225.172
    Code:
    zimbra@zimbra:/$ dig peperzaken.nl mx
    
    ; <<>> DiG 9.3.2 <<>> peperzaken.nl mx
    ;; global options:  printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49453
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 1
    
    ;; QUESTION SECTION:
    ;peperzaken.nl.			IN	MX
    
    ;; ANSWER SECTION:
    peperzaken.nl.		5974	IN	MX	1 mail.rollernet.us.
    
    ;; AUTHORITY SECTION:
    peperzaken.nl.		5974	IN	NS	ns0.argewebhosting.nl.
    peperzaken.nl.		5974	IN	NS	ns3.argewebhosting.nl.
    peperzaken.nl.		5974	IN	NS	ns.argewebhosting.nl.
    
    ;; ADDITIONAL SECTION:
    mail.rollernet.us.	75970	IN	A	208.79.240.2
    
    ;; Query time: 9 msec
    ;; SERVER: 10.0.0.1#53(10.0.0.1)
    ;; WHEN: Fri Nov 28 13:21:52 2008
    ;; MSG SIZE  rcvd: 148
    Is this the way it should be with a split DNS solution? (we're behind NAT).

  9. #9
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    Your hosts file is still slightly wrong, this line

    Code:
    10.0.0.175	zimbra.peperzaken.nl
    should be like this
    Code:
    10.0.0.175	zimbra.peperzaken.nl zimbra
    The results from your DNS are incorrect, they should point to the LAN IP of your Zimbra server, you seem to get conflicting results from the 'host `hostname`' command and the dig output. Does the output of this command:

    Code:
    cat /etc/resolv.conf
    give you the IP of your LAN server only?
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  10. #10
    Join Date
    Nov 2008
    Posts
    8
    Rep Power
    7

    Default

    Quote Originally Posted by phoenix View Post
    Your hosts file is still slightly wrong, this line

    Code:
    10.0.0.175	zimbra.peperzaken.nl
    should be like this
    Code:
    10.0.0.175	zimbra.peperzaken.nl zimbra
    Fixed.
    The results from your DNS are incorrect, they should point to the LAN IP of your Zimbra server, you seem to get conflicting results from the 'host `hostname`' command and the dig output. Does the output of this command:

    Code:
    cat /etc/resolv.conf
    give you the IP of your LAN server only?
    I deleted the 10.0.0.1 (router) entry and now 10.0.0.175 is the only nameserver IP. But the Zimbra server could not be reached:

    Code:
    root@zimbra:/etc/bind# host `hostname`
    ;; connection timed out; no servers could be reached
    What could be wrong and should be the solution to fix this?

Similar Threads

  1. Replies: 8
    Last Post: 01-12-2012, 02:20 AM
  2. [SOLVED] parts_decode_ext error
    By jsabater in forum Administrators
    Replies: 7
    Last Post: 10-13-2008, 08:24 AM
  3. slapd message error
    By smoke in forum Administrators
    Replies: 7
    Last Post: 04-27-2008, 04:23 PM
  4. Replies: 9
    Last Post: 03-01-2008, 08:21 PM
  5. Zimbra server crashed
    By goetzi in forum Administrators
    Replies: 6
    Last Post: 03-25-2006, 01:00 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
  •