Zimbra Collaboration Suite Appliance died on me

Running our Appliance (ZCA), ZCS on VMware, or any other virtual machine software? Post your thoughts here.
alex vmguru.nl
Posts: 10
Joined: Sat Sep 13, 2014 1:38 am

Zimbra Collaboration Suite Appliance died on me

Postby alex vmguru.nl » Tue Oct 26, 2010 6:01 pm

hello folks,
I'm having a serious issue here.
We run the appliance version of Zimbra 6.07. Everything was running fine until I noticed today that some mails were bounced. I tried to open the GUI management console and got nothing. It waited forever for the services status to display but nothing happened. So finally, I decided to reboot the appliance.
After the reboot, I suddenly was welcomed with 'localhost.localdomain'. This is NOT good. After a bit of trouble shooting I noticed that the localconfig.xml could not be found according to the logs. The file was there, but it was empty???? I copied a backup copy into place but I'm still stuck here. Nothing is working.
I tried the troubleshooting tips from alot of posts around here (DNS, MX, hosts file, resolv.conf) All naming related things seem to be ok, zmsshkeygen pukes me an error message which I think could be related.
Generating public/private dsa key pair.

Your identification has been saved in /opt/zimbra/.ssh/zimbra_identity.

Your public key has been saved in /opt/zimbra/.ssh/zimbra_identity.pub.

The key fingerprint is:

6e:1b:b2:36:03:93:85:7a:de:62:b3:89:79:49:bd:bd zimbra.infra.local

ERROR: service.FAILURE (system failure: unable to lookup server by name: zimbra.infra.local message: [LDAP: error code 49 - Invalid Credentials]) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
also, the mailbox.log has some nice things:

2010-10-26 22:35:52,899 INFO [ImapServer-10546] [] imap - [172.16.1.11] connected

2010-10-26 22:35:52,900 INFO [Pop3Server-11147] [ip=172.16.1.11;] pop - connected

2010-10-26 22:35:52,907 INFO [Pop3Server-11147] [ip=172.16.1.11;] pop - quit from client

2010-10-26 22:35:52,908 INFO [Pop3Server-11147] [] ProtocolHandler - Handler exiting normally

2010-10-26 22:35:52,914 INFO [ImapServer-10546] [] ProtocolHandler - Handler exiting normally

