http://blog.gmane.org/gmane.linux.highavailability.user hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.linux.highavailability.user/39056 <pre> Version Info: OS: CentOS 6.4 Kernel (current): 2.6.32-358.6.2.el6.x86_64 Pacemaker: 1.1.8-7.el6 Corosync: 1.4.1-15.el6_4 CRMSH: 1.2.5-55.4 I was attempting to create a shadow CIB so that I could test changes and I am unsuccessful getting it to work: # crm cib crm(live)cib# new test-conf INFO: 8: test-conf shadow CIB created ERROR: 8: test-conf: no such shadow CIB crm(live)cib# reset test-conf INFO: 9: copied live CIB to test-conf crm(live)cib# list crm(live)cib# new test-conf A shadow instance 'test-conf' already exists. To prevent accidental destruction of the cluster, the --force flag is required in order to proceed. crm(live)cib# use test-conf ERROR: 12: test-conf: no such shadow CIB crm(live)cib# delete test-conf INFO: 13: test-conf shadow CIB deleted So it appears to be there at some level since I can copy the live CIB, and it complains if I try to create the same name again, and I can delete it. But I cannot see it via 'l</pre> Tony Stocker 2013-05-22T13:20:06 http://comments.gmane.org/gmane.linux.highavailability.user/39055 <pre> I just want to make sure that my understanding of resource groups is correct before I proceed too far. Are the following true statements regarding resource groups: 1. The order in which resource primitives are listed in a resource group is the order in which they will be started? 2. The order in which resource primitives are listed in a resource group is the inverse of the order in which they will be stopped? 3. Resource primitives in a resource group are started sequentially, not in parallel? 4. Even if one of the primitives in the group fails to start, subsequent primitives will still be launched? 5. Ordering constraints outside of the group are not applied to resource group members? For example, given the following resource group definition: group HACMASTER HACMASTER-JOBFILE HACMASTER-PWFILE HACMASTER-JAVA HACMASTER-SSHKEYS HACMASTER-EXT-IP HACMASTER-BAK-IP HACMASTER-COMM-IP HACMASTER-STOR-IP \ meta target-role="Started" The 8 resource primitives listed will always be star</pre> Tony Stocker 2013-05-22T12:15:00 http://comments.gmane.org/gmane.linux.highavailability.user/39050 <pre>Dear Team I want to configure the DRBD and Heartbeat on RHEL-6 OS but I am not able to find out exact package of heartbeat for the installation. Please help me out to resolve this issue ! </pre> Deepak Yadav 2013-05-22T03:59:21 http://comments.gmane.org/gmane.linux.highavailability.user/39038 <pre> Version Info: OS: CentOS 6.4 Kernel (current): 2.6.32-358.6.2.el6.x86_64 Pacemaker: 1.1.8-7.el6 Corosync: 1.4.1-15.el6_4 CRMSH: 1.2.5-55.4 I'm using a number of documents from clusterlabs.org, specific to this question I'm using "Pacemaker-1.1-Pacemaker_Explained-en-US.pdf" and I'm in Chapter 8, section 8.4 regarding the use of node parameters to control resource location. This particular document appears to rely almost solely on XML snippets for its examples, and in this case these snippets are the only examples. In an online archive of the mailing list for Pacemaker I found a similar question from Jan 11, 2010 where the questioner was referred to: "Or read the crm_cli doc at clusterlabs.org. Thanks, Dejan " However the document referred to, "crm_cli doc", no longer appears to be hosted on clusterlabs.org. Does anyone know of its new location? Or the location of a similar document which will explain the correct synta</pre> Tony Stocker 2013-05-21T12:25:24 http://comments.gmane.org/gmane.linux.highavailability.user/39034 <pre>We are running heartbeat 2.1.3 on CentOS 5.4. Last Monday AM, I received a call while getting ready for work. Our high availability server was not responding. The previous Saturday, our I.T. admins had re-configured the network to expand IP address ranges on some subnets. For whatever reason, this action caused our main server (in a two-node HA configuration) to loose its virtual interface, rendering our high-availability server unavailable. The network worked fine; the nodes could ping each other based on their normal IP's and they could ping the ping node, but the virtual IP (the one we REALLY care about) was ignored. Nothing in the logs, no errors, nothing. Just an unresponsive virtual server. A manual fail-over brought it back quickly as the backup took over. I.T. had done their work on Sat and, had I checked our server on Sunday, I would have found it "unreachable" with a normal ping. When my colleague called me, I asked him what "ifconfig" looked like. He described three interf</pre> DaveW 2013-05-20T22:00:03 http://comments.gmane.org/gmane.linux.highavailability.user/39032 <pre> Here is some basic information about the cluster setup/configuration, hopefully this is not too much extraneous information. Just as hopefully, I hope that I've provided enough information. If not, please let me know and I will rectify that. Version Info: OS: CentOS 6.4 Kernel (current):2.6.32-358.6.2.el6.x86_64 Pacemaker:1.1.8-7.el6 Corosync:1.4.1-15.el6_4 CRMSH:1.2.5-55.4 Hardware Info: Six (6) 'Class A' systems (more cores, more RAM) Six (6) 'Class B' systems (less cores, less RAM) Panasas shared storage system Resources Info: A. Cluster Main Server B. Cluster FTP Server C. Custom Processing Segmenter Node D. Custom Processing Master Node E., F., G., H. Custom Processing Compute Nodes [1-4] I was hoping someone could give me some guidance about setting up constraints appropriately and effectively. Here are the guidelines/goals: 1. As much as possible resources should not be moved, high stickiness, modified as necessary of course by the issues below. 2. No resource should r</pre> Tony Stocker 2013-05-20T13:49:08 http://comments.gmane.org/gmane.linux.highavailability.user/39025 <pre>I have a heartbeat 2.1.3-1 cluster and it was running fine until a recent network outage. Since then one node has been getting errors such as heartbeat: [3824]: ERROR: Message hist queue is filling up (500 messages in queue) I have looked through other mailing lists on the internet and have found that it most likely stems from missing sockets in /var/run/heartbeat (notably /var/run/heartbeat/register) I have uninstalled the rpm and re-installed it, rebooted the machine and run an strace on the heartbeat process to no avail. It appears that heartbeat does not try to create the socket files if they are missing. Could someone help me understand which component of heartbeat is responsible for creating socket files? Thanks, Chris _______________________________________________ Linux-HA mailing list Linux-HA&lt; at &gt;lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems </pre> Wilson, Christopher (IT 2013-05-16T20:05:39 http://comments.gmane.org/gmane.linux.highavailability.user/39020 <pre>Hi, I'd like to hear from you if someone has already experienced someting similar or -in case- to get how to do better. I need to sync a few files from time to time. Non need for a storage or a DRBD solution. Active/Passive cluster, I created a OCF master/slave resource from the template called "syncer", adding in the RA_syncer::monitor() method a couple of rsync commands as the following example: ... "/usr/bin/rsync -avz --delete ${SOURCE_CFG_FOLDER_X}/ ${OTHER_NODE}::ALIAS_X" ... The ocf-tester says the RA is ok. Then I add a constraint to pacecemaker, so that the resource_ms_syncer is Master only if the other resources are master on the same node. I have performed several tests, and the sync seems to work fine either on node A or on node B if I perform some swaps in order to validate the solution. But in one case something goes wrong: while A is master, if I shut down the B node after a while the RA::monitor timer on the A node seems to stop working. Of course I expect to get some OCF log errors</pre> Guglielmo Abbruzzese 2013-05-16T09:57:32 http://comments.gmane.org/gmane.linux.highavailability.user/38999 <pre>Hi! I think there is a bug in crm shell's "rename": I renamed a colocation constraint named "col_Xen_VMs_cfs2" to "col_Xen_VMs_cfs_mir" After that I see: &lt;rsc_colocation id="col_Xen_VMs_cfs_mir" (...) &lt;resource_set id="col_Xen_VMs_cfs2-0" sequential="false" &gt; (...) I wonder: Shouldn't the resource_set id be renamed as well? Found in crmsh-1.2.4-0.6.42 (SLES11 SP2) Regards, Ulrich _______________________________________________ Linux-HA mailing list Linux-HA&lt; at &gt;lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems </pre> Ulrich Windl 2013-05-15T07:53:31 http://comments.gmane.org/gmane.linux.highavailability.user/38997 <pre>Hi, If a resource fails to stop, the node hosting it is fenced immediately. Isn't it possible to move the other resources off the node before it's fenced? Something like on-fail=standby, but with additional fencing at the end, so that the failed resource can be restarted elsewhere. </pre> Ferenc Wagner 2013-05-15T07:23:27 http://comments.gmane.org/gmane.linux.highavailability.user/38996 <pre>Hi, I learnt that it's possible to change non-unique parameters of a resource without restarting it if the agent implements the reload action. On the other hand, adding a monitor operation does not seem to have an effect until the resource is restarted. Is there a good reason for this, or am I doing something wrong? </pre> Ferenc Wagner 2013-05-15T07:19:09 http://comments.gmane.org/gmane.linux.highavailability.user/38988 <pre> This is about pull request https://github.com/ClusterLabs/resource-agents/pull/222 "Merge redhat lvm.sh feature set into heartbeat LVM agent" Apologies to the CC for list duplicates. Cc list was made by looking at the comments in the pull request, and some previous off-list thread. Even though this is about resource agent feature development, and thus actually a topic for the -dev list, I wanted to give this the maybe wider audience of the users list, to encourage feedback from people who actually *use* this feature with rgmanager, or intend to use it once it is in the pacemaker RA. Here is my perception of this pull request, as such very subjective, and I may have gotten some intentions or facts wrong, so please correct me, or add whatever I may have missed. Appart from a larger restructuring of the code, this introduces the feature of "exclusive activation" of LVM volume groups. From the commit message: This patch leaves the original LVM heartbeat functionality intact while adding these additi</pre> Lars Ellenberg 2013-05-14T11:22:08 http://comments.gmane.org/gmane.linux.highavailability.user/38985 <pre>Hello.My system os is Centos 6.4 X64,when I install corosync and pacemaker using this command(as offical document guide): yum -y install corosync* pacemaker* but I can't find crm command. why? help me! Tks!Best regards! the following is some information [root&lt; at &gt;slave log]# uname -a Linux slave 2.6.32-358.el6.x86_64 #1 SMP Fri Feb 22 00:31:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux [root&lt; at &gt;slave log]# [root&lt; at &gt;slave log]# yum -y install corosync* pacemaker* Loaded plugins: fastestmirror, security Loading mirror speeds from cached hostfile * base: mirrors.yun-idc.com * extras: mirrors.yun-idc.com * updates: mirrors.yun-idc.com Setting up Install Process Package corosynclib-1.4.1-15.el6.x86_64 already installed and latest version Package corosync-1.4.1-15.el6.x86_64 already installed and latest version Package corosynclib-devel-1.4.1-15.el6.x86_64 already installed and latest version Package pacemaker-cluster-libs-1.1.8-7.el6.x86_64 already installed and latest version Package pacemaker-libs-1.1.8-7.el6.x86_64 </pre> zhangyan 2013-05-12T04:33:05 http://comments.gmane.org/gmane.linux.highavailability.user/38982 <pre>Hi, Is there a heartbeat cluster resource agent that is able to manage multiple IP addresses at once? When we configure IP addresses as cluster resources with ocf:heartbeat:IPaddr2 it takes about a second for every addresses to switch to another node. We are building a server with potentially hundreds of service IPs. The resource agent ocf:heartbeat:IPaddr2 is not scaling very well in this scenario. Regards </pre> Robert Sander 2013-05-13T13:46:40 http://comments.gmane.org/gmane.linux.highavailability.user/38981 <pre>Hi I am compiling cluster-glue under fedora 18, and it returns an error. It seems that the specification of "FORTIFY_SOURCE" is changed. How should I fix ? I use these operations under glibc-2.16-31.fc18.x86_64. ----------------------------- # hg clone http://hg.linux-ha.org/glue cluster-glue # cd cluster-glue # make rpm rm -f cluster-glue.tar.bz2 hg archive -t tbz2 -r tip cluster-glue.tar.bz2 &lt;snip&gt; libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../include -I../include -I../include -I../linux-ha -I../linux-ha -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/libxml2 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -ggdb3 -O0 -fgnu89-inline -fstack-protector-all -Wall -Waggregate-return -Wbad-function-cast -Wcast-qual -Wcast-align -Wdeclaration-after-statement -Wendif-labels -Wfloat-equal -Wformat=2 -Wformat-security -Wformat-nonliteral -Winline -Wmissing-prototypes -Wmissing-declarations -Wmissing-format-a</pre> Takatoshi MATSUO 2013-05-13T11:58:50 http://comments.gmane.org/gmane.linux.highavailability.user/38976 <pre> Ich werde ab 08.05.2013 nicht im Büro sein. Ich kehre zurück am 21.05.2013. _______________________________________________ Linux-HA mailing list Linux-HA&lt; at &gt;lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems </pre> Robert.Koeppl< at >knapp.com 2013-05-12T23:13:20 http://comments.gmane.org/gmane.linux.highavailability.user/38974 <pre> Ich werde ab 08.05.2013 nicht im Büro sein. Ich kehre zurück am 13.05.2013. _______________________________________________ Linux-HA mailing list Linux-HA&lt; at &gt;lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems </pre> Robert.Koeppl< at >knapp.com 2013-05-10T13:40:20 http://comments.gmane.org/gmane.linux.highavailability.user/38973 <pre>Hi, An hour ago one node (n02) of our 4-node cluster started to shutdown. No idea why. But during shutdown, it asked another node (n01) to shut down as well: May 10 13:59:42 n02 pacemakerd: [10851]: info: crm_signal_dispatch: Invoking handler for signal 15: Terminated May 10 13:59:42 n02 pacemakerd: [10851]: notice: pcmk_shutdown_worker: Shuting down Pacemaker May 10 13:59:42 n02 pacemakerd: [10851]: notice: stop_child: Stopping crmd: Sent -15 to process 10860 May 10 13:59:42 n02 crmd: [10860]: info: crm_signal_dispatch: Invoking handler for signal 15: Terminated May 10 13:59:42 n02 crmd: [10860]: notice: crm_shutdown: Requesting shutdown, upper limit is 1200000ms May 10 13:59:42 n02 crmd: [10860]: debug: crm_timer_start: Started Shutdown Escalation (I_STOP:1200000ms), src=50 May 10 13:59:42 n02 crmd: [10860]: debug: s_crmd_fsa: Processing I_SHUTDOWN: [ state=S_NOT_DC cause=C_SHUTDOWN origin=crm_shutdown ] May 10 13:59:42 n02 crmd: [10860]: debug: do_fsa_action: actions:trace: #011// A_SHUTDOWN_REQ May 10</pre> Ferenc Wagner 2013-05-10T13:37:36 http://comments.gmane.org/gmane.linux.highavailability.user/38960 <pre>Hi! After installing (amoung others) a libxslt security fix for SLES11 SP2, "zypper ps" tells me sbd is using libxslt. I'm surprised: I thought sbd was just processing simple command line arguments... # zypper ps The following running processes use deleted files: PID | PPID | UID | Login | Command | Service | Files ------+-------+-----+-----------+---------------------+----------+---------------------------------- 11481 | 1 | 0 | root | sshd | sshd | /lib64/libaudit.so.0.0.0 12793 | 1 | 0 | root | cupsd | cups | /lib64/libaudit.so.0.0.0 12803 | 1 | 0 | root | dlm_controld.pcmk | | /usr/lib64/libxslt.so.1.1.24 | | | | | | /lib64/libaudit.so.0.0.0 | | | | | | /usr/lib64/libgnutls.so.26.4.5 12808 | 1 | 0 | root | libvirtd | libvirtd | /lib64/libaudit.so.0.0.0 | | |</pre> Ulrich Windl 2013-05-02T07:36:58 http://comments.gmane.org/gmane.linux.highavailability.user/38953 <pre>Hi all, I have a two node setup with replicated PostgreSQL DB (master/slave setup). Focus is on keeping the system up and running, not on capacity. All good, that works fine. Now, a new requirement shows up: the two nodes should be connected using two physically separated networks, and should survive failure of one of the two networks. The two nodes communicate together for PostgreSQL replication. Initially, the slave will communicate with the master on network 1, and if network 1 fails, it should switch to network 2. Obviously, I cannot use a virtual-ip over two different networks. What would be the closest solution in term of features ? I was thinking about having a resource agent managing a port forward rule on slave node, something like localhost:5433 =&gt; master_ip_on_network1:5432, that would switch to localhost:5433 =&gt; master_ip_on_network2:5432, so that it would be transparent for the replication tool. Do you know if such a resource agent is already implemented somewhere ? Do you have remarks, </pre> Richard Comblen 2013-04-30T11:58:02 http://comments.gmane.org/gmane.linux.highavailability.user/38931 <pre>We are installing corosync and pacemaker on a brand new RHEL 6.3 cluster today. When we installed using yum, here are the versions that pulled down from the repos. pacemaker-libs-1.1.9-1512.el6.x86_64 pacemaker-1.1.9-1512.el6.x86_64 corosync-1.4.3-26.2.x86_64 pacemaker-cluster-libs-1.1.9-1512.el6.x86_64 corosynclib-1.4.3-26.2.x86_64 pacemaker-cli-1.1.9-1512.el6.x86_64 Are those versions the best (most stable) ones, or should we be pointed at a different repo? Here are the repos we have enabled... -rw-r--r--. 1 root root 1769 Jan 8 03:13 CentOS-Base.repo -rw-r--r--. 1 root root 192 Jan 8 03:13 clusterlabs-next.repo -rw-r--r--. 1 root root 1250 Jan 8 03:13 dump.cap -rw-r--r--. 1 root root 954 Jan 8 03:13 epel.repo -rw-r--r--. 1 root root 1054 Jan 8 03:13 epel-testing.repo -rw-r--r--. 1 root root 332 Jan 8 03:13 ha-clustering.repo -rw-r--r--. 1 root root 684 Jan 8 03:13 mirrors-rpmforge -rw-r--r--. 1 root root 717 Jan 8 03:13 mirrors-rpmforge-extras -rw-r--r--. 1 root root 728 Jan 8 03:13 </pre> Robinson, Eric 2013-04-25T22:08:54 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.linux.highavailability.user