Check sendmail or other mta service's and shutdowk / kill process...

Regards,

David

----- Original Message ----- From: "Bill Campbell" centos@celestial.com To: centos@centos.org Sent: Tuesday, November 3, 2009 1:44:37 PM Subject: Re: [CentOS] Zimbra help?

On Mon, Nov 02, 2009, ML wrote:

Hi All,

Is anyone versed in Zimbra? I have most things working except some MTA issue. I tried posting on the Zimbra forums after reading the docs, but my post was labeled as SPAM and the moderators have not replied to my private message to get my post reviewed. Who uses this type of method for getting help anyway? Aren't the days of Bulletin Board BBS's gone?

Anyway...

I installed ZCS for the first time today. Most things are running except I cannot send or receive mail. I get MTA errors. I assume that it is not running. When I send I get unable to connect to MTA.

How do I diagnose the issue?

The ``already in use'' message below probably means that you have the sendmail or some other MTA already running on the system which needs to be disabled.

It's been a while since I looked at Zimbra, but I do know it wants to take over the system, using it's own MTA (Postfix), OpenLdap, MySQL, and IMAP so these must be disabled.

in /var/log/zimbra.log:

Nov  2 17:57:28 indie postfix/postfix-script[9282]: warning: not owned by root: /opt/zimbra/data/postfix/spool Nov  2 17:57:28 indie postfix/postfix-script[9289]: warning: not owned by root: /opt/zimbra/postfix-2.6.5.2z/conf/main.cf Nov  2 17:57:28 indie postfix/postfix-script[9290]: warning: not owned by root: /opt/zimbra/postfix-2.6.5.2z/conf/master.cf Nov  2 17:57:28 indie postfix/postfix-script[9291]: warning: not owned by root: /opt/zimbra/postfix-2.6.5.2z/conf/master.cf.in Nov  2 17:57:28 indie postfix/postfix-script[9294]: warning: not owned by postfix: /opt/zimbra/data/postfix/./spool/maildrop/E18EC1C1048D Nov  2 17:57:28 indie postfix/postfix-script[9295]: warning: not owned by postfix: /opt/zimbra/data/postfix/./spool/pid/master.pid Nov  2 17:57:28 indie postfix/postfix-script[9308]: starting the Postfix mail system Nov  2 17:57:28 indie postfix/master[9309]: fatal: bind 0.0.0.0 port 25: Address already in use Nov  2 17:57:28 indie saslauthd[9316]: detach_tty      : master pid is: 9316 Nov  2 17:57:28 indie saslauthd[9316]: ipc_init        : listening on socket: /opt/zimbra/cyrus-sasl-2.1.23.3z/state/mux Nov  2 17:57:28 indie zimbramon[2574]: 2574:info: Starting stats via zmcontrol Nov  2 17:57:59 indie zmmailboxdmgr[10822]: status requested   Nov  2 17:57:59 indie zmmailboxdmgr[10822]: status OK Nov  2 17:57:59 indie zmmailboxdmgr[10894]: status requested   Nov  2 17:57:59 indie zmmailboxdmgr[10894]: status OK Nov  3 01:58:00 indie postfix/postqueue[10943]: fatal: Queue report unavailable - mail system is down Nov  2 17:58:09 indie zmmailboxdmgr[11484]: status requested Nov  2 17:58:09 indie zmmailboxdmgr[11484]: status OK

I have not done anything with Postfix at all....U am sure it is the Fatal Bind message above, do I need to configure Postfix? I thought Zimbra did that on install?

-Jason _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos

Hi

Like said before. Kill all other MTA's and make shore they remain stopped at system start.

Regarding Zimbra MTA issues, i've always ended up with dns problems as the cause of mta malfunction.

Check if the DNS you provided at /etc/resolv.conf is resolving correctly the zimbra server name. Check local /etc/hosts file to see if your server is listed there correctly.

At last, check the firewall it may be blocking smtp.

Regards,

Nassri

Esta mensagem pode conter informa??o Confidencial/Privilegiada. Se n?o ? o destinat?rio desta mensagem (ou respons?vel por entregar esta mensagem ao destinat?rio), n?o deve copiar ou entregar esta mensagem a outra pessoa. Nesse caso, deve fazer o favor de destruir esta mensagem e de notificar o emissor por e-mail. Por favor, avise imediatamente se o destinat?rio ou a sua empresa n?o consentirem este tipo de mensagens Internet. Opini?es, conclus?es ou outro tipo de informa??es contidas nesta mensagem que n?o estejam relacionadas com o neg?cio oficial da empresa do emissor devem ser entendidas como n?o enviadas ou emitidas por essa empresa.

Confidential/Privileged Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of my firm shall be understood as neither given nor endorsed by it.

Neil Muller schrieb:

I run Zimbra (commercial) on Centos for my employers and there is no problem running Zimbra on Centos or on getting support from Zimbra for Zimbra on Centos. Where did this idea of "no support for Zimbra on Centos" come from?

It comes from the fact that if a problem with Zimbra can be tracked down to a problem in RHEL, Zimbra will work with RedHat to get a fix. If the problem is in CentOS, you will have to work with this forum basically to get it fixed...

Depending on the size of your customer-base, it may make sense to spend those bucks for a yearly RHEL license....

Rainer

Neil Muller schrieb:

On 04/11/2009, at 9:50 PM, Rainer Duffner wrote:

...

It comes from the fact that if a problem with Zimbra can be tracked down to a problem in RHEL, Zimbra will work with RedHat to get a fix. If the problem is in CentOS, you will have to work with this forum basically to get it fixed...

That's not exactly the same as saying that Zimbra is not supported on Centos which is a much more sweeping statement.

...

Depending on the size of your customer-base, it may make sense to spend those bucks for a yearly RHEL license....

Are you saying that there is a current problem with Zimbra on RHEL and Centos

No, I said "if".

and that this problem will only be fixed for RHEL? Won't a RHEL fix eventually flow through in to Centos?

If the problem doesn't exist on RHEL, they probably won't come-up with a fix, right?

Rainer

Neil Muller wrote:

On 03/11/2009, at 8:06 PM, Corey Chandler wrote:

...

ML wrote:

...

Hi All,

Is anyone versed in Zimbra?

Extremely-- and I know that Zimbra is flat out not supported under CentOS, by their own decision. If this is community edition, it's a different kettle of fish entirely.

I run Zimbra (commercial) on Centos for my employers and there is no problem running Zimbra on Centos or on getting support from Zimbra for Zimbra on Centos. Where did this idea of "no support for Zimbra on Centos" come from?

Citation: http://www.zimbra.com/forums/announcements/14116-centos-not-supported.html

Based upon my experience with Zimbra (and other similar vendors), I'm a big fan of NOT having anything that they don't explicitly support touching the Zimbra box. It helps keep the fingerpointing to a minimum when things end up going wrong; if they can point to the OS as a reason to claim a box is "unsupported," they will; compared to the cost of a Zimbra license, the $400 or whatnot for RHEL is inconsequential.

-- Corey / KB1JWQ

Corey Chandler wrote:

Corey Chandler wrote:

...

Citation: http://www.zimbra.com/forums/announcements/14116-centos-not-supported.html

Er, this was updated and linked, just noticed that.

indeed, and the followup links to...

http://www.zimbra.com/forums/announcements/14213-our-centos-users.html

which clarifies that the CentOS4 problem in the prior bulletin turned out to be a customer-installed Perl 5.8.8 which caused problems with Scalar::Util and that in fact, stock CentOS 4.5 and 4.6 worked just fine for them.

The real issue is, when running complex multi-faceted software systems, you really can't just update things at random and expect it to all play nicely.