similar to: Missing dependencies for HA

Hello all, I've been googling and haven't found an answer. I have a Centos 4.6 box that is having an issue since the last yum update. The nss_ldap and kernel packages were the only packages installed/updated. When I try to run yum I now receive: [root at ns1 ~]# yum update There was a problem importing one of the Python modules required to run yum. The error leading to this problem was:

Howdy, If ever somebody here might have encountered this, the rpm -qa commands just stuck for ages on my box ( honestly this is rhel 3 box). I done rebuilding already the /var/lib/rpm/__db* as per KB article but to no avail. Any additional hints what's to look for? One thing I notice w/c I think is weird is that we I losf the process of rpm -qa that's freezing, it's looking

Greetings - Hoping to hear from hunner or one of the other maintainers of the puppetlabs corosync module - there is a note on the git project page that there is currently no way to configure STONITH. Is this information current? If so, has anybody come up with a simple method of managing STONITH with corosync via puppet? -- You received this message because you are subscribed to the

Hello List, Any suggestions to solve the following would be most appreciated. Setup: Active/Passive Two Node Cluster. Two UPSes (APC Smart-UPS 1500 C) with USB communication cables cross connected (ie UPS-webserver1 monitored by webserver2, and vice versa) to allow for stonith/fencing OS OpenSuse Leap 42.2 NUT version 2.7.1-2.41-x86_64 Fencing agent: external/nut Problem: When power fails to a

Roger, Thanks for your reply. As I understand it, for reliable fencing a node cannot be responsible for fencing itself, as it may not be functioning properly. Hence my "cross over" setup. The direct USB connection from Webserver1 to UPS-Webserver2 means that Webserver1 can fence (cut the power to) Webserver2 if the cluster software decides that it is necessary. If my UPSes were able to

On Fri, 22 Apr 2016, Digimer wrote: > Then you would use pacemaker to manage the floating IP, fence > (stonith) a lost node, and promote drbd->mount FS->start nfsd->start > floating IP. My favorite acronym: stonith -- shoot the other node in the head. -- Paul Heinlein heinlein at madboa.com 45?38' N, 122?6' W

Four problems below: # dnf -y groupupdate "Core" "Minimal Install" bintray-tvheadend-stable 0.0? B/s |?? 0? B???? 00:00 Failed to synchronize cache for repo 'bintray-tvheadend-stable', ignoring this repo. Last metadata expiration check: 0:03:11 ago on Sat 16 May 2020 12:30:47 PM CDT. Error: ?Problem 1: package python3-hawkey-0.35.1-9.el8_1.x86_64 requires

I am stuck. This is X86_64 platform. In the extras repos, there is the SRPMS for heartbeat along with the RPMS for it. I have downloaded both. But I can't build the RPMS from the SRPM as it fails compiling something in BUILD/heartbeat-2.0.8/lib/crm/pengine Additionally, I can't install the RPMS: rpm -Uvh heartbeat-2.0.8-3.el5.centos.i386.rpm heartbeat-2.0.8-3.el5.centos.x86_64.rpm

Hi list, I'm new to clustering, and I'm running a little cluster at home. The cluster is running on a workstation hardware and running on Centos 6.5. Component: corosync, pacemaker, drbd and pcs. All works good. This cluster has different resources: 1) drbd0 2) drbd1 3) drbd0_fs 4) drbd1_fs 5) pgsql 6) smb + nmb 7) libvirt (lbs) 8) libvirt_guests (lsb) I've this constraint

Hi, I recently configured Linux HA for Asterisk service (using Asterisk resource agent downloaded from link: https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/asterisk ). As per configuration it is working good but when I include "monitor_sipuri=" sip:42 at 10.3.152.103" " parameter in primitive section it is giving me an errors like listed below; root at

Hello all, I am trying to create a corosync/pacemaker cluster using CentOS 6.0. However, I'm having a great deal of difficulty doing so. Corosync has a valid configuration file and an authkey has been generated. When I run /etc/init.d/corosync I see that only corosync is started. >From experience working with corosync/pacemaker before, I know that this is not enough to have a functioning

Hi All, Is anybody succeed to run a configuration on a two node clusters with Samba installed on each machine? I compiled two versions on different directories (/usr/local/samba1 and samba2). At this point, I can run 2 samba's on one node in case of failure but problems are on Active Directory authentication for the Fallback node. Any suggestion! I'm running AIX 5.2 with HACMP and

Greetings - I have a Centos 6 box fully updated that intermittently sends me an "[abrt] full crash report" email. I am not familiar with these at all and in my limited google search have not found good information to interpret this information. The most recent (and the most frequent one) is listed below, also I have listed the lines from /var/log/messages that correspond to

Hi, I am trying to build a rock solid XEN High availability cluster. The platform is SLES 11 SP1 running on 2 HP DL585 both connected through HBA fiber channel to the SAN (HP EVA). XEN is running smoothly and I''m even amazed with the live migration performances (this is the first time I have the chance to try it in such a nice environment). XEN apart the SLES heartbeat cluster is

Hi, For a testing purposes I'm trying to create two node HA environment for running some service (openvpn and haproxy). I installed two CentOS 6.4 KVM guests. I was able to create a cluster and some resources. I followed the document https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Configuring_the_Red_Hat_High_Availability_Add-On_with_Pacemaker/index.html

Hi all, I am following the guide on HowToForge to get Heartbeat going for two Apache web servers (http://www.howtoforge.com/high_availability_heartbeat_centos), a quick question for anyone who might have a similar setup. Do I have to assign the service IP to either of the NICs or does Heartbeat do that automagically? Thanks -- "The secret impresses no-one, the trick you use it for is

I have a suggestion about the heartbeat and the way that "downed node" detection works. There are occasions where a node is up, and for whatever reason, I need to power cycle it (for instance, a frozen process, etc). In these instances, my other nodes are unable to perform file system operations until the heartbeat period expires. This ends up being somewhere around 30-60 seconds (this

I just recently upgraded a box from i386 5.3 -> 5.4. The box has heartbeat packages installed from "extras:" heartbeat-pils-2.1.3-3.el5.centos heartbeat-stonith-2.1.3-3.el5.centos heartbeat-devel-2.1.3-3.el5.centos heartbeat-2.1.3-3.el5.centos The heartbeat daemon no longer starts.. the init script reports a success, as well as the logs: May 4 22:33:10 fc-fmcln02 heartbeat: [9344]:

Hi, I think this would be the best forum, let me know if not. I am in the middle of writing fencing scripts for Citrix XenServer virtual machines (specifically for use with Redhat Clustering, but will also work from pacemaker etc) and I noticed that XCP uses the same XenAPI (from what I can tell). Just wondering if someone would be able to test the scripts on XCP and let me know if they work.

Hello The "version" function is not supported by the hyperv driver: $ virsh --connect=hyperv://hypervhost version Compiled against library: libvirt 1.1.1 Using library: libvirt 1.1.1 Using API: Hyper-V 1.1.1 error: failed to get the hypervisor version error: this function is not supported by the connection driver: virConnectGetVersion But we need this funtion for the