Can Not Start MTA

[JonathanC]

Hi Everyone,

I just attempted to install a clean version on RHES 4. I used the basic setup on RH and attempted to install Zimbra Beta 2. Durring the install, I got a port conflict on port 25. By what, I am not sure. It is a clean RH install. Once the install completed, I can not start the MTA service. When I view the logs, I see the following:

Nov 23 09:45:41 mail postfix/postfix-script: warning: not owned by root: /opt/zimbra/postfix-2.2.3/conf/main.cf
Nov 23 09:45:41 mail postfix/postfix-script: starting the Postfix mail system
Nov 23 09:45:41 mail postfix/master[9297]: fatal: bind 0.0.0.0 port 25: Address already in use

Can anyone help guide me in the right direction? Thanks in advance!

[goetzi]

Try following:

As root:

chkconfig sendmail off
service sendmail stop

As zimbra:

zmcontrol stop
zmcontrol start

[JonathanC]

Thanks very much goetzi....that did the trick!!

[JonathanC]

I am not sure if this is related or not, but now I can not authenticate to the SMTP server using an outlook client. I have TLS disabled but I just wind up in an endless SMTP authentication loop. Please help! I am so close...

[goetzi]

Can you post the appropriate lines from /var/log/zimbra.log ... this would help much.

[JonathanC]

Here is the part of the log...

Nov 23 15:20:04 mail zimbramon[19297]: 19297:info: 2005-11-23 15:20:01, DISK: mail.myhost.com: dev: /dev/sda1, mp: /boot, tot: 99, avail: 82
Nov 23 15:20:04 mail postfix/smtpd[18704]: connect from mymachine[192.168.0.117]
Nov 23 15:20:04 mail postfix/smtpd[18704]: warning: mymachine[192.168.0.117]: SASL LOGIN authentication failed
Nov 23 15:20:04 mail postfix/smtpd[18704]: lost connection after AUTH from mymachine [192.168.0.117]
Nov 23 15:20:04 mail postfix/smtpd[18704]: disconnect from mymachine[192.168.0.117]
Nov 23 15:20:06 mail postfix/smtpd[18704]: connect from mymachine[192.168.0.117]
Nov 23 15:20:06 mail postfix/smtpd[18704]: warning: mymachine[192.168.0.117]: SASL LOGIN authentication failed
Nov 23 15:20:06 mail postfix/smtpd[18704]: lost connection after AUTH from mymachine[192.168.0.117]
Nov 23 15:20:06 mail postfix/smtpd[18704]: disconnect from mymachine[192.168.0.117]

We are not using TLS. Thanks in advance for your help.

[marcmac]

Is sasl running?

[JonathanC]

Yes - when I use the command ps aux | grep sasl, I get the following:

[root@mail ~]# ps aux | grep sasl
zimbra 14373 0.0 0.0 5344 1752 ? Ss 14:57 0:00 /opt/zimbra/cyrus-sasl-2.1.21.ZIMBRA/sbin/saslauthd -r -a zimbra
zimbra 14374 0.0 0.0 5344 1752 ? S 14:57 0:00 /opt/zimbra/cyrus-sasl-2.1.21.ZIMBRA/sbin/saslauthd -r -a zimbra
zimbra 14375 0.0 0.0 5344 1752 ? S 14:57 0:00 /opt/zimbra/cyrus-sasl-2.1.21.ZIMBRA/sbin/saslauthd -r -a zimbra
zimbra 14376 0.0 0.0 5344 1752 ? S 14:57 0:00 /opt/zimbra/cyrus-sasl-2.1.21.ZIMBRA/sbin/saslauthd -r -a zimbra
zimbra 14377 0.0 0.0 5344 1752 ? S 14:57 0:00 /opt/zimbra/cyrus-sasl-2.1.21.ZIMBRA/sbin/saslauthd -r -a zimbra
root 17167 0.0 0.0 5604 676 pts/3 S+ 17:51 0:00 grep sasl

I am able to telnet to port 25 if that helps in any way. Thanks for your help.

[Crowhurst]

I just had the same problem earlier today. I needed to find what was running on port 25 and stop it. I ran a "ps ax" and then "lsof -i -P | grep :25" to find out what was running.

For lsof i had to go to the right directory (locate lsof)

from "ps ax" I was able to see the pid which was running the program on port 25

"12055 ? Ss 0:00 /opt/zimbra/cyrus-sasl-2.1.21.ZIMBRA/sbin/saslauthd -r -a zimbra"

I then killed that pid. the other 5 pid's with the same service died from killing that one pid.

Then restarted zimbra and it worked.
-------

However, I am still having the outgoing mail problems and authentication problems which you are writing about. Also, i cannot get either outlook or evolution to connect via imap. I dont know if all of these things are related.

[kevindods]

We have had similar SMTP probs with clients looping at TLS auth. Has anyone seen a solution? We have bodged to continue playing by selecting tls 'if available' in Thunderbird and not requiring it at the server end, most times this works. Didnt have this problem on beta 1, there was a missing -r in a conf file but its certainly there now!

We will need to clear fedora and start again I think as the prodding has caused some fun and games with other services now - logger failing and most recently MTA not starting. uninstall and reinstall of Zimbra is not curing it.

Thanks

Kevin