Page 6 of 7 FirstFirst ... 4567 LastLast
Results 51 to 60 of 61

Thread: [SOLVED] Zimbra on DRBD

  1. #51
    Join Date
    Jan 2009
    Posts
    369
    Rep Power
    6

    Default

    anyone has solution HA with multi server by BRDB and Heartbeat. For example we have:
    - 1 MTA (1)
    - 1 Mailbox store (2)
    - 1 LDAP server (3)
    Now how we use BRDB and heartbeat with server (2) and (3).

  2. #52
    Join Date
    May 2010
    Location
    Budapest
    Posts
    56
    Rep Power
    5

    Default

    And What is the question?

    If you have 3 servers, and you would like to build a culster for the mailbox and LDAP servers with DRBD, then you'll need two Mailbox servers and two LDAP servers.
    configure both LDAP to listen on the floating HB IP Address and do the same with the mailbox store server.

    example:
    MAILBOX1 -------- [Mailbox Heartbeat IP] -------- MAILBOX2
    LDAP1 -------- [LDAP Heartbeat IP] -------- LDAP2

    and configure every server to access the Heartbeat IP
    Tibby

  3. #53
    Join Date
    Sep 2011
    Posts
    8
    Rep Power
    4

    Default Need Help with ZCS open source clustering

    Quote Originally Posted by tapan.thapa View Post
    I also got the success in clustering of two zimbra server. If any one require any help do let me know.
    Hi tapan,
    Hope you are doing well,

    We have 6.0.13 open source in our environment mail box store mounted on DAS, and have a one spare server with same configuration but no other DAS.

    I am an new to linux clusters but can follow instructions and get the thing done. Please advice how to I go about setting up DRBD+heartbeat for our ZCS.

    Pawan

  4. #54
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    Quote Originally Posted by pawann.sharma View Post
    I am an new to linux clusters but can follow instructions and get the thing done. Please advice how to I go about setting up DRBD+heartbeat for our ZCS.
    This thread is marked as Solved for the simple reason that the answer to your question is on the first page, did you try that solution?
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  5. #55
    Join Date
    Nov 2010
    Posts
    54
    Rep Power
    5

    Post Zimbra DRDB links

    I just wanted to summarize a bit my Zimbra DRDB howto search in this thread so that it can help to someone else:

    Adrian Gibanel, IT Manager

    "be free, be innovative, bTactic"

    Av. Balmes, 34 4rt 1a B | Lleida, Spain 25006

    www.btactic.com

  6. #56
    Join Date
    Apr 2011
    Posts
    117
    Rep Power
    4

    Default

    had anyone tried or found any documention of using DRBD as DRC site (2+1 multiserver setup)?

    current primary is 2+1

    would like to do:
    primary mailbox 1 synched with drbd 8.3 on centos to DRC mailbox 1
    primary mailbox 2 synched with drbd 8.3 on centos to DRC mailbox 2

  7. #57
    Join Date
    May 2008
    Location
    Nigeria
    Posts
    92
    Rep Power
    7

    Arrow Heartbeat Unable to Start Zimbra service

    Please help, I keep getting this error in Heartbeat log (/var/log/ha-log). It says the service zimbra timed out. What am I missing please!!!

    Quote Originally Posted by tapan.thapa View Post
    I also got the success in clustering of two zimbra server. If any one require any help do let me know.

  8. #58
    Join Date
    May 2008
    Location
    Nigeria
    Posts
    92
    Rep Power
    7

    Default Heartbeat 2.1.3 Fails to Start Zimbra

    Hi Papaya,

    I am using heartbeat 2.1.3 on CENTOS/REDHAT 5,

    Here's my /etc/ha.d/ha.cf:
    logfile /var/log/ha-log

    logfacility local0

    keepalive 2

    deadtime 60

    warntime 10

    initdead 120

    auto_failback on

    bcast eth0

    node hercules.olotu.com

    ping 192.168.183.2

    respawn hacluster /usr/lib/heartbeat/ipfail

    crm yes

    I am using crm,

    So I created and xml file using the command:
    /usr/lib/heartbeat/haresources2cib.py --stdout -c /etc/ha.d/ha.cf, and got this config file (I am testing it one a single node, since two nodes fail to work)

    Resources section:
    <resources>
    <group id="group_1">
    <primitive class="ocf" id="IPaddr_192_168_183_99" provider="heartbeat" type="IPaddr">
    <operations>
    <op id="IPaddr_192_168_183_99_mon" interval="5s" name="monitor" timeout="5s"/>
    </operations>
    <instance_attributes id="IPaddr_192_168_183_99_inst_attr">
    <attributes>
    <nvpair id="IPaddr_192_168_183_99_attr_0" name="ip" value="192.168.183.99"/>
    </attributes>
    </instance_attributes>
    </primitive>
    <primitive class="lsb" id="zimbra_2" provider="heartbeat" type="zimbra">
    <operations>
    <op id="zimbra_2_mon" interval="120s" name="monitor" timeout="60s"/>
    </operations>
    </primitive>
    </group>
    </resources>

    But Zimbra always fail to start! I get this error when I run "crm_mon"
    [root@hercules ~]# crm_mon
    Defaulting to one-shot mode
    You need to have curses available at compile time to enable console mode


    ============
    Last updated: Wed Jun 20 18:17:21 2012
    Current DC: hercules.olotu.com (a33babe8-8574-49a4-8f4e-1e7f7a43f551)
    1 Nodes configured.
    1 Resources configured.
    ============

    Node: hercules.olotu.com (a33babe8-8574-49a4-8f4e-1e7f7a43f551): online

    Resource Group: group_1
    IPaddr_192_168_183_99 (heartbeat:cf:IPaddr): Started hercules.olotu.com
    zimbra_2 (lsb:zimbra): Started hercules.olotu.com (unmanaged) FAILED

    Failed actions:
    zimbra_2_start_0 (node=hercules.olotu.com, call=7, rc=-2): Timed Out
    zimbra_2_stop_0 (node=hercules.olotu.com, call=8, rc=-2): Timed Out

    Then "crm_verify --live-check -V" gives me:
    [root@hercules ~]# crm_verify --live-check -V
    crm_verify[1103]: 2012/06/20_18:19:17 WARN: unpack_rsc_op: Processing failed op zimbra_2_start_0 on hercules.olotu.com: Timed Out
    crm_verify[1103]: 2012/06/20_18:19:17 WARN: unpack_rsc_op: Compatability handling for failed op zimbra_2_start_0 on hercules.olotu.com
    crm_verify[1103]: 2012/06/20_18:19:17 WARN: unpack_rsc_op: Processing failed op zimbra_2_stop_0 on hercules.olotu.com: Timed Out
    crm_verify[1103]: 2012/06/20_18:19:17 WARN: unpack_rsc_op: Compatability handling for failed op zimbra_2_stop_0 on hercules.olotu.com
    crm_verify[1103]: 2012/06/20_18:19:17 WARN: native_color: Resource zimbra_2 cannot run anywhere
    crm_verify[1103]: 2012/06/20_18:19:17 WARN: custom_action: Action zimbra_2_stop_0 (unmanaged)
    Warnings found during check: config may not be valid

    I have run checks on on linux-ha.org to be sure zimbra startup script is okay.

    KIndly help, anyone please!!

    I even created a custom zimbra init file, thinking maybe ZImbra's own startup script wasn't working:

    #!/bin/bash
    #
    # Run-level Startup script for the Zimbra services
    #
    # chkconfig: 345 91 19
    # description: Startup/Shutdown Zimbra services

    # if the executables do not exist -- display error

    # of the service or usage display
    RETVAL=0
    case "$1" in
    start)
    # Zimbra startup
    echo -n "Starting Zimbra: "
    su - zimbra -c "/opt/zimbra/bin/zmcontrol start"
    RETVAL=$?
    sleep 5
    touch /var/lock/subsys/zimbra
    echo "OK"
    ;;
    stop)
    # Zimbra shutdown
    echo -n "Shutdown Zimbra: "
    sleep 5
    su - zimbra -c "/opt/zimbra/bin/zmcontrol stop"
    RETVAL=$?
    rm -f /var/lock/subsys/zimbra
    echo "OK"
    ;;
    status)
    # Zimbra status
    echo -n "Zimbra Status: "
    su - zimbra -c "/opt/zimbra/bin/zmcontrol status"
    #if ! test -f /var/lock/subsys/zimbra ; then
    RETVAL=$?
    # RETVAL=3
    ;;
    reload|restart)
    # Zimbra shutdown
    echo -n "Shutdown Zimbra: "
    sleep 1
    su - zimbra -c "/opt/zimbra/bin/zmcontrol stop"
    RETVAL=$?
    rm -f /var/lock/subsys/zimbra
    echo "OK"
    # Zimbra startup
    echo -n "Starting Zimbra: "
    su - zimbra -c "/opt/zimbra/bin/zmcontrol start"
    RETVAL=$?
    sleep 1
    touch /var/lock/subsys/zimbra
    echo "OK"
    ;;
    *)
    echo "Usage: $0 start|stop|restart|reload|status"
    exit 1
    esac
    exit $RETVAL
    @


    STILL NOT WORKING, kindly share solutions please!



    Quote Originally Posted by papaya74 View Post
    Hi folks,

    on my Debian-Servers i got ZIMBRA successfull working with heartbeat on a DRBD netraid !

    Short description (how i did it): FOR TESTING ONLY !!!!
    ==============================================


    I ASSUME, that you have a proper running installation of heartbeat & DRBD !!

    1. Make 2 (!) installations of Zimbra with exactly the same parameters, on 2 different server, of course.

    2. Define one server as Master (for yourself and later for heartbeat), and configure this one to your ZIMBRA-requirements.

    3. Test your Master-Zimbra-Server if everything is fine, up & running

    4. Remove on BOTH NODES ALL Zimbra auto-start-scripts, like
    Code:
    rm /etc/rc2.d/S99zimbra
    rm /etc/rc3.d/S99zimbra
    rm /etc/rc4.d/S99zimbra
    rm /etc/rc5.d/S99zimbra
    5. STOP ALL Zimbra services:
    Code:
    /etc/init.d/zimbra stop
    6. MOVE /opt to somewhere else, e.g /opt_save, and create /opt again:
    Code:
    # mv /opt /opt_save
    # mkdir /opt
    7. Get the DRBD working on /opt as a netraid. I don't know if it will work with symlinks, so i decided to mount /opt directly with DRBD. Don't forget /etc/fstab

    8. Now you have to reboot BOTH nodes, to be sure that you have a proper DRBD netraid running on /opt !!!
    Check also if heartbeat is running as well and mounts /opt properly if your Master is dead !!

    9. If everythings is working fine, then it's time to copy Zimbra back to production state:
    Code:
    mv /opt_save/zimbra /opt/
    10. Edit /etc/ha.d/haresources on BOTH NODES and ADD 'zimbra' at the end of the line where you a controlling, what heartbeat should start & stop.
    Code:
    # nano /etc/ha.d/haresources
    
    zimbra-01 drbddisk::netraid1 Filesystem::/dev/drbd0::/opt::ext3 YOUR_MASTER_IP zimbra
    11. REBOOT both Nodes, and Zimbra should now start on the master. If the master dies, the 2nd node will takeover completly

    BEWARE:
    ==> THIS WAS DONE JUST FOR TESTING PURPOSES !!!
    ==> EXACTLY ANALYSIS of Zimbra's behaviour is PENDING !!!


    I hope it'll work in a production enviroment, i will test it this week with nearly 60GB email, so we will see....

    /harry

  9. #59
    Join Date
    May 2010
    Posts
    272
    Rep Power
    5

    Default

    Quote Originally Posted by adrian.gibanel.btactic View Post
    I just wanted to summarize a bit my Zimbra DRDB howto search in this thread so that it can help to someone else:

    one of the comments:


    at step 11 shouldn't you change the ip address of zimbra-2
    Anonymous (not verified)
    Sat, 09/06/2008 - 03:36

    reply

    Absolutely, I guess I glossed over that when I mentioned making the clone. Naturally you will not get very far if your clone has the same IP of the original server . I will annotate the post, thanks for the heads up
    diveli
    Sat, 09/06/2008 - 05:15

    -----------------------------------------



    you where right it was worth reading,.. laught my ass of xD

  10. #60
    Join Date
    Dec 2008
    Location
    San Rafael, CA
    Posts
    113
    Rep Power
    6

    Lightbulb

    Quote Originally Posted by phoenix View Post
    This thread is marked as Solved for the simple reason that the answer to your question is on the first page, did you try that solution?
    Unfortunately, that configuration is very old and the software has gone under numerous upgrades.

    Currently, Hearbeat has been upgraded it to Pacemaker.
    Next, Corosync has entered the arena as part of the package alongside DRBD.
    Here is a simple explanation from the master cluster/fencing crew on a two node (bare-metal servers) set up akin to RAID 1.

    Find support on IRC #DRBD and #linux-cluster - Folks who can help newbies in an instant or emergency are on there all the time.
    Pacemaker mailing list: Pacemaker@oss.clusterlabs.org Pacemaker Info Page
    Andrew Beekhof's "Clusters from Scratch" is pretty much the de-facto tutorial on pacemaker
    DRBD LINBIT - Your Way to High Availability - DRBD, Cluster, Heartbeat
    Corosync http://www.corosync.org

    To get automatic recovery after failure, yes, you need all three.

    DRBD simply replicates raw data. That's it, nothing more. Promoting a
    secondary node to primary requires external actions, be it by the user
    or via another program.

    Heartbeat is deprecated and has no future. Anyone using it should be
    making near-term plans to get off of it. So let's take the right off the
    table.

    Corosync is a stand alone tool that handles cluster membership and
    message passing.
    It doesn't care what other programs do or how they use
    it's message passing capabilities. It is merely a communications tool.
    Specifically; It decided who can send and receive messages amoungst a
    group of machines. In our case, we want this so that pacemaker can
    coordinate actions.

    Pacemaker is a cluster resource manager. That is, it reacts to changes
    in cluster membership and, based on defined policies, decides to stop,
    start, migrate or otherwise act on services. It doesn't care *how*
    machines in the cluster come and go, only that they do.

    So in your use case, you would setup DRBD to replicate data. Next, you
    would configure corosync to say "these two nodes are members of cluster
    X". Then you tell Pacemaker; "When both nodes are available, make node
    1's DRBD the primary and make node 2 secondary. However, if not 1 dies,
    promote node 2 to primary. When node 1 returns, demote node 2 and
    promote node 1."

Similar Threads

  1. Replies: 26
    Last Post: 04-19-2011, 10:24 AM
  2. Zimbra shutdowns every n hours.
    By Andrewb in forum Administrators
    Replies: 13
    Last Post: 08-14-2007, 09:55 AM
  3. Fedora Core 3, Clean Install - Not working!
    By pcjackson in forum Installation
    Replies: 17
    Last Post: 03-05-2006, 07:38 PM
  4. Monitoring : Data not yet avalaible
    By s3nz3x in forum Installation
    Replies: 7
    Last Post: 11-30-2005, 07:18 PM
  5. FC3 Install and no zimbra ?
    By aws in forum Installation
    Replies: 10
    Last Post: 10-09-2005, 05:19 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •