<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""></div><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class="">On 09 Mar 2016, at 10:23, Ken Gaillot <<a href="mailto:kgaillot@redhat.com" class="">kgaillot@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">On 03/08/2016 11:38 PM, Сергей Филатов wrote:</span><br style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><blockquote type="cite" style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">ssh -p 3121 compute-1<br class="">ssh_exchange_identification: read: Connection reset by peer<br class=""><br class="">That’s what I get in /var/log/pacemaker.log after restarting pacemaker_remote:<br class="">Mar 09 05:30:27 [28031] <a href="http://compute-1.domain.com" class="">compute-1.domain.com</a> lrmd: info: crm_signal_dispatch: Invoking handler for signal 15: Terminated<br class="">Mar 09 05:30:27 [28031] <a href="http://compute-1.domain.com" class="">compute-1.domain.com</a> lrmd: info: lrmd_shutdown: Terminating with 0 clients<br class="">Mar 09 05:30:27 [28031] <a href="http://compute-1.domain.com" class="">compute-1.domain.com</a> lrmd: info: qb_ipcs_us_withdraw: withdrawing server sockets<br class="">Mar 09 05:30:27 [28031] <a href="http://compute-1.domain.com" class="">compute-1.domain.com</a> lrmd: info: crm_xml_cleanup: Cleaning up memory from libxml2<br class="">Mar 09 05:30:27 [28193] <a href="http://compute-1.domain.com" class="">compute-1.domain.com</a> lrmd: info: crm_log_init: Changed active directory to /var/lib/heartbeat/cores/root<br class="">Mar 09 05:30:27 [28193] <a href="http://compute-1.domain.com" class="">compute-1.domain.com</a> lrmd: info: qb_ipcs_us_publish: server name: lrmd<br class="">Mar 09 05:30:27 [28193] <a href="http://compute-1.domain.com" class="">compute-1.domain.com</a> lrmd: notice: lrmd_init_remote_tls_server: Starting a tls listener on port 3121.<br class="">Mar 09 05:30:28 [28193] <a href="http://compute-1.domain.com" class="">compute-1.domain.com</a> lrmd: notice: bind_and_listen: Listening on address ::<br class="">Mar 09 05:30:28 [28193] <a href="http://compute-1.domain.com" class="">compute-1.domain.com</a> lrmd: info: qb_ipcs_us_publish: server name: cib_ro<br class="">Mar 09 05:30:28 [28193] <a href="http://compute-1.domain.com" class="">compute-1.domain.com</a> lrmd: info: qb_ipcs_us_publish: server name: cib_rw<br class="">Mar 09 05:30:28 [28193] <a href="http://compute-1.domain.com" class="">compute-1.domain.com</a> lrmd: info: qb_ipcs_us_publish: server name: cib_shm<br class="">Mar 09 05:30:28 [28193] <a href="http://compute-1.domain.com" class="">compute-1.domain.com</a> lrmd: info: qb_ipcs_us_publish: server name: attrd<br class="">Mar 09 05:30:28 [28193] <a href="http://compute-1.domain.com" class="">compute-1.domain.com</a> lrmd: info: qb_ipcs_us_publish: server name: stonith-ng<br class="">Mar 09 05:30:28 [28193] <a href="http://compute-1.domain.com" class="">compute-1.domain.com</a> lrmd: info: qb_ipcs_us_publish: server name: crmd<br class="">Mar 09 05:30:28 [28193] <a href="http://compute-1.domain.com" class="">compute-1.domain.com</a> lrmd: info: main: Starting<br class=""></blockquote><br style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">It looks like the cluster is not even trying to connect to the remote</span><br style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">node. pacemaker_remote here is binding only to IPv6, so the cluster will</span><br style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">need to contact it on that address.</span><br style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">What is your ocf:pacemaker:remote resource configuration?</span><br style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Check your cluster node logs for the start action -- if your resource is</span><br style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">named R, the start action will be R_start_0. There will be two nodes of</span><br style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">interest: the node assigned the remote node resource, and the DC.</span><br style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><blockquote type="cite" style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">I got only pacemaker-remote resource-agents pcs installed, so no /etc/default/pacemaker file on remote node<br class="">selinux is disabled and I specifically opened firewall on 2224, 3121 and 21064 tcp and 5405 udp<br class=""><br class=""><blockquote type="cite" class="">On 08 Mar 2016, at 08:51, Ken Gaillot <<a href="mailto:kgaillot@redhat.com" class="">kgaillot@redhat.com</a>> wrote:<br class=""><br class="">On 03/07/2016 09:10 PM, Сергей Филатов wrote:<br class=""><blockquote type="cite" class="">Thanks for an answer. Turned out the problem was not in ipv6.<br class="">Remote node is listening on 3121 port and it’s name is resolving fine.<br class="">Got authkey file at /etc/pacemaker on both remote and cluster nodes.<br class="">What can I check in addition? Is there any walkthrough for ubuntu?<br class=""></blockquote><br class="">Nothing specific to ubuntu, but there's not much distro-specific to it.<br class=""><br class="">If you "ssh -p 3121" to the remote node from a cluster node, what do you<br class="">get?<br class=""><br class="">pacemaker_remote will use the usual log settings for pacemaker (probably<br class="">/var/log/pacemaker.log, probably configured in /etc/default/pacemaker on<br class="">ubuntu). You should see "New remote connection" in the remote node's log<br class="">when the cluster tries to connect, and "LRMD client connection<br class="">established" if it's successful.<br class=""><br class="">As always, check for firewall and SELinux issues.<br class=""><br class=""><blockquote type="cite" class=""><br class=""><blockquote type="cite" class="">On 07 Mar 2016, at 09:40, Ken Gaillot <<a href="mailto:kgaillot@redhat.com" class="">kgaillot@redhat.com</a>> wrote:<br class=""><br class="">On 03/06/2016 07:43 PM, Сергей Филатов wrote:<br class=""><blockquote type="cite" class="">Hi,<br class="">I’m trying to set up pacemaker_remote resource on ubuntu 14.04<br class="">I followed "remote node walkthrough” guide (<a href="http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html-single/Pacemaker_Remote/#idm140473081667280" class="">http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html-single/Pacemaker_Remote/#idm140473081667280</a> <<a href="http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html-single/Pacemaker_Remote/#idm140473081667280" class="">http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html-single/Pacemaker_Remote/#idm140473081667280</a>>)<br class="">After creating ocf:pacemaker:remote resource on cluster node, remote node doesn’t show up as online.<br class="">I guess I need to configure remote agent to listen on ipv4, where can I configure it?<br class="">Or is there any other steps to set up remote node besides the ones mentioned in guide?<br class="">tcp6 0 0 :::3121 :::* LISTEN 21620/pacemaker_rem off (0.00/0/0)<br class=""><br class="">pacemaker and pacemaker_remote are 1.12 version<br class=""></blockquote><br class=""><br class="">pacemaker_remote will try to bind to IPv6 addresses first, and only if<br class="">that fails, will it bind to IPv4. There is no way to configure this<br class="">behavior currently, though it obviously would be nice to have.<br class=""><br class="">The only workarounds I can think of are to make IPv6 connections work<br class="">between the cluster and the remote node, or disable IPv6 on the remote<br class="">node. Using IPv6, there could be an issue if your name resolution<br class="">returns both IPv4 and IPv6 addresses for the remote host; you could<br class="">potentially work around that by adding an IPv6-only name for it, and<br class="">using that as the server option to the remote resource.</blockquote></blockquote></blockquote></blockquote></div></blockquote></div><br class=""></body></html>