Installation of Zimbra on Amazon EC2

[trident4172]

I am using the following image at Amazon EC2.
Amazon Web Services Developer Connection : RightImage: CentOS 5 Base, Version 1
I am following this guide Centos 5 Install Guide

I am installing zimbra-core-4.5.6_GA_1044.RHEL5 .

I have uninstalled postfix and resolved port conflict on port 25. I have installed the dependencies using yum install [package name].

I need to resolve this error - yes, DNS. I have ready everything in the forum (split dns etc). I need specific help.

For confidentialty, I will replace my domain name with domain.com

My EC2 instance has the following:
public dns name: ec2-67-202-13-130.z-1.compute-1.amazonaws.com (also has ip address of 67.202.13.130)
private dns name (within EC2) domU-12-31-36-00-18-C4.z-1.compute-1.internal

I have a domain name with an MX record pointing to an A record which contains the IP address of the instance. I use DNS Made Easy and have full control over DNS server entries. For testing, I have also pointed all CNAME (*, WWW, WEBMAIL) to the same IP address of the EC2/Zimbra instance.

Specifically, I think I need help with my /etc/hosts file.

My /etc/hosts file has the following content:
127.0.0.1 localhost localhost.localdomain
67.202.13.130 domain.com

I have also tried /etc/hosts
127.0.0.1 localhost localhost.localdomain
67.202.13.130 mail.domain.com

The hostname command returns the following:
domU-12-31-36-00-18-C4

The specific error during installation is:
DNS ERROR resolving MX for domu-12-31-36-00-C4.z-1.compute-1.internal
Is is suggested that the domain name have an MX record configured in DNS
Change domain name? [Yes] y
Create Domain [domU-12-31-36-00-C4.z-1.compute-1.internal] domain.com
MX: mail.domain.com (67.202.13.130)
Interface: 10.253.31.50
Interface: 127.0.0.1
DNS ERROR - none of the MX records for domain.com resolve to this host
Re-Enter domain name? [Yes]

As above, I have entered my domain.com domain and it can not resolve the MX record. I assume that it would say "success" if everything was OK.

Is this my hosts file? What is the correct structure?

If I proceed with the installation, then the next error that I get is:
Initializing ldap...Failed to start slapd. Attempting debug start to determine error.
daemon: bind(6) failed errno=99 (Cannot assign requested address)
slap_open_listener: failed on ldap://domain.com:389

FAILED (1)

[phoenix]

Your hosts file is incorrect, check the Quick Start Installation Guide or search the forums for the format. You'll also need a Split DNS set-up if your on a private IP address.

[jholder]

Originally Posted by trident4172

I am using the following image at Amazon EC2.
Amazon Web Services Developer Connection : RightImage: CentOS 5 Base, Version 1
I am following this guide Centos 5 Install Guide

I am installing zimbra-core-4.5.6_GA_1044.RHEL5 .

I have uninstalled postfix and resolved port conflict on port 25. I have installed the dependencies using yum install [package name].

I need to resolve this error - yes, DNS. I have ready everything in the forum (split dns etc). I need specific help.

For confidentialty, I will replace my domain name with domain.com

My EC2 instance has the following:
public dns name: ec2-67-202-13-130.z-1.compute-1.amazonaws.com (also has ip address of 67.202.13.130)
private dns name (within EC2) domU-12-31-36-00-18-C4.z-1.compute-1.internal

I have a domain name with an MX record pointing to an A record which contains the IP address of the instance. I use DNS Made Easy and have full control over DNS server entries. For testing, I have also pointed all CNAME (*, WWW, WEBMAIL) to the same IP address of the EC2/Zimbra instance.

Specifically, I think I need help with my /etc/hosts file.

My /etc/hosts file has the following content:
127.0.0.1 localhost localhost.localdomain
67.202.13.130 domain.com

I have also tried /etc/hosts
127.0.0.1 localhost localhost.localdomain
67.202.13.130 mail.domain.com

The hostname command returns the following:
domU-12-31-36-00-18-C4

The specific error during installation is:
DNS ERROR resolving MX for domu-12-31-36-00-C4.z-1.compute-1.internal
Is is suggested that the domain name have an MX record configured in DNS
Change domain name? [Yes] y
Create Domain [domU-12-31-36-00-C4.z-1.compute-1.internal] domain.com
MX: mail.domain.com (67.202.13.130)
Interface: 10.253.31.50
Interface: 127.0.0.1
DNS ERROR - none of the MX records for domain.com resolve to this host
Re-Enter domain name? [Yes]

