Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Installation

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 02-12-2010, 03:22 AM
New Member
 
Posts: 4
Default [SOLVED] Problem with internal delivery/ fresh 6.05 installation

Hey there,

I performed a fresh install of zimbra (version 6.0.5_GA_2213.RHEL5_64) and set up 2 user accounts.

When I log in as the first user and try to send some email to the second (a local account) a popup menu comes up saying that the server is slow/not responding.

Any ideas?

By the way.
Code:
/var/log/zimbra.log
is empty.

Help is appreciated very much!

Dominik

Code:
zmcontrol status
Host mail.xxx.local
	antispam                Running
	antivirus               Running
	ldap                    Running
	logger                  Running
	mailbox                 Running
	mta                     Running
	snmp                    Stopped
		zmswatch is not running.
	spell                   Running
	stats                   Running
Code:
 cat /opt/zimbra/log/mailbox.log
com.zimbra.common.service.ServiceException: system failure: Unable to send message
ExceptionId:btpool0-8://192.168.200.15/service/soap/SendMsgRequest:1265971502365:964e295cee4c2e52
Code:service.FAILURE
	at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:248)
	at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:492)
	at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:308)
	at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:265)
	at com.zimbra.cs.service.mail.SendMsg.doSendMessage(SendMsg.java:189)
	at com.zimbra.cs.service.mail.SendMsg.handle(SendMsg.java:150)
	at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:419)
	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:273)
	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:157)
	at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:291)
	at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:212)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:181)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
	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:216)
	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:418)
	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:939)
	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755)
	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:409)
	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
Caused by: com.zimbra.cs.mailbox.MailSender$SafeMessagingException: Exception reading response; chained exception is:
	java.net.SocketTimeoutException: Read timed out
	at com.sun.mail.smtp.SMTPTransport.readServerResponse(SMTPTransport.java:1764)
	at com.sun.mail.smtp.SMTPTransport.close(SMTPTransport.java:823)
	at com.zimbra.cs.mailbox.MailSender.sendMessageToHost(MailSender.java:755)
	at com.zimbra.cs.mailbox.MailSender.sendMessage(MailSender.java:672)
	at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:415)
	... 39 more
Reply With Quote
  #2 (permalink)  
Old 02-12-2010, 04:02 AM
Zimbra Consultant & Moderator
 
Posts: 20,317
Default

Did you set-up a Split DNS before the installation (you should have) and is your /etc/hosts file correct as per the Quick Start Installation Guide (and the myriad of threads on these forums that cover this topic)?
__________________
Regards


Bill
Reply With Quote
  #3 (permalink)  
Old 02-12-2010, 04:08 AM
New Member
 
Posts: 4
Default

Thanks for your answer.

The hosts file is correct.

Code:
cat /etc/hosts
127.0.0.1	        localhost.localdomain	localhost
10.10.200.15	mail.connexia.local	mail
Why should I need split DNS at this stage as only local delivery is concerned?

Best!
Dominik
Reply With Quote
  #4 (permalink)  
Old 02-12-2010, 04:29 AM
Zimbra Consultant & Moderator
 
Posts: 20,317
Default

Quote:
Originally Posted by netboy1977 View Post
Why should I need split DNS at this stage as only local delivery is concerned?
Postfix requires it to be able to look-up it's IP address.
__________________
Regards


Bill
Reply With Quote
  #5 (permalink)  
Old 02-13-2010, 12:30 AM
New Member
 
Posts: 4
Default

Unfortunately local delivery is still not working:

1. After I have restarted the box and tried to send a message via zimbra web client the log shows that the web client is missing the smtp ip and port

Code:
2010-02-13 09:08:46,460 INFO  [btpool0-1://192.168.200.15/service/soap/SendMsgRequest] [name=office@mail.xxx.local;mid=4;ip=10.8.0.6;ua=ZimbraWebClient - FF3.0 (Linux)/6.0.5_GA_2213.RHEL5_64;] smtp - Sending message to MTA at null, port null: Message-ID=<1769608838.0.1266048525887.JavaMail.root@mail.xxx.local>, replyType=r
Any ideas how to fix this?

2. Unfortunately, in my split DNS scenario, bind is not working either.
a. The zimbra split DNS howto says

Code:
       Define the nameservers and the mail servers
               IN      NS      
               IN      A       
               IN      MX      10 server.example.com.
Should it be the internal IP address of localhost = 127.0.0.1 or the IP in my local private network = 10.10.200.15?

b. What is going wrong here?
Quote:
$TTL 86400
@ IN SOA @ mail.xxx.local. (
42 ; serial
21600 ; refresh after 6 hours
3600 ; retry after 1 hour
604800 ; expire after 1 week
86400 ) ; minimum TTL of 1 day

@ IN NS mail.xxx.local.
IN MX 10 mail.xxx.local.
IN A 10.10.200.15
mail IN A 10.10.200.15
Quote:
nslookup mail.xxx.local. 127.0.0.1
Server: 127.0.0.1
Address: 127.0.0.1#53

** server can't find mail.xxx.local.: NXDOMAIN



Thanks in advance!

Dominik
Reply With Quote
  #6 (permalink)  
Old 02-13-2010, 12:33 AM
Zimbra Consultant & Moderator
 
Posts: 20,317
Default

It needs to point to a LAN IP address not the loopback.
__________________
Regards


Bill
Reply With Quote
  #7 (permalink)  
Old 02-13-2010, 10:31 AM
New Member
 
Posts: 4
Default

Quote:
Originally Posted by phoenix View Post
It needs to point to a LAN IP address not the loopback.
Thanks for your help. It is working now.
There was another problem with an unstable nfs mount which caused postfix to throttle.

Kind regards,

Dominik
Reply With Quote
  #8 (permalink)  
Old 02-13-2010, 10:56 AM
Zimbra Consultant & Moderator
 
Posts: 20,317
Default

Glad you've fixed it.

Quote:
Originally Posted by netboy1977 View Post
There was another problem with an unstable nfs mount which caused postfix to throttle.
NFS mounts are not recommended for any part of the /opt/zimbra directory structure.
__________________
Regards


Bill

Last edited by phoenix; 02-26-2010 at 11:41 PM..
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.