MTA Service Stopped

[Ryan Frantz]

I followed the instructions in this post:
http://www.zimbra.com/forums/showth...ght=install+FC4

to install the latest version of the Network Edition on my freshly installed FC4 box (using zcs-NETWORK-3.0.0_M2_744.RHEL4.tgz).

The installation was successful and I followed steps in this post to get the MTA service running:

MTA: Stopped --> Problem with amavisd, BerkeleyDB & libdb-4.2.so

However, the admin console shows that 'mta' is running (everything but 'spell' is running) but 'zmcontrol status' does not:

antispam Stopped
antivirus Stopped
ldap Running
logger Running
mailbox Stopped
mta Stopped
snmp Running
spell Stopped

What gives?

[KevinH]

Please look in your /tmp/install.log that may give us some clues.

[Ryan Frantz]

From: /tmp/install.log.32074:

Preparing packages for installation...
zimbra-core-3.0.0_M2_744.RHEL4-20051116095201
cat: /opt/zimbra/zimbramon/zimbra.cf.in: No such file or directory
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.C
ommunicationException localhost:389)
Preparing packages for installation...
zimbra-ldap-3.0.0_M2_744.RHEL4-20051116095201
cat: /opt/zimbra/zimbramon/zimbraldap.cf: No such file or directory
Preparing packages for installation...
zimbra-logger-3.0.0_M2_744.RHEL4-20051116095201
cat: /opt/zimbra/zimbramon/zimbralogger.cf: No such file or directory
Preparing packages for installation...
zimbra-mta-3.0.0_M2_744.RHEL4-20051116095201
cat: /opt/zimbra/zimbramon/zimbramta.cf: No such file or directory
Preparing packages for installation...
zimbra-snmp-3.0.0_M2_744.RHEL4-20051116095201
cat: /opt/zimbra/zimbramon/zimbrasnmp.cf: No such file or directory
Preparing packages for installation...
zimbra-store-3.0.0_M2_744.RHEL4-20051116095201
cat: /opt/zimbra/zimbramon/zimbramail.cf: No such file or directory
Preparing packages for installation...
zimbra-apache-3.0.0_M2_744.RHEL4-20051116095201
Preparing packages for installation...
zimbra-spell-3.0.0_M2_744.RHEL4-20051116095201

From /opt/zimbra/config.447:

HOSTNAME=zimbra.informeddom.com
IMAPPORT=143
IMAPSSLPORT=993
LDAPHOST=zimbra.informeddom.com
LDAPPORT=389
MODE=http
POPPORT=110
POPSSLPORT=995
REMOVE=no
RUNAV=yes
RUNSA=yes
SMTPDEST=admin@zimbra.informeddom.com
SMTPHOST=zimbra.informeddom.com
SMTPNOTIFY=yes
SMTPSOURCE=admin@zimbra.informeddom.com
SNMPNOTIFY=yes
SNMPTRAPHOST=zimbra.informeddom.com
SPELLURL=http://zimbra.informeddom.com:7780/aspell.php
STARTSERVERS=yes
UPGRADE=yes
USESPELL=yes
INSTALL_PACKAGES="zimbra-apache zimbra-core zimbra-ldap zimbra-logger zimbra-mta zimbra-snmp zimbra-spell zimbra-store "

Other than the java error, I found nothing major in the logs. Nothing in /var/log/zimbra.log either...

[KevinH]

Well that Java error is pretty major. Means LDAP never started. Did you only try to install once?

[Ryan Frantz]

Originally Posted by KevinH

Well that Java error is pretty major. Means LDAP never started. Did you only try to install once?

Yes, I only ran the installation once.

And the LDAP service is running...

[goetzi]

Just search on the forums. Several people had this problem before.

I think your /etc/hosts isn't correct. What do you have in there? It should look like:

127.0.0.1 localhost.localdomain localhost
192.168.1.157 mail.example.com mail

The first line exactly like this. The second line with the IP adress, the FQDN and the hostname of the machine.

[Ryan Frantz]

Originally Posted by goetzi

Just search on the forums. Several people had this problem before.

I think your /etc/hosts isn't correct. What do you have in there? It should look like:

127.0.0.1 localhost.localdomain localhost
192.168.1.157 mail.example.com mail

The first line exactly like this. The second line with the IP adress, the FQDN and the hostname of the machine.

I originally put the relevant line (after localhost) in my /etc/hosts file but took it out because I'm using DHCP to grab an address (I know, I know! This is just a test box for the next few weeks ). How does this explain the difference between zmcontrol's output and the admin console?

[Ryan Frantz]

Well, after logging in to my Zimbra server today and running 'zmcontrol status' again, all is well. The CLI output matches what the admin console claims. All's well that ends well...