[SOLVED] Zimbra on DRBD

[c_kalbhor]

We have installed Release 5.0.16_GA_2921.UBUNTU8_64 UBUNTU8_64
about a month back.

It was working fine till yesterday afternoon. We are able to receive mails.
But when we try to send emails we get error.

I checked /var/log/zimbra.log file it gave following message :
Sep 18 16:58:03 webmail zmmailboxdmgr[20879]: status requested
Sep 18 16:58:03 webmail zmmailboxdmgr[20879]: status OK
Sep 18 16:58:03 webmail zimbramon[20716]: 20716:info: 2009-09-18 16:58:01, STATUS: webmail.chpl.in: antispam: Running
Sep 18 16:58:03 webmail zimbramon[20716]: 20716:info: 2009-09-18 16:58:01, STATUS: webmail.chpl.in: antivirus: Running
Sep 18 16:58:03 webmail zimbramon[20716]: 20716:info: 2009-09-18 16:58:01, STATUS: webmail.chpl.in: ldap: Running
Sep 18 16:58:03 webmail zimbramon[20716]: 20716:info: 2009-09-18 16:58:01, STATUS: webmail.chpl.in: logger: Running
Sep 18 16:58:03 webmail zimbramon[20716]: 20716:info: 2009-09-18 16:58:01, STATUS: webmail.chpl.in: mailbox: Running
Sep 18 16:58:03 webmail zimbramon[20716]: 20716:info: 2009-09-18 16:58:01, STATUS: webmail.chpl.in: mta: Stopped
Sep 18 16:58:03 webmail zimbramon[20716]: 20716:info: 2009-09-18 16:58:01, STATUS: webmail.chpl.in: snmp: Running
Sep 18 16:58:03 webmail zimbramon[20716]: 20716:info: 2009-09-18 16:58:01, STATUS: webmail.chpl.in: spell: Running
Sep 18 16:58:03 webmail zimbramon[20716]: 20716:info: 2009-09-18 16:58:01, STATUS: webmail.chpl.in: stats: Running
Sep 18 16:58:30 webmail postfix/postqueue[21058]: fatal: Queue report unavailable - mail system is down

I tried to get the satus on zimbra control prompt

zimbra@webmail:~$ zmcontrol status
Host webmail.chpl.in
antispam Running
antivirus Running
ldap Running
logger Running
mailbox Running
mta Stopped
postfix is not running
snmp Running
spell Running
stats Running

Thus it gives mta Stopped and postfix is not running
Further zimbra is also not opening in browser using http://localhost/zimbra
Yes but it opens with https://localhost/zimbra

Kindly help - Chandrashekhar

[hizar2000]

Originally Posted by sems

Heartbeat does in R1 mode does not check the status of each resource, whether they are up or down. So, you'll need to implement something, like MON package to monitor zimbra status and if needed stop heartbeat accordingly.

Hizar,

In your setup, I haven't seen anything related to split-brain on DRBD. That has been my major issue (I have been running an active/passive cluster since March, but it always comes back as a problem). How do you deal with it on yours? I have been searching on the net for possible ways to prevent split-brain to happen in the first place. I found some articles suggesting to increase heartbeat's drbddisk script's retry from 6 to 20 and increasing timeout values (see Otherworldly Gate: STONITH with DRBD and Heartbeat), I haven't tried it yet but I am open to suggestions.

Yes this is an issue with my setup. I've never really understood how this whole Stonith thing is supposed to work and when I've tried it, it hasnt quite given me the results I was expecting. Other than a Stonith device, it seems hard to get stonith to work properly. (If the network between the two hosts is down, then how is one host supposed to kill the other?)

The other thing I tried that got me mixed results is setting up 'Shoot myself in the Head' which as it sounds is when the other host is unreachable, kill yourself.

This has the effect that both servers recover after a minimal downtime, but its hardly High Availability.

The other problem I had was sometimes it refused to work because something was holding the DRBD partition open and would not die.

[lassaad]

empty the qeue