Hi!
I had thought ordrring of clones would work, but it looks like it does not in
current SLES11 SP3 (1.1.11-3ca8c3b):
I have rules like:
order ord_DLM_cLVMd inf: cln_DLM cln_cLVMd
order ord_DLM_O2CB inf: cln_DLM cln_O2CB
order ord_DLM_cLVMd inf: cln_DLM cln_cLVMd
colocation col_O2CB_DLM inf:
Hi!
I just discoverd a 134MB core-dump of corosync on x86_64 (SLES11 SP2). The
backtrace looks like this:
Core was generated by `/usr/sbin/corosync'.
Program terminated with signal 11, Segmentation fault.
#0 0x7f1cb4a515a9 in memcpy () from /lib64/libc.so.6
(gdb) bt
#0 0x7f1cb4a515a9
Hi!
I have some strange problems with the current update of the cluster software in
SLES11 SP2 (I didn't see such problems before the update):
sbd monitoring went crazy (reporting running sbds when there were none,
compaining the unability to stop sbd when there was none), so I stopped it.
Hi!
In SLES11 SP2 when I try to display (show) a resource group that does not
exist, there is no error message, but when I try to delete a non-existing
object, I get an error message. That's inconsistent: Trying to display an
object that does not exist should also display an error.
Example:
Hi!
When deleting resources using the crm shell, show changed will show nothing:
crm(live)configure# delete prm_v05_npiv_2
INFO: resource references in location:cli-standby-grp_v05 updated
INFO: hanging location:cli-standby-grp_v05 deleted
crm(live)configure# verify
crm(live)configure# show
Hi,
I found these error messages in syslog on April 1st:
Apr 1 00:04:30 h06 pengine: [20168]: ERROR: crm_abort: gregorian_to_ordinal:
Triggered assert at iso8601.c:635 : a_date-days 0
[...]
Apr 1 01:49:30 h06 pengine: [20168]: ERROR: crm_abort: convert_from_gregorian:
Triggered assert at
Hello,
I'm wondering about these messages:
Feb 25 14:53:31 so4 corosync[12457]: [TOTEM ] Retransmit List: 2a5 28b 28d 28e
295 296 297 298 299 29a 29b 29c 29d 29e 29f 2a0 2a1 2a2 2a3 2a4 2a6
Feb 25 14:53:31 so4 corosync[12457]: [TOTEM ] Retransmit List: 2a6 28b 28d 28e
295 296 297 298 299 29a
Hi!
If you want to use node_ip_attribute, you should make sure the code has this
fix:
---
# diff -u /usr/lib/ocf/resource.d/heartbeat/Xen.orig
/usr/lib/ocf/resource.d/heartbeat/Xen
--- /usr/lib/ocf/resource.d/heartbeat/Xen.orig 2012-07-24 10:54:12.0
+0200
+++
Hi!
I have a question on the Xen RA: The docs say:
---(resource-agents-3.9.3-0.7.1 of SLES 11 SP2)---
node_ip_attribute (string): Node attribute containing target IP address
In case of a live migration, the system will default to using the IP
address associated with the hostname via DNS
Hi!
In pacemaker-1.1.6-1.29.1 (SLES11 SP2 x86_64) I see this for an idle cluster
with just one stonith resource being running when doing some unrelated change:
Aug 13 15:33:19 h3 cib: [31938]: info: apply_xml_diff: Digest mis-match:
expected 466ee3cf78eec0772f78b6fc965e9601, calculated
10 matches
Mail list logo