2010-10-26 22:35:52,973 INFO [btpool0-2511://localhost:7071/service/admin/soap/GetDomainInfoRequest] [ip=127.0.0.1;] soap - GetDomainInfoRequest

2010-10-26 22:35:53,024 INFO [btpool0-2511://localhost:7071/service/admin/soap/GetDomainInfoRequest] [ip=127.0.0.1;] soap - GetDomainInfoRequest

2010-10-26 22:36:21,461 INFO [btpool0-2509://zimbra.vmguru.nl/service/soap/] [name=meagain@vmguru.nl;mid=12;ip=86.82.120.204;ua=Zimbra Desktop/1.0.4_1833_Mac;] soap - GetInfoRequest

2010-10-26 22:37:20,812 INFO [Shutdown] [] log - Shutdown hook executing

2010-10-26 22:37:21,610 INFO [Shutdown] [] StatsImageServlet - Servlet StatsImageServlet shutting down

2010-10-26 22:37:21,610 INFO [Shutdown] [] FileUploadServlet - Servlet FileUploadServlet shutting down

2010-10-26 22:37:21,610 INFO [Shutdown] [] PublicICalServlet - Servlet PublicICalServlet shutting down

2010-10-26 22:37:21,610 INFO [Shutdown] [] account - Servlet PreAuthServlet shutting down

2010-10-26 22:37:21,610 INFO [Shutdown] [] mailbox - Servlet UserServlet shutting down

2010-10-26 22:37:21,610 INFO [Shutdown] [] ContentServlet - Servlet ContentServlet shutting down

2010-10-26 22:37:21,610 INFO [Shutdown] [] soap - Servlet AdminServlet shutting down

2010-10-26 22:37:21,610 INFO [Shutdown] [] TcpServer/7025 - LmtpServer initiating shutdown

2010-10-26 22:37:21,610 INFO [MailboxPurge] [] purge - Shutting down purge thread.

2010-10-26 22:37:21,631 INFO [Shutdown] [] TcpServer/7025 - LmtpServer shutting down idle thread pool

2010-10-26 22:37:21,631 INFO [Shutdown] [] TcpServer/110 - Pop3Server initiating shutdown

2010-10-26 22:37:21,631 INFO [Shutdown] [] TcpServer/110 - Pop3Server shutting down idle thread pool

2010-10-26 22:37:21,631 INFO [Shutdown] [] TcpServer/995 - Pop3SSLServer initiating shutdown

2010-10-26 22:37:21,611 INFO [LmtpServer] [] TcpServer/7025 - finished accept loop

2010-10-26 22:37:21,631 INFO [Pop3Server] [] TcpServer/110 - finished accept loop

2010-10-26 22:37:21,631 INFO [Pop3SSLServer] [] TcpServer/995 - finished accept loop

2010-10-26 22:37:21,675 INFO [Shutdown] [] TcpServer/995 - Pop3SSLServer shutting down idle thread pool

2010-10-26 22:37:21,675 INFO [Shutdown] [] TcpServer/143 - ImapServer initiating shutdown

2010-10-26 22:37:21,675 INFO [Shutdown] [] TcpServer/143 - ImapServer shutting down idle thread pool

2010-10-26 22:37:21,675 INFO [Shutdown] [] TcpServer/993 - ImapSSLServer initiating shutdown

2010-10-26 22:37:21,675 INFO [Shutdown] [] ProtocolHandler - graceful shutdown requested

2010-10-26 22:37:21,675 INFO [ImapServer] [] TcpServer/143 - finished accept loop

2010-10-26 22:37:21,675 INFO [ImapSSLServer] [] TcpServer/993 - finished accept loop

2010-10-26 22:37:25,771 WARN [Shutdown] [] session - exception recording unloaded session's RECENT limit

com.zimbra.common.service.ServiceException: system failure: getting database connection

ExceptionId:Shutdown:1288125445770:050c902ea1947ab8

Code:service.FAILURE

at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:248)

at com.zimbra.cs.db.DbPool.getConnection(DbPool.java:328)

at com.zimbra.cs.mailbox.Mailbox$MailboxChange.getConnection(Mailbox.java:310)

at com.zimbra.cs.mailbox.Mailbox.getOperationConnection(Mailbox.java:1130)

at com.zimbra.cs.db.DbMailItem.saveMetadata(DbMailItem.java:670)

at com.zimbra.cs.mailbox.MailItem.saveMetadata(MailItem.java:2856)

at com.zimbra.cs.mailbox.MailItem.saveMetadata(MailItem.java:2849)

at com.zimbra.cs.mailbox.Folder.checkpointRECENT(Folder.java:565)

at com.zimbra.cs.mailbox.Mailbox.recordImapSession(Mailbox.java:2436)

at com.zimbra.cs.imap.ImapFolder.snapshotRECENT(ImapFolder.java:154)

at com.zimbra.cs.imap.ImapFolder.unregister(ImapFolder.java:143)

at com.zimbra.cs.imap.ImapHandler.unsetSelectedFolder(ImapHandler.java:825)

at com.zimbra.cs.imap.TcpImapHandler.dropConnection(TcpImapHandler.java:155)

at com.zimbra.cs.imap.ImapHandler.dropConnection(ImapHandler.java:3719)

at com.zimbra.cs.tcpserver.ProtocolHandler.hardShutdown(ProtocolHandler.java:246)

at com.zimbra.cs.tcpserver.ProtocolHandler.gracefulShutdown(ProtocolHandler.java:237)

at com.zimbra.cs.tcpserver.TcpServer.shutdownActiveHandlers(TcpServer.java:116)

at com.zimbra.cs.tcpserver.TcpServer.shutdown(TcpServer.java:147)

at com.zimbra.cs.tcpserver.TcpServer.shutdown(TcpServer.java:131)

at com.zimbra.cs.imap.ImapServer.shutdownImapServers(ImapServer.java:111)

at com.zimbra.cs.util.Zimbra.shutdown(Zimbra.java:299)

at com.zimbra.soap.SoapServlet.destroy(SoapServlet.java:138)

at org.mortbay.jetty.servlet.ServletHolder.destroyInstance(ServletHolder.java:318)

at org.mortbay.jetty.servlet.ServletHolder.doStop(ServletHolder.java:289)

at org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:76)

at org.mortbay.jetty.servlet.ServletHandler.doStop(ServletHandler.java:174)

at org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:76)

