Re: [Pacemaker] active cluster and load-balancer
On 29.06.2011 05:28, Arizka Ashar wrote: Hello All, in active-active each node have clone vip.. node1 = 1.2.3.4 node2 = 5.6.7.8 node3 = 9.10.11.12 clone vip = 13.14.15.16 honestly, that depends on your network setup and on the lvs forwarding type. (e.g. are the node's real ips routable?) what i would do: 1. configure the clone vip using a tun device on the real servers (pay attention to the arp configuration!) (13.14.15.16 = tunl0) 2. add the vip to the load balancers. make this setup redundant using pacemaker. (floating vip, ldirectord, etc.) (lb ip = x.x.x.x, y.y.y.y; 13.14.15.16 = floating vip, not cloned) 3. point the lvs setup to the node's ips (1.2.3.4, 5.6.7.8, 9.10.11.12) a similar setup is running at my company (except for the tunl devices which are not managed by pacemaker) cheers, raoul ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
[Pacemaker] active cluster and load-balancer
Hello All, in active-active each node have clone vip.. node1 = 1.2.3.4 node2 = 5.6.7.8 node3 = 9.10.11.12 clone vip = 13.14.15.16 let say we want to setup load-balancer for resource ex: apache we need point our lvs load balancer to resource vip (13.14.15.16) or node real ip ? Thanks Regard Arizka ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] Patch for bugzilla 2541: Shell should warn if parameter uniqueness is violated
Well, never mind ... There appears to be an easy fix for this "violate uniqueness for parameter" issue with stonith:/external/ipmi. As noted earlier in this thread WRT fence_ipmilan, the parmeters in stonith:external/ipmi have all been set to "unique". Unsetting the uniqueness seems to solve the issue. For example, setting unique to 0: Is proper protocol for me to file a bug with Novell as this is code from Novell? Regards, Bob Haxo On Tue, 2011-06-28 at 17:53 -0700, Bob Haxo wrote: > All, > > I'm seeing a problem referred to in this thread: > > crm(live)configure# primitive stonith-ipmi-1 stonith:external/ipmi \ > > meta target-role="started" is-managed="true" \ > > operations $id="stonith-ipmi-1-operations" \ > > op monitor interval="15" timeout="15" on-fail="restart" start-delay="15" \ > > op start interval="0" timeout="15" on-fail="restart" \ > > params hostname="r1lead2-bmc" ipaddr="172.24.0.10" userid="X" > > passwd="X" passwd_method="param" interface="lanplus" > > crm(live)configure# commit > > crm(live)configure# primitive stonith-ipmi-2 stonith:external/ipmi \ > > meta target-role="started" is-managed="true" \ > > operations $id="stonith-ipmi-2-operations" \ > > op monitor interval="15" timeout="15" on-fail="restart" start-delay="15" \ > > op start interval="0" timeout="15" on-fail="restart" \ > > params hostname="r1lead1-bmc" ipaddr="172.24.0.7" userid="X" > > passwd="X" passwd_method="param" interface="lanplus" > > crm(live)configure# commit > WARNING: Resources stonith-ipmi-1,stonith-ipmi-2 violate uniqueness for > parameter "passwd": "X" > WARNING: Resources stonith-ipmi-1,stonith-ipmi-2 violate uniqueness for > parameter "passwd_method": "param" > WARNING: Resources stonith-ipmi-1,stonith-ipmi-2 violate uniqueness for > parameter "interface": "lanplus" > WARNING: Resources stonith-ipmi-1,stonith-ipmi-2 violate uniqueness for > parameter "userid": "X" > Do you still want to commit? yes > crm(live)configure# > > The problem is that I want to perform this operation as "crm < > commands", which returns the warnings and assumes a "NO" to the > question. > > I have current Novell updates applied, which includes the cibconfig.py > d0472a26eda1 patch. I see no Novell bug for this issue. > > Have I missed the fix under a different thread? > > Any suggestions will be appreciated. Thanks. > > Bob Haxo > > > > > > > > > > > On Fri, 2011-04-01 at 10:33 +0200, Andrew Beekhof wrote: > > On Tue, Mar 29, 2011 at 6:03 PM, Vladislav Bogdanov > > wrote: > > > Hi, > > > > > > 29.03.2011 18:33, Dejan Muhamedagic wrote: > > >> Hi, > > >> > > >> On Sat, Mar 26, 2011 at 08:41:45AM +0200, Vladislav Bogdanov wrote: > > >>> Oops, this is actually a bug in fence_ipmilan which reports all params > > >>> as unique. > > >> > > >> Well, that's bad, but then we don't want to annoy people until > > >> this issue has been resolved. The meta-data stuff usually needs > > >> a bit more attention, as far as I could see. I think that we'd > > >> need to make this check optional. > > > > > > I planned to post patch to redhat's bugzilla in nearest days (together > > > with bunch of other fixes and features). Should I send it (them) > > > somewhere else too? > > > > Nah, RHBZ should be enough. > > > > > > > >> > > >> What's your experience? Does it show these messages only once or > > >> all the time? > > > > > > Only once after resource either defined or changed. > > > It also cries something about start and stop operations, do not remember > > > now, sorry, short on time right now. > > > > > > > > > Vladislav > > > > > > ___ > > > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > > > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > > > > > Project Home: http://www.clusterlabs.org > > > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > > > Bugs: > > > http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker > > > > > > > ___ > > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > > > Project Home: http://www.clusterlabs.org > > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > > Bugs: > > http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] Patch for bugzilla 2541: Shell should warn if parameter uniqueness is violated
All, I'm seeing a problem referred to in this thread: crm(live)configure# primitive stonith-ipmi-1 stonith:external/ipmi \ > meta target-role="started" is-managed="true" \ > operations $id="stonith-ipmi-1-operations" \ > op monitor interval="15" timeout="15" on-fail="restart" start-delay="15" \ > op start interval="0" timeout="15" on-fail="restart" \ > params hostname="r1lead2-bmc" ipaddr="172.24.0.10" userid="X" > passwd="X" passwd_method="param" interface="lanplus" crm(live)configure# commit crm(live)configure# primitive stonith-ipmi-2 stonith:external/ipmi \ > meta target-role="started" is-managed="true" \ > operations $id="stonith-ipmi-2-operations" \ > op monitor interval="15" timeout="15" on-fail="restart" start-delay="15" \ > op start interval="0" timeout="15" on-fail="restart" \ > params hostname="r1lead1-bmc" ipaddr="172.24.0.7" userid="X" > passwd="X" passwd_method="param" interface="lanplus" crm(live)configure# commit WARNING: Resources stonith-ipmi-1,stonith-ipmi-2 violate uniqueness for parameter "passwd": "X" WARNING: Resources stonith-ipmi-1,stonith-ipmi-2 violate uniqueness for parameter "passwd_method": "param" WARNING: Resources stonith-ipmi-1,stonith-ipmi-2 violate uniqueness for parameter "interface": "lanplus" WARNING: Resources stonith-ipmi-1,stonith-ipmi-2 violate uniqueness for parameter "userid": "X" Do you still want to commit? yes crm(live)configure# The problem is that I want to perform this operation as "crm < commands", which returns the warnings and assumes a "NO" to the question. I have current Novell updates applied, which includes the cibconfig.py d0472a26eda1 patch. I see no Novell bug for this issue. Have I missed the fix under a different thread? Any suggestions will be appreciated. Thanks. Bob Haxo On Fri, 2011-04-01 at 10:33 +0200, Andrew Beekhof wrote: > On Tue, Mar 29, 2011 at 6:03 PM, Vladislav Bogdanov > wrote: > > Hi, > > > > 29.03.2011 18:33, Dejan Muhamedagic wrote: > >> Hi, > >> > >> On Sat, Mar 26, 2011 at 08:41:45AM +0200, Vladislav Bogdanov wrote: > >>> Oops, this is actually a bug in fence_ipmilan which reports all params > >>> as unique. > >> > >> Well, that's bad, but then we don't want to annoy people until > >> this issue has been resolved. The meta-data stuff usually needs > >> a bit more attention, as far as I could see. I think that we'd > >> need to make this check optional. > > > > I planned to post patch to redhat's bugzilla in nearest days (together > > with bunch of other fixes and features). Should I send it (them) > > somewhere else too? > > Nah, RHBZ should be enough. > > > > >> > >> What's your experience? Does it show these messages only once or > >> all the time? > > > > Only once after resource either defined or changed. > > It also cries something about start and stop operations, do not remember > > now, sorry, short on time right now. > > > > > > Vladislav > > > > ___ > > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > > > Project Home: http://www.clusterlabs.org > > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > > Bugs: > > http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker > > > > ___ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: > http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] Pacemaker and LDAP (389 Directory Service)
I have a similar setup running with this simple configuration: node mexico node washington primitive LDAP lsb:openldap \ op monitor interval="30s" primitive masterIP ocf:heartbeat:IPaddr \ params ip="XXX.XXX.XXX.XXX" cidr_netmask="21" \ meta migration-threshold="3" primitive pingd ocf:pacemaker:ping \ params dampen="5s" multiplier="1000" host_list="XXX.XXX.XXX.XXX" \ op monitor interval="20s" timeout="15s" clone LDAP-clone LDAP \ meta target-role="Started" is-managed="true" clone pingd-clone pingd \ meta target-role="Started" location cli-prefer-masterIP masterIP \ rule $id="cli-prefer-rule-masterIP" inf: #uname eq washington location connected masterIP \ rule $id="connected-rule" -inf: not_defined pingd or pingd lte 0 location primNode masterIP \ rule $id="prefered_primNode" 500: #uname eq washington colocation IP_with_LDAP inf: masterIP LDAP-clone Not on Amazon cloud but on a real hardware though. You can ignore pingd part. On Mon, Jun 27, 2011 at 4:56 PM, veghead wrote: > Serge Dubrouski writes: > > On Mon, Jun 27, 2011 at 3:33 PM, veghead studyblue.com> > wrote: > > If I remove the co-location, won't the elastic_ip resource just stay > where it > > is? Regardless of what happens to LDAP? > > > > Right. That's why I think that you don't really want to do it. You have > > to make sure that your IP is up where you LDAP is up. > > Okay. So I took a step and revamped the configuration to test the > elastic_ip > less frequently and with a long timeout. I committed the changes, but "crm > status" doesn't reflect the resources in question. > > Here's the new config: > > ---snip--- > # crm configure show > node $id="d2b294cf-328f-4481-aa2f-cc7b553e6cde" ldap1.example.ec2 > node $id="e2a2e42e-1644-4f7d-8e54-71e1f7531e08" ldap2.example.ec2 > primitive elastic_ip lsb:elastic-ip \ >op monitor interval="30" timeout="300" on-fail="ignore" > requires="nothing" > primitive ldap lsb:dirsrv \ >op monitor interval="15s" on-fail="standby" requires="nothing" > clone ldap-clone ldap > colocation ldap-with-eip inf: elastic_ip ldap-clone > order ldap-after-eip inf: elastic_ip ldap-clone > property $id="cib-bootstrap-options" \ >dc-version="1.0.11-1554a83db0d3c3e546cfd3aaff6af1184f79ee87" \ >cluster-infrastructure="Heartbeat" \ >stonith-enabled="false" \ >no-quorum-policy="ignore" \ >stop-all-resources="true" > rsc_defaults $id="rsc-options" \ >resource-stickiness="100" > ---snip--- > > And here's the output from "crm status": > > ---snip--- > # crm status > > Last updated: Mon Jun 27 18:50:14 2011 > Stack: Heartbeat > Current DC: ldap2.studyblue.ec2 (e2a2e42e-1644-4f7d-8e54-71e1f7531e08) - > partition with quorum > Version: 1.0.11-1554a83db0d3c3e546cfd3aaff6af1184f79ee87 > 2 Nodes configured, unknown expected votes > 2 Resources configured. > > > Online: [ ldap1.example.ec2 ldap2.example.ec2 ] > ---snip--- > > I restarted the nodes one at a time - first I restarted ldap2, then I > restarted > ldap1. When ldap1 went down, ldap2 stopped the ldap resource and didn't > make any > attempt to start the elastic_ip resource: > > ---snip--- > pengine: [12910]: notice: unpack_config: On loss of CCM Quorum: Ignore > pengine: [12910]: info: unpack_config: Node scores: 'red' = -INFINITY, > 'yellow' > = 0, 'green' = 0 > pengine: [12910]: info: determine_online_status: Node ldap2.example.ec2 is > online > pengine: [12910]: notice: native_print: elastic_ip (lsb:elastic-ip): > Stopped > pengine: [12910]: notice: clone_print: Clone Set: ldap-clone > pengine: [12910]: notice: short_print: Stopped: [ ldap:0 ldap:1 ] > pengine: [12910]: notice: LogActions: Leave resource elastic_ip > (Stopped) > pengine: [12910]: notice: LogActions: Leave resource ldap:0(Stopped) > pengine: [12910]: notice: LogActions: Leave resource ldap:1(Stopped) > ---snip--- > > After heartbeat/pacemaker came back up on ldap1, it terminated the ldap > service > on ldap1. Now I'm just confused. > > > ___ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: > http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker > -- Serge Dubrouski. ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] Not connected to AIS
On 06/27/2011 09:15 AM, Andrew Beekhof wrote: On Fri, Jun 24, 2011 at 6:56 PM, Proskurin Kirill wrote: Hello. I have a strange problem. One node in cluster are not work right. In logs: Jun 23 20:25:25 mysender39.example.com lrmd: [10371]: WARN: For LSB init script, no additional parameters are needed. Jun 23 20:25:25 mysender39.example.com lrmd: [30679]: info: RA output: (onlineconf.init:3:stop:stdout) Stopping onlineconf_updater: Jun 23 20:25:25 mysender39.example.com lrmd: [30679]: info: RA output: (onlineconf.init:3:stop:stdout) [ Jun 23 20:25:25 mysender39.example.com lrmd: [30679]: info: RA output: (onlineconf.init:3:stop:stdout) OK Jun 23 20:25:25 mysender39.example.com lrmd: [30679]: info: RA output: (onlineconf.init:3:stop:stdout) ] Jun 23 20:25:25 mysender39.example.com crmd: [30682]: info: process_lrm_event: LRM operation onlineconf.init:3_stop_0 (call=181, rc=0, cib-update=683339, confirm ed=true) ok Jun 23 20:25:25 mysender39.example.com cib: [30678]: ERROR: send_ais_message: Not connected to AIS And then many errors and this string over and over. Not enough information. Please include a crm_report for the time between 20:20:00 and 20:30:00 on June 23. I attached logs to this mail. Hope it helps. -- Best regards, Proskurin Kirill report.tar.bz2 Description: application/bzip ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
[Pacemaker] [PATCH] Dev: build: avoid GCC 4.6 warnings
# HG changeset patch
# User Pádraig Brady
# Date 1309255312 -3600
# Node ID 7948a86a7e9510db13baa318fe64e9015fdbbd72
# Parent 75575ce398615dff21e2309c6b97523e99499498
Dev: build: avoid GCC 4.6 warnings
diff -r 75575ce39861 -r 7948a86a7e95 crmd/election.c
--- a/crmd/election.c Tue Jun 21 15:54:20 2011 +0200
+++ b/crmd/election.c Tue Jun 28 11:01:52 2011 +0100
@@ -445,6 +445,8 @@
}
last_election_win = time(NULL);
+#else
+(void) last_election_win;
#endif
register_fsa_input(C_FSA_INTERNAL, I_ELECTION, NULL);
g_hash_table_destroy(voted);
diff -r 75575ce39861 -r 7948a86a7e95 crmd/lrm.c
--- a/crmd/lrm.cTue Jun 21 15:54:20 2011 +0200
+++ b/crmd/lrm.cTue Jun 28 11:01:52 2011 +0100
@@ -621,6 +621,8 @@
if(non_empty) {
crm_log_xml_debug(restart, "restart digest source");
}
+#else
+(void) non_empty;
#endif
free_xml(restart);
@@ -1275,7 +1277,7 @@
fsa_cib_update(XML_CIB_TAG_STATUS, fragment,
cib_quorum_override, rc, user_name);
free_xml(fragment);
-
+ (void) rc;
} else if(safe_str_eq(crm_op, CRM_OP_LRM_QUERY)) {
xmlNode *data = do_lrm_query(FALSE);
xmlNode *reply = create_reply(input->msg, data);
diff -r 75575ce39861 -r 7948a86a7e95 crmd/te_actions.c
--- a/crmd/te_actions.c Tue Jun 21 15:54:20 2011 +0200
+++ b/crmd/te_actions.c Tue Jun 28 11:01:52 2011 +0100
@@ -240,7 +240,6 @@
lrm_op_t *op = NULL;
xmlNode *state= NULL;
xmlNode *rsc = NULL;
- xmlNode *xml_op = NULL;
xmlNode *action_rsc = NULL;
enum cib_errors rc = cib_ok;
@@ -310,7 +309,7 @@
op->user_data = generate_transition_key(
transition_graph->id, action->id, target_rc, te_uuid);
- xml_op = create_operation_update(
+ create_operation_update(
rsc, op, CRM_FEATURE_SET, target_rc, __FUNCTION__, LOG_INFO);
free_lrm_op(op);
diff -r 75575ce39861 -r 7948a86a7e95 lib/cib/cib_ops.c
--- a/lib/cib/cib_ops.c Tue Jun 21 15:54:20 2011 +0200
+++ b/lib/cib/cib_ops.c Tue Jun 28 11:01:52 2011 +0100
@@ -169,7 +169,6 @@
xmlNode *existing_cib, xmlNode **result_cib, xmlNode **answer)
{
const char *tag = NULL;
-gboolean verbose = FALSE;
enum cib_errors result = cib_ok;
crm_debug_2("Processing \"%s\" event for section=%s",
@@ -188,9 +187,6 @@
tag = crm_element_name(input);
-if (options & cib_verbose) {
- verbose = TRUE;
-}
if(safe_str_eq(XML_CIB_TAG_SECTION_ALL, section)) {
section = NULL;
diff -r 75575ce39861 -r 7948a86a7e95 lib/cib/cib_remote.c
--- a/lib/cib/cib_remote.c Tue Jun 21 15:54:20 2011 +0200
+++ b/lib/cib/cib_remote.c Tue Jun 28 11:01:52 2011 +0100
@@ -364,20 +364,27 @@
if(private->passwd == NULL) {
struct termios settings;
- int rc;
-
- rc = tcgetattr (0, &settings);
+ int rtc;
+
+ rtc = tcgetattr (0, &settings);
settings.c_lflag &= ~ECHO;
- rc = tcsetattr (0, TCSANOW, &settings);
+ if (rtc == 0) {
+ rtc = tcsetattr (0, TCSANOW, &settings);
+ }
- fprintf(stderr, "Password: ");
- crm_malloc0(private->passwd, 1024);
- scanf("%s", private->passwd);
- fprintf(stdout, "\n");
- /* fprintf(stderr, "entered: '%s'\n", buffer); */
+ if (rtc) {
+ fprintf(stderr, "Error disabling terminal echo: [%d]\n", errno);
+ rc = cib_unknown;
+ } else {
+ fprintf(stderr, "Password: ");
+ crm_malloc0(private->passwd, 1024);
+ scanf("%s", private->passwd);
+ fprintf(stdout, "\n");
+ /* fprintf(stderr, "entered: '%s'\n", buffer); */
- settings.c_lflag |= ECHO;
- rc = tcsetattr (0, TCSANOW, &settings);
+ settings.c_lflag |= ECHO;
+ tcsetattr (0, TCSANOW, &settings);
+ }
}
if(private->server == NULL || private->user == NULL) {
diff -r 75575ce39861 -r 7948a86a7e95 lib/common/utils.c
--- a/lib/common/utils.cTue Jun 21 15:54:20 2011 +0200
+++ b/lib/common/utils.cTue Jun 28 11:01:52 2011 +0100
@@ -2253,7 +2253,7 @@
return TRUE;
}
-crm_info("Could not send update: %s=%s for %s", name, value,
host?host:"localhost");
+crm_info("Could not send update: %s=%s for %s: %s", name, value,
host?host:"localhost", reason);
return FALSE;
}
diff -r 75575ce39861 -r 7948a86a7e95 lib/common/xml.c
--- a/lib/common/xml.c Tue Jun 21 15:54:20 2011 +0200
+++ b/lib/common/xml.c Tue Jun 28 11:01:52 2011 +0100
@@ -1168,7 +1168,6 @@
const char *prefix, xmlNode *data, int depth, gboolean formatted)
{
xmlNode *a_child = NULL;
-int child_result = 0;
int offset = 0;
int printed = 0;
@@ -1230,7 +1229,7 @@
}
for(a_child = __xml_first_child(data); a_child != NULL; a_child =
__xml_next
Re: [Pacemaker] Problem with Web Site start
Hi, On Tue, Jun 28, 2011 at 09:58:47AM +0200, Alfredo Parisi wrote: > Hi at all, tomorrow i've this problem...web site doesn't start and > i've these errors. > Where can I check to resolve it? Thank you. > > > Last updated: Tue Jun 28 09:57:17 2011 > Stack: openais > Current DC: server2 - partition with quorum > Version: 1.0.9-unknown > 2 Nodes configured, 2 expected votes > 2 Resources configured. > > > Online: [ server2 server1 ] > > Master/Slave Set: ms_drbd_mysql > Masters: [ server1 ] > Slaves: [ server2 ] > Resource Group: mysql > vip(ocf::heartbeat:IPaddr2): Started server1 > fs_mysql (ocf::heartbeat:Filesystem):Started server1 > mysqld (ocf::heartbeat:mysql): Started server1 > WebSite(ocf::heartbeat:apache):Stopped > > Failed actions: > WebSite_start_0 (node=server1, call=17, rc=-2, status=Timed Out): unknown > ex > ec error > WebSite_start_0 (node=server2, call=17, rc=-2, status=Timed Out): unknown > ex Most probably the apache status page wasn't setup. Check out the documentation for the RA: crm ra info apache. Thanks, Dejan > ___ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: > http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Re: [Pacemaker] IPC Channel is not connected
Hi, On Mon, Jun 27, 2011 at 03:31:05PM +0200, Kulovits Christian - OS ITSC wrote: > Hello Dejan, > please, can you explain what process you mean? Any process talking to the cib. It could be another pacemaker subsystem or a client. Since this is happening that often, it's probably some client. Otherwise, your cluster will be in a yo-yo mode. Thanks, Dejan > > Christian > > -Original Message- > From: Dejan Muhamedagic [mailto:deja...@fastmail.fm] > Sent: Montag, 27. Juni 2011 14:44 > To: The Pacemaker cluster resource manager > Subject: Re: [Pacemaker] IPC Channel is not connected > > Hi, > > On Mon, Jun 27, 2011 at 08:17:38AM -0400, imnotpc wrote: > > On Monday, June 27, 2011 08:08:46 Dejan Muhamedagic wrote: > > > Hi, > > > > > > On Mon, Jun 27, 2011 at 10:42:46AM +0200, Kulovits Christian - OS > > > ITSC > > wrote: > > > > Hello > > > > > > > > In the corosync log file i can find many lines like this: > > > > > > > > Jun 27 10:38:41 amosn3 cib: [1842]: WARN: send_ipc_message: IPC > > > > Channel to 414 is not connected > > > > > > > > Any idea what this means? > > > > > > Probably the other process crashed. > > > > Are these normal warnings when testing fencing, etc? > > No. IIRC, the only times I've seen such messages is when a process crashed. > > Thanks, > > Dejan > > > Jeff > > > > ___ > > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > > > Project Home: http://www.clusterlabs.org Getting started: > > http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > > Bugs: > > http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacema > > ker > > ___ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org Getting started: > http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: > http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker > > > Austrian Airlines AG, Office Park 2, P.O. Box 100, 1300 Vienna-Airport, > Austria, registered office: Vienna, registered with Vienna Commercial Court > under FN 111000k, DVR 0091740. This e-mail is confidential and is subject to > disclaimers. Details can be found at: http://www.austrian.com/disclaimer. > > > ___ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: > http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
[Pacemaker] Problem with Web Site start
Hi at all, tomorrow i've this problem...web site doesn't start and i've these errors. Where can I check to resolve it? Thank you. Last updated: Tue Jun 28 09:57:17 2011 Stack: openais Current DC: server2 - partition with quorum Version: 1.0.9-unknown 2 Nodes configured, 2 expected votes 2 Resources configured. Online: [ server2 server1 ] Master/Slave Set: ms_drbd_mysql Masters: [ server1 ] Slaves: [ server2 ] Resource Group: mysql vip(ocf::heartbeat:IPaddr2): Started server1 fs_mysql (ocf::heartbeat:Filesystem):Started server1 mysqld (ocf::heartbeat:mysql): Started server1 WebSite(ocf::heartbeat:apache):Stopped Failed actions: WebSite_start_0 (node=server1, call=17, rc=-2, status=Timed Out): unknown ex ec error WebSite_start_0 (node=server2, call=17, rc=-2, status=Timed Out): unknown ex ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
