On Thursday 28 October 2010 21:41:59 Greg Woods wrote:
> I currently have an old heartbeat v1 cluster that I am moving to a newer
> Pacemaker/heartbeat v3 cluster. That is, I am moving the functionality
> of the old cluster to the new one so that the old one can be phased out.
> The new cluster is running all the latest stuff from the clusterlabs
> repo under CentOS 5.5
> 
> One thing the old one does is run Linux Virtual Server and ipvsadm to
> farm out incoming SMTP connections to multiple mail processing nodes
> (virus scanning, spamassassin scanning, alias lookup, etc.). I would
> like to have the new cluster do this.
> 
> >From what I have read, it appears that the "right" way to do this is to
> 
> install ldirectord and set up an ldirectord resource in Pacemaker. The
> problem is that I can't get ldirectord to install. There is an
> ldirectord package in the clusterlabs repo, and a heartbeat-ldirectord
> package in the CentOS-extras repo, and they conflict. Neither one is
> installed now but I still get this error when I try to install
> ldirectord:
> 
> ERROR with rpm_check_debug vs depsolve:
> heartbeat-ldirectord conflicts with ldirectord-1.0.3-2.6.el5.x86_64
> Complete!
> (1, [u'Please report this error in
> https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Enterprise
> %20Linux%205&component=yum'])
> 
> The same thing happens if I disable the extras repo, and even if I do
> "yum clean all" first. If instead I try to install heartbeat-ldirectord
> and disable the clusterlabs repo (which might result in a package that
> doesn't work right in any event), I get a different error:
> 
> Transaction Check Error:
>   file /usr/lib/ocf/resource.d/heartbeat/ldirectord from install of
> heartbeat-ldirectord-2.1.3-3.el5.centos.x86_64 conflicts with file from
> package resource-agents-1.0.3-2.6.el5.x86_64

Try to get rid of the file if it is still there. Try it again afterwards.

> Is going to the source the only way to get ldirectord to install on this
> system, or has someone else seen this before and know of a workaround?

The resource-agents package is definitely the right one. And there should be no 
problem to install it after a fresh install.

-- 
Dr. Michael Schwartzkopff
Guardinistr. 63
81375 München

Tel: (0163) 172 50 98
Fax: (089) 620 304 13

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to