at org.mortbay.jetty.handler.HandlerWrapper.doStop(HandlerWrapper.java:142)

at org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:76)

at org.mortbay.jetty.handler.HandlerWrapper.doStop(HandlerWrapper.java:142)

at org.mortbay.jetty.servlet.SessionHandler.doStop(SessionHandler.java:125)

at org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:76)

at org.mortbay.jetty.handler.HandlerWrapper.doStop(HandlerWrapper.java:142)

at org.mortbay.jetty.handler.ContextHandler.doStop(ContextHandler.java:591)

at org.mortbay.jetty.webapp.WebAppContext.doStop(WebAppContext.java:505)

at org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:76)

at org.mortbay.jetty.handler.HandlerCollection.doStop(HandlerCollection.java:169)

at org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:76)

at org.mortbay.jetty.handler.HandlerCollection.doStop(HandlerCollection.java:169)

at org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:76)

at org.mortbay.jetty.handler.HandlerWrapper.doStop(HandlerWrapper.java:142)

at org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:76)

at org.mortbay.jetty.handler.HandlerWrapper.doStop(HandlerWrapper.java:142)

at org.mortbay.jetty.handler.DebugHandler.doStop(DebugHandler.java:135)

at org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:76)

at org.mortbay.jetty.handler.HandlerWrapper.doStop(HandlerWrapper.java:142)

at org.mortbay.jetty.Server.doStop(Server.java:283)

at org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:76)

at org.mortbay.jetty.Server$ShutdownHookThread.run(Server.java:561)

Caused by: com.mysql.jdbc.exceptions.MySQLNonTransientConnectionException: Server connection failure during transaction. Due to underlying exception: 'java.net.ConnectException: Connection refused'.
** BEGIN NESTED EXCEPTION **
java.net.ConnectException

MESSAGE: Connection refused
STACKTRACE:
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:525)

at java.net.Socket.connect(Socket.java:475)

at java.net.Socket.(Socket.java:372)

at java.net.Socket.(Socket.java:215)

at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:256)

at com.mysql.jdbc.MysqlIO.(MysqlIO.java:271)

at com.mysql.jdbc.Connection.createNewIO(Connection.java:2921)

at com.mysql.jdbc.Connection.(Connection.java:1555)

at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:285)

at java.sql.DriverManager.getConnection(DriverManager.java:582)

at java.sql.DriverManager.getConnection(DriverManager.java:154)

at org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:68)

at com.zimbra.cs.db.DbPool$ZimbraConnectionFactory.createConnection(DbPool.java:239)

at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:294)

at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1148)

at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:96)

at com.zimbra.cs.db.DbPool.getConnection(DbPool.java:309)

at com.zimbra.cs.mailbox.Mailbox$MailboxChange.getConnection(Mailbox.java:310)

at com.zimbra.cs.mailbox.Mailbox.getOperationConnection(Mailbox.java:1130)

at com.zimbra.cs.db.DbMailItem.saveMetadata(DbMailItem.java:670)

at com.zimbra.cs.mailbox.MailItem.saveMetadata(MailItem.java:2856)

at com.zimbra.cs.mailbox.MailItem.saveMetadata(MailItem.java:2849)

