Results 1 to 7 of 7

Thread: Zimbra not playing nice with Pacemaker

  1. #1
    Join Date
    Dec 2009
    Posts
    25
    Rep Power
    5

    Default Zimbra not playing nice with Pacemaker

    I'm setting up a new installation of Zimbra that is going to have 2 nodes for high availability. I'm using Heartbeat and Pacemaker as my cluster monitoring stack, and DRBD as my network replication. I've got a happy Zimbra installation, and a happy cluster configuration. When kept separate, they both work fine. I'm having a bit of trouble integrating Zimbra to the cluster. I'm using the regular init script for Zimbra, since there is no OCF script that I can find anywhere. As far as I can tell, the Zimbra init script is LSB compliant, as described here.

    Appendix*G.*Is This init Script LSB Compatible?

    I *think* the problem is Pacemaker is timing out before Zimbra can finish starting, which causes a failure. The timeout is somewhere in the neighborhood of 20 seconds. LSB resources can't be given any parameters in Pacemaker like OCF can, they're just run "as is". I've tried adding "op timeout=360s" to the Zimbra resource, but that didn't change anything.

    It works fine if I let it time out and fail and then do a zmcontrol startup. The crm_mon still sees it as stopped, so I'm thinking it times out and then stops monitoring it.

    Is anybody here familiar with this sort of setup and can help me out? I'll post configs and logs if so. If not anybody on the forums, does tech support help with this sort of stuff, or will it be brushed away as a Pacemaker problem? We've got a support contract and I don't mind using a ticket for this, but I don't want to waste one if it's something they're not going to help me with.

  2. #2
    Join Date
    Jul 2007
    Location
    Baltimore
    Posts
    1,649
    Rep Power
    11

    Default

    zimbra on drbd is not supported, so you will most likely not get any help from zimbra support. theres only one thread i've seen that seemed to have any value for this and thats

    http://www.zimbra.com/forums/adminis...mbra-drbd.html

  3. #3
    Join Date
    Nov 2010
    Posts
    1
    Rep Power
    4

    Default

    BCamp or anyone else, have you been able to get Zimbra working with Corosync and Pacemaker?

  4. #4
    Join Date
    Nov 2010
    Posts
    54
    Rep Power
    4

    Post This might be of help

    I am also trying to making it work, not sure if I will post the final result because our setup is too specific, doc is being written in Spanish and other things. If I ever do it I will use the Solved DRBD post.

    But I can tell you telling you what I am going to do to try to solve this same problem.

    According to OCF Resource Agents you have to write a proper OCF agent. Reusing an LSB script as an OCF is not right. I mean old heartbeat used LSB scripts but pacemaker no longer uses them.

    It would seem that you are lacking the monitor parametre.

    So what I am going to do is to copy the:
    Code:
    /usr/lib/ocf/resource.d/heartbeat/postfix
    file into this new file:
    Code:
    /usr/lib/ocf/resource.d/btactic/zimbra
    .

    Then using a find postfix string and replace it with zimbra string might help a bit. But be sure to read the Debugging part of the link I have given you.

    And the other part of the setup should be this one. When setting up pacemaker with crm instead of using:
    Code:
    ocf:hearbeat:postfix
    you should use:
    Code:
    ocf:btactic:zimbra
    .

    As I said this is how I understand all this stuff but I haven't tested it yet.

    Just hope that it helps someone else.
    Adrian Gibanel, IT Manager

    "be free, be innovative, bTactic"

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

    www.btactic.com

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

    Default Same Issue here

    Same issue here, I am using Heartbeat 2.1.3, but Zimbra fails to start, the error is the same timeout.

    I may have to revert back to heartbeat 1.2.5, since I am sure it works. But is there a way to resolve this? My script works fine with LSB tests after I edited zmcontrol (changed the second dbstatus value to 3).

    Thanks in advance...

    Quote Originally Posted by BCamp View Post
    I'm setting up a new installation of Zimbra that is going to have 2 nodes for high availability. I'm using Heartbeat and Pacemaker as my cluster monitoring stack, and DRBD as my network replication. I've got a happy Zimbra installation, and a happy cluster configuration. When kept separate, they both work fine. I'm having a bit of trouble integrating Zimbra to the cluster. I'm using the regular init script for Zimbra, since there is no OCF script that I can find anywhere. As far as I can tell, the Zimbra init script is LSB compliant, as described here.

    Appendix*G.*Is This init Script LSB Compatible?

    I *think* the problem is Pacemaker is timing out before Zimbra can finish starting, which causes a failure. The timeout is somewhere in the neighborhood of 20 seconds. LSB resources can't be given any parameters in Pacemaker like OCF can, they're just run "as is". I've tried adding "op timeout=360s" to the Zimbra resource, but that didn't change anything.

    It works fine if I let it time out and fail and then do a zmcontrol startup. The crm_mon still sees it as stopped, so I'm thinking it times out and then stops monitoring it.

    Is anybody here familiar with this sort of setup and can help me out? I'll post configs and logs if so. If not anybody on the forums, does tech support help with this sort of stuff, or will it be brushed away as a Pacemaker problem? We've got a support contract and I don't mind using a ticket for this, but I don't want to waste one if it's something they're not going to help me with.

  6. #6
    Join Date
    Nov 2010
    Posts
    54
    Rep Power
    4

    Default

    Quote Originally Posted by emmaylots View Post
    Same issue here, I am using Heartbeat 2.1.3, but Zimbra fails to start, the error is the same timeout.
    I was advised by the #linux-ha people to use pacemaker instead of heartbeat because heartbeat seemed not to be as well supported as heartbeat.
    Adrian Gibanel, IT Manager

    "be free, be innovative, bTactic"

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

    www.btactic.com

  7. #7
    Join Date
    Oct 2012
    Posts
    2
    Rep Power
    3

    Default

    adrian.gibanel.btactic this script saved my life thanks for
    adrian.gibanel.btactic it works for me cenots6.4 zimbra 8.2

Similar Threads

  1. Zimbra spam system
    By rajahd in forum Administrators
    Replies: 9
    Last Post: 04-16-2008, 07:25 PM
  2. Major Issue - 5.0RC2 NE to 5.0GA NE failed
    By DougWare in forum Installation
    Replies: 7
    Last Post: 01-06-2008, 08:56 PM
  3. Replies: 22
    Last Post: 12-02-2007, 04:05 PM
  4. Zimbra shutdowns every n hours.
    By Andrewb in forum Administrators
    Replies: 13
    Last Post: 08-14-2007, 08:55 AM
  5. zmtlsctl give LDAP error
    By sourcehound in forum Administrators
    Replies: 5
    Last Post: 03-11-2007, 03:48 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
  •