<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>
<div>Hi,</div>
<div> </div>
<div>i recompiled all packages, and now, it works...</div>
<div> </div>
<div>But my /var/run/crm is also in the new installation empty, is this ok?</div>
<div>
<div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="margin:0 0 10px 0;"><b>Gesendet:</b> Montag, 19. Januar 2015 um 11:07 Uhr<br/>
<b>Von:</b> "Thomas Manninger" <DBGTMaster@gmx.at><br/>
<b>An:</b> pacemaker@oss.clusterlabs.org<br/>
<b>Betreff:</b> Re: [Pacemaker] no nodes on both hosts</div>
<div name="quoted-content">
<div style="font-family: Verdana;font-size: 12.0px;">
<div>
<div>Hi,</div>
<div> </div>
<div>now, i see, in "/var/run/crm" there are no socket- files, the directory is empty.</div>
<div> </div>
<div>How can i debug the problem?</div>
<div>
<div style="margin: 10.0px 5.0px 5.0px 10.0px;padding: 10.0px 0 10.0px 10.0px;border-left: 2.0px solid rgb(195,217,229);">
<div style="margin: 0 0 10.0px 0;"><b>Gesendet:</b> Montag, 19. Januar 2015 um 10:18 Uhr<br/>
<b>Von:</b> "Thomas Manninger" <DBGTMaster@gmx.at><br/>
<b>An:</b> pacemaker@oss.clusterlabs.org<br/>
<b>Betreff:</b> Re: [Pacemaker] no nodes on both hosts</div>
<div>
<div style="font-family: Verdana;font-size: 12.0px;">
<div>
<div>Hi,</div>
<div> </div>
<div>in reinstalled in the same vm debian, and used the debian pacemaker & corosync packages, everything works fine.</div>
<div>Then, i recomilied the newest pacemaker & corosync packages with the same problem..</div>
<div> </div>
<div>Jan 19 10:13:31 [24271] pacemaker2 cib: info: cib_process_request: Completed cib_modify operation for section nodes: OK (rc=0, origin=pacemaker2/crmd/3, version=0.0.0)</div>
<div>This line means, that the node is added in the cib.xml?</div>
<div> </div>
<div>But there are no nodes:</div>
<div>root@pacemaker2:/var/lib/pacemaker/cib# cat cib.xml<br/>
<cib crm_feature_set="3.0.9" validate-with="pacemaker-2.0" epoch="0" num_updates="0" admin_epoch="0" cib-last-written="Mon Jan 19 10:13:30 2015"><br/>
<configuration><br/>
<crm_config/><br/>
<nodes/><br/>
<resources/><br/>
<constraints/><br/>
</configuration><br/>
</cib></div>
<div> </div>
<div>I also changed the permission of the cib folder to 777...</div>
<div> </div>
<div>Someone can help me??<br/>
Thanks!</div>
<div>
<div style="margin: 10.0px 5.0px 5.0px 10.0px;padding: 10.0px 0 10.0px 10.0px;border-left: 2.0px solid rgb(195,217,229);">
<div style="margin: 0 0 10.0px 0;"><b>Gesendet:</b> Freitag, 16. Januar 2015 um 16:51 Uhr<br/>
<b>Von:</b> "Thomas Manninger" <DBGTMaster@gmx.at><br/>
<b>An:</b> pacemaker@oss.clusterlabs.org<br/>
<b>Betreff:</b> [Pacemaker] no nodes on both hosts</div>
<div>
<div style="font-family: Verdana;font-size: 12.0px;">
<div>Hi,</div>
<div> </div>
<div>i use debian 7.</div>
<div> </div>
<div>At first, i use the standard packages of debian, and pacemaker works perfect.</div>
<div> </div>
<div>Now, i compiled my own packages, because i need pacemaker_remote. Since i use my compiled version, pacemaker see no nodes!</div>
<div> </div>
<div>corosync2 lists both hosts:</div>
<div>root@pacemaker1:/var/lib/pacemaker/cib# corosync-cmapctl | grep members<br/>
runtime.totem.pg.mrp.srp.members.181614346.config_version (u64) = 0<br/>
runtime.totem.pg.mrp.srp.members.181614346.ip (str) = r(0) ip(10.211.55.10)<br/>
runtime.totem.pg.mrp.srp.members.181614346.join_count (u32) = 1<br/>
runtime.totem.pg.mrp.srp.members.181614346.status (str) = joined<br/>
runtime.totem.pg.mrp.srp.members.181614347.config_version (u64) = 0<br/>
runtime.totem.pg.mrp.srp.members.181614347.ip (str) = r(0) ip(10.211.55.11)<br/>
runtime.totem.pg.mrp.srp.members.181614347.join_count (u32) = 1<br/>
runtime.totem.pg.mrp.srp.members.181614347.status (str) = joined</div>
<div> </div>
<div>
<div>root@pacemaker1:/var/lib/pacemaker/cib# crm_mon -1<br/>
Last updated: Fri Jan 16 16:49:10 2015<br/>
Last change: Fri Jan 16 16:05:15 2015<br/>
Current DC: NONE<br/>
0 Nodes configured<br/>
0 Resources configured</div>
<div> </div>
<div>uname -n returns pacemaker1 / pacemaker2.</div>
<div> </div>
<div>Logfile is attached.</div>
<div> </div>
<div>corosync.conf:</div>
<div>
<div>totem {<br/>
version: 2</div>
<div> token: 5000</div>
<div> # crypto_cipher and crypto_hash: Used for mutual node authentication.<br/>
# If you choose to enable this, then do remember to create a shared<br/>
# secret with "corosync-keygen".<br/>
# enabling crypto_cipher, requires also enabling of crypto_hash.<br/>
crypto_cipher: none<br/>
crypto_hash: none</div>
<div> # interface: define at least one interface to communicate<br/>
# over. If you define more than one interface stanza, you must<br/>
# also set rrp_mode.<br/>
interface {<br/>
# Rings must be consecutively numbered, starting at 0.<br/>
ringnumber: 0<br/>
# This is normally the *network* address of the<br/>
# interface to bind to. This ensures that you can use<br/>
# identical instances of this configuration file<br/>
# across all your cluster nodes, without having to<br/>
# modify this option.<br/>
bindnetaddr: 10.211.55.10<br/>
# However, if you have multiple physical network<br/>
# interfaces configured for the same subnet, then the<br/>
# network address alone is not sufficient to identify<br/>
# the interface Corosync should bind to. In that case,<br/>
# configure the *host* address of the interface<br/>
# instead:<br/>
# bindnetaddr: 192.168.1.1<br/>
# When selecting a multicast address, consider RFC<br/>
# 2365 (which, among other things, specifies that<br/>
# 239.255.x.x addresses are left to the discretion of<br/>
# the network administrator). Do not reuse multicast<br/>
# addresses across multiple Corosync clusters sharing<br/>
# the same network.<br/>
mcastaddr: 239.255.1.1<br/>
# Corosync uses the port you specify here for UDP<br/>
# messaging, and also the immediately preceding<br/>
# port. Thus if you set this to 5405, Corosync sends<br/>
# messages over UDP ports 5405 and 5404.<br/>
mcastport: 5405<br/>
# Time-to-live for cluster communication packets. The<br/>
# number of hops (routers) that this ring will allow<br/>
# itself to pass. Note that multicast routing must be<br/>
# specifically enabled on most network routers.<br/>
ttl: 1<br/>
}<br/>
}</div>
<div>logging {<br/>
# Log the source file and line where messages are being<br/>
# generated. When in doubt, leave off. Potentially useful for<br/>
# debugging.<br/>
fileline: off<br/>
# Log to standard error. When in doubt, set to no. Useful when<br/>
# running in the foreground (when invoking "corosync -f")<br/>
to_stderr: no<br/>
# Log to a log file. When set to "no", the "logfile" option<br/>
# must not be set.<br/>
to_logfile: yes<br/>
logfile: /var/log/cluster/corosync.log<br/>
# Log to the system log daemon. When in doubt, set to yes.<br/>
to_syslog: no<br/>
# Log debug messages (very verbose). When in doubt, leave off.<br/>
debug: on<br/>
# Log messages with time stamps. When in doubt, set to on<br/>
# (unless you are only logging to syslog, where double<br/>
# timestamps can be annoying).<br/>
timestamp: on<br/>
logger_subsys {<br/>
subsys: QUORUM<br/>
debug: off<br/>
}<br/>
}</div>
<div>quorum {<br/>
# Enable and configure quorum subsystem (default: off)<br/>
# see also corosync.conf.5 and votequorum.5<br/>
#provider: corosync_votequorum<br/>
}</div>
<div> </div>
<div>Thanks!</div>
</div>
</div>
</div>
_______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a> Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a> Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a></div>
</div>
</div>
</div>
</div>
_______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a> Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a> Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a></div>
</div>
</div>
</div>
</div>
_______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a> Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a> Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a></div>
</div>
</div>
</div></div></body></html>