at com.zimbra.cs.mailbox.Folder.checkpointRECENT(Folder.java:565)

at com.zimbra.cs.mailbox.Mailbox.recordImapSession(Mailbox.java:2436)

at com.zimbra.cs.imap.ImapFolder.snapshotRECENT(ImapFolder.java:154)

at com.zimbra.cs.imap.ImapFolder.unregister(ImapFolder.java:143)

at com.zimbra.cs.imap.ImapHandler.unsetSelectedFolder(ImapHandler.java:825)

at com.zimbra.cs.imap.TcpImapHandler.dropConnection(TcpImapHandler.java:155)

at com.zimbra.cs.imap.ImapHandler.dropConnection(ImapHandler.java:3719)

at com.zimbra.cs.tcpserver.ProtocolHandler.hardShutdown(ProtocolHandler.java:246)

at com.zimbra.cs.tcpserver.ProtocolHandler.gracefulShutdown(ProtocolHandler.java:237)

at com.zimbra.cs.tcpserver.TcpServer.shutdownActiveHandlers(TcpServer.java:116)

at com.zimbra.cs.tcpserver.TcpServer.shutdown(TcpServer.java:147)

at com.zimbra.cs.tcpserver.TcpServer.shutdown(TcpServer.java:131)

at com.zimbra.cs.imap.ImapServer.shutdownImapServers(ImapServer.java:111)

at com.zimbra.cs.util.Zimbra.shutdown(Zimbra.java:299)

at com.zimbra.soap.SoapServlet.destroy(SoapServlet.java:138)

at org.mortbay.jetty.servlet.ServletHolder.destroyInstance(ServletHolder.java:318)

at org.mortbay.jetty.servlet.ServletHolder.doStop(ServletHolder.java:289)

at org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:76)

at org.mortbay.jetty.servlet.ServletHandler.doStop(ServletHandler.java:174)

at org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:76)

at org.mortbay.jetty.handler.HandlerWrapper.doStop(HandlerWrapper.java:142)

at org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:76)

at org.mortbay.jetty.handler.HandlerWrapper.doStop(HandlerWrapper.java:142)

at org.mortbay.jetty.servlet.SessionHandler.doStop(SessionHandler.java:125)

at org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:76)

at org.mortbay.jetty.handler.HandlerWrapper.doStop(HandlerWrapper.java:142)

at org.mortbay.jetty.handler.ContextHandler.doStop(ContextHandler.java:591)

at org.mortbay.jetty.webapp.WebAppContext.doStop(WebAppContext.java:505)

at org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:76)

at org.mortbay.jetty.handler.HandlerCollection.doStop(HandlerCollection.java:169)

at org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:76)

at org.mortbay.jetty.handler.HandlerCollection.doStop(HandlerCollection.java:169)

at org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:76)

at org.mortbay.jetty.handler.HandlerWrapper.doStop(HandlerWrapper.java:142)

at org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:76)

at org.mortbay.jetty.handler.HandlerWrapper.doStop(HandlerWrapper.java:142)

at org.mortbay.jetty.handler.DebugHandler.doStop(DebugHandler.java:135)

at org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:76)

at org.mortbay.jetty.handler.HandlerWrapper.doStop(HandlerWrapper.java:142)

at org.mortbay.jetty.Server.doStop(Server.java:283)

at org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:76)

at org.mortbay.jetty.Server$ShutdownHookThread.run(Server.java:561)


** END NESTED EXCEPTION **


Attempted reconnect 3 times. Giving up.

at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:888)

at com.mysql.jdbc.Connection.createNewIO(Connection.java:2997)

at com.mysql.jdbc.Connection.(Connection.java:1555)

at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:285)

at java.sql.DriverManager.getConnection(DriverManager.java:582)

at java.sql.DriverManager.getConnection(DriverManager.java:154)

at org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:68)

at com.zimbra.cs.db.DbPool$ZimbraConnectionFactory.createConnection(DbPool.java:239)

at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:294)

at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1148)

at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:96)

