<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Jan,<br>
Here is the output from your command:<br>
<br>
attrd: 609413<br>
cib: 609409<br>
corosync: 608778<br>
crmd: 609415<br>
lrmd: 609412<br>
pengine: 609414<br>
pacemakerd: 609407<br>
stonithd: 609411<br>
<br>
Regarding using a newer version, that's what I've been thinking
about, but I've been using this combination of corosync/pacemaker
for many years on a different hardware and hever had similar
problem.<br>
The main difference is that I have stonith enabled only the
problematic cluster, but I also suspect that the node, which
causes this problem may have some hardware issues.<br>
<br>
BTW my last few tests with the newest corosync/pacemaker gave me
very annoying delay, when commiting configuration changes (maybe
it's a known problem?).<br>
<br>
Best regards,<br>
Klecho<br>
<br>
<br>
On 17.02.2016 14:59, Jan Pokorný wrote:<br>
</div>
<blockquote cite="mid:20160217125937.GA4980@redhat.com" type="cite">
<pre wrap="">On 17/02/16 14:10 +0200, Klechomir wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Having strange issue lately.
I have two node cluster with some cloned resources on it.
One of my nodes suddenly starts reporting all its resources down (some of
them are actually running), stops logging and reminds in this this state
forever, while still responding to crm commands.
The curious thing is that restarting corosync/pacemaker doesn't change
anything.
Here are the last lines in the log after restart:
[...]
Feb 17 12:55:19 [609409] CLUSTER-1 cib: info:
cib_process_replace: Replaced 0.238.40 with 0.238.40 from CLUSTER-2
Feb 17 12:55:21 [609413] CLUSTER-1 attrd: warning: attrd_cib_callback:
Update shutdown=(null) failed: No such device or address
Feb 17 12:55:22 [609413] CLUSTER-1 attrd: warning: attrd_cib_callback:
Update terminate=(null) failed: No such device or address
Feb 17 12:55:25 [609413] CLUSTER-1 attrd: warning: attrd_cib_callback:
Update pingd=(null) failed: No such device or address
Feb 17 12:55:26 [609413] CLUSTER-1 attrd: warning: attrd_cib_callback:
Update fail-count-p_Samba_Server=(null) failed: No such device or address
Feb 17 12:55:26 [609413] CLUSTER-1 attrd: warning: attrd_cib_callback:
Update master-p_Device_drbddrv1=(null) failed: No such device or address
Feb 17 12:55:27 [609413] CLUSTER-1 attrd: warning: attrd_cib_callback:
Update last-failure-p_Samba_Server=(null) failed: No such device or address
Feb 17 12:55:27 [609413] CLUSTER-1 attrd: warning: attrd_cib_callback:
Update probe_complete=(null) failed: No such device or address
After that the logging on the problematic node stops.
</pre>
</blockquote>
<pre wrap="">
Note sure I follow, what does the following command produce:
for i in attrd cib corosync crmd lrmd pengine pacemakerd stonithd; do \
echo "${i}: $(pgrep ${i})"; done
?
</pre>
<blockquote type="cite">
<pre wrap="">Corosync is v2.1.0.26; Pacemaker v1.1.8
</pre>
</blockquote>
<pre wrap="">
Definitely try a most recent version of Pacemaker; what you are using
is 3.5 years old and plentiful fixes landed since then.
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list: <a class="moz-txt-link-abbreviated" href="mailto:Users@clusterlabs.org">Users@clusterlabs.org</a>
<a class="moz-txt-link-freetext" href="http://clusterlabs.org/mailman/listinfo/users">http://clusterlabs.org/mailman/listinfo/users</a>
Project Home: <a class="moz-txt-link-freetext" href="http://www.clusterlabs.org">http://www.clusterlabs.org</a>
Getting started: <a class="moz-txt-link-freetext" href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a>
Bugs: <a class="moz-txt-link-freetext" href="http://bugs.clusterlabs.org">http://bugs.clusterlabs.org</a>
</pre>
</blockquote>
<br>
</body>
</html>