As above, I have entered my domain.com domain and it can not resolve the MX record. I assume that it would say "success" if everything was OK.

Is this my hosts file? What is the correct structure?

If I proceed with the installation, then the next error that I get is:
Initializing ldap...Failed to start slapd. Attempting debug start to determine error.
daemon: bind(6) failed errno=99 (Cannot assign requested address)
slap_open_listener: failed on ldap://domain.com:389

FAILED (1)

We actually have a super secret installation of Zimbra on EC2. Forum member "SuperMario" would be the one who set that up. I'll let him know about this thread.

[SuperMario]

This isn't an EC2 issue per se, but an issue directly related to how you've setup the /etc/hosts file

I think that your best option is to set your internal EC2 instance name to point to your DNS record. This way the EC2 network doing the routing will be configured to route through your DNS if I understand the /etc/host file correctly.

I think that the best way to troubleshoot this problem is to make sure that you're always correctly pointing your DNS entries in your EC2 instance to the domain DNS entries routing your hostname.

[Klug]

You're using EC2 with S3 ?

[trident4172]

I have access to S3 but am not using it at this stage. S3 will primarily be used for server backups.

[trident4172]

I have tried the following layout of the /etc/hosts file:
127.0.0.1 localhost localhost.localdomain
67.202.13.130 mail.domain.com mail

Can anyone suggest a hosts file for me given the details above?

Please confirm a split DNS is required to get Zimbra working on EC2 (and I will then learn commit to learning a new skill)

[jholder]

Originally Posted by trident4172

I have tried the following layout of the /etc/hosts file:
127.0.0.1 localhost localhost.localdomain
67.202.13.130 mail.domain.com mail

Can anyone suggest a hosts file for me given the details above?

Please confirm a split DNS is required to get Zimbra working on EC2 (and I will then learn commit to learning a new skill)

Should be
127.0.0.1 localhost.localdomain localhost
[internal ip] domU-12-31-36-00-18-C4.z-1.compute-1.internal domu-12-31-36-00-18-C4

[SuperMario]

try putting your dom1.internal.* hostname behind the localhost directive

or just what ^ said

[trident4172]

I have the following in my hosts file:
127.0.0.1 localhost.localdomain localhost
10.253.31.50 domU-12-31-36-00-18-C4.z-1.compute-1.internal domU-12-31-36-00-18-C4

I think this was the internal IP address you referred to above. I inferred it from the MX lookup information.

I let it proceed past the MX record lookup error.

If I type domain.com as the host name, I get the following error:
Initializing ldap...Failed to start slapd. Attempting debug start to determine error.
daemon:bind(6) failed errno=99 (Cannot assign requested address)
slap_open_listener:failed on ldap://domain.com:389

If I leave the hostname at the default (domU-12-36-00-18-C4.z-1.compute-1.internal) Zimbra is successfully installed (once).

For 30 minutes last night, I logged into Zimbra Admin and the user console. The only noticeable issue was the it said logger was not operating. I could not test whether it was working or not. Unfortunately, I rebooted the instance and zimbra ceased to work (with zmcontrol and zmstart outcomes below). I have been unable to reproduce a working Zimbra (hosts file has not been changed / leave default hostname).

Zmcontrol status reveals:
Host domu-12-31-36-00-18-c4.z-1.compute-1.internal
antispam stopped
zmmtaconfigctl is not running
zmamavisdctl is not running
antivirus stopped
zmmtaconfigctl is not running
zmamavisdctl is not running
zmclamdctl is not running
ldap running
logger stopped
zmlogswatchctl is not running
mailbox stopped
zmmtaconfigctl is not running
mta stopped
zmmtaconfigchctl is not running
postfix is not running
zmsaslauthdctl is not running
snmp stopped
swatch is not running
spell stopped
zmapachectl is not running

zmcontrol start results
no connection to syslog available
- /dev/log is not a socket at /opt/zimbra/zimbramon/lib/Zimbra/Mon/Logger.pm line 51

It sort of worked for a while. I really appreciate your help any ideas?

What EC2 instance and Zimbra versions have been successful on EC2?