at com.zimbra.cs.db.DbPool.getConnection(DbPool.java:309)

... 47 more

2010-10-26 22:37:25,792 INFO [Shutdown] [] ProtocolHandler - graceful shutdown requested

2010-10-26 22:37:25,811 INFO [Shutdown] [] ProtocolHandler - graceful shutdown requested
So, it just died and now I have a box of fragments. Plz help me out here cos it's our production mail server so basically we're down as far as mail is concerned.
Greatly appreciate help
cheers,

Alex


alex vmguru.nl
Posts: 10
Joined: Sat Sep 13, 2014 1:38 am

Zimbra Collaboration Suite Appliance died on me

Postby alex vmguru.nl » Wed Oct 27, 2010 12:36 am

small addition: when I try to start the server daemons, the following output is displayed:

Host zimbra.infra.local

Unable to determine enabled services from ldap.

Unable to determine enabled services. Cache is out of date or doesn't exist

[fail]
phoenix
Ambassador
Ambassador
Posts: 26342
Joined: Fri Sep 12, 2014 9:56 pm
Location: Liverpool, England

Zimbra Collaboration Suite Appliance died on me

Postby phoenix » Wed Oct 27, 2010 12:52 am

[quote user="alex vmguru.nl"]small addition: when I try to start the server daemons, the following output is displayed:

Host zimbra.infra.local

Unable to determine enabled services from ldap.

Unable to determine enabled services. Cache is out of date or doesn't exist

[fail][/QUOTE]That error is usually caused by a DNS error or an incorrect /etc/hosts file, go to the Split DNS article and in the 'Verify...' section you'll see details on how to check the DNS records and the format of the hosts file.
Regards

Bill

Rspamd: A high performance spamassassin replacement

If you'd like to see this implemented in a future version of ZCS then please vote on Bugzilla entries 97706 & 108168
alex vmguru.nl
Posts: 10
Joined: Sat Sep 13, 2014 1:38 am

Zimbra Collaboration Suite Appliance died on me

Postby alex vmguru.nl » Wed Oct 27, 2010 1:03 am

Goodmorning Bill,
It would be odd as Zimbra has worked fine for us for more than 3 months. As far as I can tell, all is well in the named department. The server isn't published with a public name to the internet but behind a firewall and a spam gateway.
As mentioned, it worked perfectly before.
Name Resolution Tests:

zimbra@zimbra:~$ hostname

zimbra.infra.local

zimbra@zimbra:~$ cat /etc/hosts

127.0.0.1 localhost.localdomain localhost

172.16.1.12 zimbra.infra.local

zimbra@zimbra:~$ cat /etc/resolv.conf

search infra.local

nameserver 172.16.1.254

nameserver 8.8.8.8

zimbra@zimbra:~$ host `hostname`

zimbra.infra.local has address 172.16.1.12
phoenix
Ambassador
Ambassador
Posts: 26342
Joined: Fri Sep 12, 2014 9:56 pm
Location: Liverpool, England

Zimbra Collaboration Suite Appliance died on me

Postby phoenix » Wed Oct 27, 2010 1:21 am

How about the output of the dig commands just for completeness? You should also only have one DNS server in your resolve.conf unless both of your DNS server have identical records for the Zimbra server.
Regards

Bill

Rspamd: A high performance spamassassin replacement

If you'd like to see this implemented in a future version of ZCS then please vote on Bugzilla entries 97706 & 108168
alex vmguru.nl
Posts: 10
Joined: Sat Sep 13, 2014 1:38 am

Zimbra Collaboration Suite Appliance died on me

Postby alex vmguru.nl » Wed Oct 27, 2010 1:24 am

Bill,
the internal domain "infra.local" does not have an MX entry. The domains that run on the zimbra appliance (or should I say ran) have an MX entry that point to the external IP address of the firewall.
Does Zimbra need to be able to resolve any hosted domains to the internal IP address?
phoenix
Ambassador
Ambassador
Posts: 26342
Joined: Fri Sep 12, 2014 9:56 pm
Location: Liverpool, England

Zimbra Collaboration Suite Appliance died on me

Postby phoenix » Wed Oct 27, 2010 1:48 am

[quote user="alex vmguru.nl"]Bill,
the internal domain "infra.local" does not have an MX entry. The domains that run on the zimbra appliance (or should I say ran) have an MX entry that point to the external IP address of the firewall.
Does Zimbra need to be able to resolve any hosted domains to the internal IP address?[/QUOTE]Yes, it does and you should have an A & MX records pointing at the lan IP server.
Regards

Bill

Rspamd: A high performance spamassassin replacement

If you'd like to see this implemented in a future version of ZCS then please vote on Bugzilla entries 97706 & 108168
alex vmguru.nl
Posts: 10
Joined: Sat Sep 13, 2014 1:38 am

Zimbra Collaboration Suite Appliance died on me

Postby alex vmguru.nl » Wed Oct 27, 2010 1:51 am

Bill,
so, basically, what you're saying is that Zimbra needs to resolve all hosted domains via (local) dns to it's own (internal) IP. Odd then that the appliance version does not have a Bind instance installed.
I need to move to a different location now, I will be back in approx 2 hours. I will then install Bind on the local machine and configure the hosted domains. Do I need to put an MX record in for the local domain "infra.local" as well?
Cheers and thanks for your help!
Alex
phoenix
Ambassador
Ambassador
Posts: 26342
Joined: Fri Sep 12, 2014 9:56 pm
Location: Liverpool, England

Zimbra Collaboration Suite Appliance died on me

Postby phoenix » Wed Oct 27, 2010 5:21 am

[quote user="alex vmguru.nl"]Bill,
so, basically, what you're saying is that Zimbra needs to resolve all hosted domains via (local) dns to it's own (internal) IP.[/QUOTE]You only need the DNS A & MX records for the primary domain on the Zimbra server.
[quote user="alex vmguru.nl"]Odd then that the appliance version does not have a Bind instance installed.[/QUOTE]That's for flexibility, you don't specifically need the DNS server on the appliance or on the 'normal' Zimbra server. If you already have a DNS server in your LAN then feel free to use that, the Split DNS article is just one example of how to set-up that facility.
[quote user="alex vmguru.nl"] I need to move to a different location now, I will be back in approx 2 hours. I will then install Bind on the local machine and configure the hosted domains. Do I need to put an MX record in for the local domain "infra.local" as well?[/QUOTE]If that's the primary domain then, yes you'll need the records for that (as I mentioned above).
Regards

Bill

Rspamd: A high performance spamassassin replacement

If you'd like to see this implemented in a future version of ZCS then please vote on Bugzilla entries 97706 & 108168
alex vmguru.nl
Posts: 10
Joined: Sat Sep 13, 2014 1:38 am

Zimbra Collaboration Suite Appliance died on me

Postby alex vmguru.nl » Wed Oct 27, 2010 6:22 am

ok, so I just installed BIND9 on the appliance, added the zone files, checked the config, dig works fine for infra.local and vmguru.nl and points to the local IP:


root@zimbra:/var/log# dig infra.local mx
; <<>> DiG 9.4.2-P2.1 <<>> infra.local mx

;; global options: printcmd

;; Got answer:

;; ->>HEADER<
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1
;; QUESTION SECTION:

;infra.local. IN MX
;; ANSWER SECTION:

infra.local. 86400 IN MX 10 zimbra.infra.local.
;; AUTHORITY SECTION:

infra.local. 86400 IN NS zimbra.infra.local.
;; ADDITIONAL SECTION:

zimbra.infra.local. 86400 IN A 172.16.1.12
;; Query time: 0 msec

;; SERVER: 172.16.1.12#53(172.16.1.12)

;; WHEN: Wed Oct 27 13:21:00 2010

;; MSG SIZE rcvd: 82
Zimbra still refuses service however. How do we proceed from here?

Return to “Virtualization”

Who is online

Users browsing this forum: No registered users and 6 guests