<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Hello Derek<br>
      <br>
      Three things I might recommend given my experience having issues
      similar to yours.<br>
      <br>
      1) Do be sure that every package that you have, depending on your
      Linux distribution (or depending on the OS version), is updated to
      the latest version. <br>
      In my case, I apparently had permission problems with Erlang and a
      segmentation fault. I added the Debian repository<br>
      along with the Squeeze repositories, used the latest version and
      it worked. This only applies to Debian Squeeze (6) and RabbitMQ V
      3.1.5<br>
      <br>
      2) Be sure that you don't have the hosts ports restricted by any
      Firewalling or Wrappers software. Be sure you have no entries<br>
      on /etc/hosts.allow and /etc/hosts.deny and that your endpoint
      (network router/switch) doesn't have any port or network
      restrictions.<br>
      <br>
      3) Test the connectivity and the ports. You can try doing "telnet
      hostname port" to see if you can see the ports from one host to
      the <br>
      other. I would particularly recommend testing this with the Rabbit
      and to simply disconnect.<br>
      <br>
      Let's hope this helps<br>
      <br>
      Regards,<br>
      Allan Baker<br>
      <br>
      El 25/09/2013 10:27 a.m., Derek Wyatt escribi&oacute;:<br>
    </div>
    <blockquote
cite="mid:CAMxG3ZPRpVe81Nc+aewtDcg2tRH6n8cG4xvKwXqzhHK04zsW6Q@mail.gmail.com"
      type="cite">
      <div dir="ltr">This is rabbitmq 3.1.5 - I'm not sure what the
        erlang version is, but the erts version is 5.8.5. &nbsp;I'm a little
        new to the whole erlang thing, so I just picked a component with
        'e' in it :P
        <div>
          <br>
        </div>
        <div>I'm planning to get these machines into the DNS proper to
          see if that helps. &nbsp;It would be pretty weird if it works,
          since everyone else works OK with just /etc/hosts resolution,
          but it's worth a try.</div>
      </div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">On 25 September 2013 11:16, Simon
          MacMullen <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:simon@rabbitmq.com" target="_blank">simon@rabbitmq.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">You may
            (depending on Erlang version) need to make sure that each
            machine can resolve its own hostname too, as well as the
            other one.<br>
            <br>
            Cheers, Simon<br>
            <br>
            On 25/09/13 16:04, Derek Wyatt wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              Damn. That's exactly the setup I have.<br>
              <br>
              <br>
              On 25 September 2013 10:55, Robin Lawrie - HostelBookers<br>
              &lt;<a moz-do-not-send="true"
                href="mailto:Robin.Lawrie@hostelbookers.com"
                target="_blank">Robin.Lawrie@hostelbookers.com</a>
              &lt;mailto:<a moz-do-not-send="true"
                href="mailto:Robin.Lawrie@hostelbookers.com"
                target="_blank">Robin.Lawrie@hostelbookers.com</a>&gt;&gt;<br>
              wrote:<br>
              <br>
              &nbsp; &nbsp; Hi,<br>
              <br>
              &nbsp; &nbsp; In my case, I have a 2 node cluster (called cache1 and
              cache2) and I<br>
              &nbsp; &nbsp; needed to add an entry to the hosts file on both nodes
              to ensure<br>
              &nbsp; &nbsp; each node can resolve the name of the other node
              before clustering<br>
              &nbsp; &nbsp; worked for me.<br>
              <br>
              &nbsp; &nbsp; My hosts file is in /etc and is called hosts<br>
              <br>
              &nbsp; &nbsp; In there I entered the following:<br>
              <br>
              &nbsp; &nbsp; On cache1.lon.hosting, enter the line 192.168.3.1 <a
                moz-do-not-send="true" href="http://Cache2.domain.com"
                target="_blank">Cache2.domain.com</a><br>
              &nbsp; &nbsp; &lt;<a moz-do-not-send="true"
                href="http://Cache2.domain.com" target="_blank">http://Cache2.domain.com</a>&gt;
              Cache2<br>
              <br>
              &nbsp; &nbsp; On cache2.lon.hosting, enter the line 192.168.3.0 <a
                moz-do-not-send="true" href="http://Cache1.domain.com"
                target="_blank">Cache1.domain.com</a><br>
              &nbsp; &nbsp; &lt;<a moz-do-not-send="true"
                href="http://Cache1.domain.com" target="_blank">http://Cache1.domain.com</a>&gt;
              Cache1<br>
              <br>
              &nbsp; &nbsp; Once done, I needed to confirm I could ping each node
              using it&#8217;s<br>
              &nbsp; &nbsp; hostname from the other node. I don&#8217;t care about DNS
              or nslookup<br>
              &nbsp; &nbsp; working/resolving the name.<br>
              <br>
              &nbsp; &nbsp; HTH<br>
              <br>
              &nbsp; &nbsp; Robin<br>
              <br>
              &nbsp; &nbsp; *From:*<a moz-do-not-send="true"
                href="mailto:rabbitmq-discuss-bounces@lists.rabbitmq.com"
                target="_blank">rabbitmq-discuss-bounces@lists.rabbitmq.com</a><br>
              &nbsp; &nbsp; &lt;mailto:<a moz-do-not-send="true"
                href="mailto:rabbitmq-discuss-bounces@lists.rabbitmq.com"
                target="_blank">rabbitmq-discuss-bounces@lists.rabbitmq.com</a>&gt;<br>
              &nbsp; &nbsp; [mailto:<a moz-do-not-send="true"
                href="mailto:rabbitmq-discuss-bounces@lists.rabbitmq.com"
                target="_blank">rabbitmq-discuss-bounces@lists.rabbitmq.com</a><br>
              &nbsp; &nbsp; &lt;mailto:<a moz-do-not-send="true"
                href="mailto:rabbitmq-discuss-bounces@lists.rabbitmq.com"
                target="_blank">rabbitmq-discuss-bounces@lists.rabbitmq.com</a>&gt;]
              *On Behalf Of<br>
              &nbsp; &nbsp; *Derek Wyatt<br>
              &nbsp; &nbsp; *Sent:* 25 September 2013 15:47<br>
              &nbsp; &nbsp; *To:* Discussions about RabbitMQ<br>
              &nbsp; &nbsp; *Subject:* Re: [rabbitmq-discuss] Clustering - just
              can't get it going<br>
              <br>
              &nbsp; &nbsp; Ah, I do have more information though:<br>
              <br>
              &nbsp; &nbsp; DIAGNOSTICS<br>
              <br>
              &nbsp; &nbsp; ===========<br>
              <br>
              &nbsp; &nbsp; nodes in question: ['RMQ1']<br>
              <br>
              &nbsp; &nbsp; hosts, their running nodes and ports:<br>
              <br>
              &nbsp; &nbsp; - unable to connect to epmd on RMQ1: nxdomain
              (non-existing domain)<br>
              <br>
              &nbsp; &nbsp; current node details:<br>
              <br>
              &nbsp; &nbsp; - node name: 'rabbitmqctl1577@RMQ2'<br>
              <br>
              &nbsp; &nbsp; - home dir: /var/lib/rabbitmq<br>
              <br>
              &nbsp; &nbsp; - cookie hash: ohQKEF09peb6bAgNqawvKA==<br>
              <br>
              &nbsp; &nbsp; And just to be clear, the cookie is the same:<br>
              <br>
              &nbsp; &nbsp; *01*:~$ sudo md5sum /var/lib/rabbitmq/.erlang.cookie<br>
              <br>
              &nbsp; &nbsp; a2140a105d3da5e6fa6c080da9ac2f28
              &nbsp;/var/lib/rabbitmq/.erlang.cookie<br>
              <br>
              &nbsp; &nbsp; *02*:~$ sudo md5sum /var/lib/rabbitmq/.erlang.cookie<br>
              <br>
              &nbsp; &nbsp; a2140a105d3da5e6fa6c080da9ac2f28
              &nbsp;/var/lib/rabbitmq/.erlang.cookie<br>
              <br>
              &nbsp; &nbsp; Somehow, telnet to epmd works just fine, but something
              that RMQ is<br>
              &nbsp; &nbsp; doing fails to make that happen. &nbsp;Is there some sort
              of DNS work<br>
              &nbsp; &nbsp; that it's doing, instead of using the hosts files?<br>
              <br>
              &nbsp; &nbsp; i.e. one thing I found is that nslookup fails:<br>
              <br>
              &nbsp; &nbsp; 02:~$ nslookup RMQ1<br>
              <br>
              &nbsp; &nbsp; ;; Got SERVFAIL reply from &lt;ipaddress&gt;, trying
              next server<br>
              <br>
              &nbsp; &nbsp; Server: &nbsp; &nbsp; &nbsp; &lt;ipaddress&gt;<br>
              <br>
              &nbsp; &nbsp; Address: &nbsp;&lt;ipaddress&gt;<br>
              <br>
              &nbsp; &nbsp; ** server can't find RMQ1: SERVFAIL<br>
              <br>
              &nbsp; &nbsp; But if I ping RMQ1 it works fine. /etc/nsswitch.conf
              specifies that<br>
              &nbsp; &nbsp; files should be tried first, before DNS w.r.t. hosts.<br>
              <br>
              &nbsp; &nbsp; So, it looks like RMQ is doing something more rigorous
              to resolve<br>
              &nbsp; &nbsp; the host, and I don't know how to change that. &nbsp;I also
              don't have<br>
              &nbsp; &nbsp; access to the DNS server configuration in order to
              modify it in any way.<br>
              <br>
              &nbsp; &nbsp; On 25 September 2013 09:57, Jason McIntosh &lt;<a
                moz-do-not-send="true" href="mailto:mcintoshj@gmail.com"
                target="_blank">mcintoshj@gmail.com</a><br>
              &nbsp; &nbsp; &lt;mailto:<a moz-do-not-send="true"
                href="mailto:mcintoshj@gmail.com" target="_blank">mcintoshj@gmail.com</a>&gt;&gt;
              wrote:<br>
              <br>
              &nbsp; &nbsp; Check your erlang cookie on both servers to make sure
              it matches I<br>
              &nbsp; &nbsp; think it's in - /var/lib/rabbitmq/ - then you can use
              rabbitmqctl<br>
              &nbsp; &nbsp; from one machine and see if you can connect to another
              to list<br>
              &nbsp; &nbsp; queues. &nbsp;I THINK that's rabbitmqctl -n
              &lt;servernode&gt; list_queues for<br>
              &nbsp; &nbsp; example. &nbsp;If both servers can talk to each other then
              it should be<br>
              &nbsp; &nbsp; rabbitmqctl stop_app, join_cluster, start_app.<br>
              <br>
              &nbsp; &nbsp; Jason<br>
              <br>
              &nbsp; &nbsp; On Wed, Sep 25, 2013 at 8:50 AM, Derek Wyatt &lt;<a
                moz-do-not-send="true"
                href="mailto:derek@derekwyatt.org" target="_blank">derek@derekwyatt.org</a><br>
              &nbsp; &nbsp; &lt;mailto:<a moz-do-not-send="true"
                href="mailto:derek@derekwyatt.org" target="_blank">derek@derekwyatt.org</a>&gt;&gt;
              wrote:<br>
              <br>
              &nbsp; &nbsp; Hi,<br>
              <br>
              &nbsp; &nbsp; I've seen a number of people failing to get clustering
              running and,<br>
              &nbsp; &nbsp; unfortunately, I can't get it going either. &nbsp;Here's
              the summary of<br>
              &nbsp; &nbsp; what I've got:<br>
              <br>
              &nbsp; &nbsp; &nbsp; * Two nodes - RMQ1 and RMQ2<br>
              &nbsp; &nbsp; &nbsp; * I can ping RMQ1 from RMQ2, and vice versa<br>
              &nbsp; &nbsp; &nbsp; * I can telnet from RMQ1 to RMQ2:epmd, and vice
              versa<br>
              &nbsp; &nbsp; &nbsp; * I can telnet from RMQ1 to RMQ2:amqp, and vice
              versa<br>
              &nbsp; &nbsp; &nbsp; * The cookie file is identical, as is clear from the
              startup INFO<br>
              <br>
              &nbsp; &nbsp; My goal is to have RMQ2 join RMQ1 in a cluster.<br>
              <br>
              &nbsp; &nbsp; The servers are started using the init script in
              Ubuntu (i.e.<br>
              &nbsp; &nbsp; service rabbitmq-server start). &nbsp;This is different
              than the script<br>
              &nbsp; &nbsp; at <a moz-do-not-send="true"
                href="http://www.rabbitmq.com/clustering.html"
                target="_blank">http://www.rabbitmq.com/clustering.html</a>,
              which says to start with<br>
              &nbsp; &nbsp; "rabbitmq-server -detached". &nbsp;I've tried that and it
              doesn't seem to<br>
              &nbsp; &nbsp; make any difference so I always use the init script
              instead.<br>
              <br>
              &nbsp; &nbsp; So, the script says to stop the RMQ2 server and then
              join the<br>
              &nbsp; &nbsp; cluster. &nbsp;The following transcript shows how well all
              this goes:<br>
              <br>
              &nbsp; &nbsp; 02:~$ sudo rabbitmqctl stop_app<br>
              <br>
              &nbsp; &nbsp; Stopping node 'rabbit@RMQ2' ...<br>
              <br>
              &nbsp; &nbsp; ...done.<br>
              <br>
              &nbsp; &nbsp; 02:~$ sudo rabbitmqctl join_cluster --ram rabbit@RMQ1<br>
              <br>
              &nbsp; &nbsp; Clustering node 'rabbit@RMQ2' with 'rabbit@RMQ1' ...<br>
              <br>
              &nbsp; &nbsp; Error: {cannot_discover_cluster,"The nodes provided
              are either<br>
              &nbsp; &nbsp; offline or not running"}<br>
              <br>
              &nbsp; &nbsp; However, as I said above, telnetting to the ports
              works just fine:<br>
              <br>
              &nbsp; &nbsp; 02:~$ telnet RMQ1 epmd<br>
              <br>
              &nbsp; &nbsp; Trying &lt;ip address&gt;...<br>
              <br>
              &nbsp; &nbsp; Connected to RMQ1<br>
              <br>
              &nbsp; &nbsp; Escape character is '^]'.<br>
              <br>
              &nbsp; &nbsp; booger!<br>
              <br>
              &nbsp; &nbsp; Connection closed by foreign host.<br>
              <br>
              &nbsp; &nbsp; 02:~$ telnet RMQ1 amqp<br>
              <br>
              &nbsp; &nbsp; Trying &lt;ip address&gt;...<br>
              <br>
              &nbsp; &nbsp; Connected to RMQ1<br>
              <br>
              &nbsp; &nbsp; Escape character is '^]'.<br>
              <br>
              &nbsp; &nbsp; booger!<br>
              <br>
              &nbsp; &nbsp; AMQP Connection closed by foreign host.<br>
              <br>
              &nbsp; &nbsp; I'm stuck for what else to test. &nbsp;Does anyone know how
              to<br>
              &nbsp; &nbsp; troubleshoot this thing further?<br>
              <br>
              &nbsp; &nbsp; Thanks,<br>
              <br>
              &nbsp; &nbsp; Derek<br>
              <br>
              <br>
              &nbsp; &nbsp; _______________________________________________<br>
              &nbsp; &nbsp; rabbitmq-discuss mailing list<br>
              &nbsp; &nbsp; <a moz-do-not-send="true"
                href="mailto:rabbitmq-discuss@lists.rabbitmq.com"
                target="_blank">rabbitmq-discuss@lists.rabbitmq.com</a><br>
              &nbsp; &nbsp; &lt;mailto:<a moz-do-not-send="true"
                href="mailto:rabbitmq-discuss@lists.rabbitmq.com"
                target="_blank">rabbitmq-discuss@lists.rabbitmq.com</a>&gt;<br>
              &nbsp; &nbsp; <a moz-do-not-send="true"
href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss"
                target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
              <br>
              <br>
              <br>
              &nbsp; &nbsp; --<br>
              &nbsp; &nbsp; Jason McIntosh<br>
              &nbsp; &nbsp; <a moz-do-not-send="true"
                href="http://mcintosh.poetshome.com/blog/"
                target="_blank">http://mcintosh.poetshome.com/blog/</a><br>
              &nbsp; &nbsp; <a moz-do-not-send="true" href="tel:573-424-7612"
                value="+15734247612" target="_blank">573-424-7612</a>
              &lt;tel:<a moz-do-not-send="true" href="tel:573-424-7612"
                value="+15734247612" target="_blank">573-424-7612</a>&gt;<br>
              <br>
              <br>
              &nbsp; &nbsp; _______________________________________________<br>
              &nbsp; &nbsp; rabbitmq-discuss mailing list<br>
              &nbsp; &nbsp; <a moz-do-not-send="true"
                href="mailto:rabbitmq-discuss@lists.rabbitmq.com"
                target="_blank">rabbitmq-discuss@lists.rabbitmq.com</a><br>
              &nbsp; &nbsp; &lt;mailto:<a moz-do-not-send="true"
                href="mailto:rabbitmq-discuss@lists.rabbitmq.com"
                target="_blank">rabbitmq-discuss@lists.rabbitmq.com</a>&gt;<br>
              &nbsp; &nbsp; <a moz-do-not-send="true"
href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss"
                target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
              <br>
              &nbsp; &nbsp; ------------------------------------------------------------------------<br>
              <br>
              &nbsp; &nbsp; This email is from Hostelbookers.com Limited.
              Registered office:<br>
              &nbsp; &nbsp; 52-54 High Holborn, London, WC1V 6RL, UK. Registered
              in England<br>
              &nbsp; &nbsp; under Company No.: 2841908. This email and any files
              transmitted<br>
              &nbsp; &nbsp; with it are confidential and may be privileged and are
              intended<br>
              &nbsp; &nbsp; solely for the use of the individual or entity to whom
              they are<br>
              &nbsp; &nbsp; addressed. As email can be subject to operational or
              technical<br>
              &nbsp; &nbsp; difficulties and time delays, communications that are
              subject to<br>
              &nbsp; &nbsp; deadlines should also be sent by post. Any
              unauthorised direct or<br>
              &nbsp; &nbsp; indirect dissemination, distribution or copying of
              this message and<br>
              &nbsp; &nbsp; any attachments is strictly prohibited. If you have
              received the<br>
              &nbsp; &nbsp; email in error, please notify <a
                moz-do-not-send="true"
                href="mailto:postmaster@hostelbookers.com"
                target="_blank">postmaster@hostelbookers.com</a><br>
              &nbsp; &nbsp; &lt;mailto:<a moz-do-not-send="true"
                href="mailto:postmaster@hostelbookers.com"
                target="_blank">postmaster@hostelbookers.com</a>&gt;<br>
              <br>
              &nbsp; &nbsp; ------------------------------------------------------------------------<br>
              <br>
              &nbsp; &nbsp; _______________________________________________<br>
              &nbsp; &nbsp; rabbitmq-discuss mailing list<br>
              &nbsp; &nbsp; <a moz-do-not-send="true"
                href="mailto:rabbitmq-discuss@lists.rabbitmq.com"
                target="_blank">rabbitmq-discuss@lists.rabbitmq.com</a><br>
              &nbsp; &nbsp; &lt;mailto:<a moz-do-not-send="true"
                href="mailto:rabbitmq-discuss@lists.rabbitmq.com"
                target="_blank">rabbitmq-discuss@lists.rabbitmq.com</a>&gt;<br>
              &nbsp; &nbsp; <a moz-do-not-send="true"
href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss"
                target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
              <br>
              <br>
              <br>
              <br>
              _______________________________________________<br>
              rabbitmq-discuss mailing list<br>
              <a moz-do-not-send="true"
                href="mailto:rabbitmq-discuss@lists.rabbitmq.com"
                target="_blank">rabbitmq-discuss@lists.rabbitmq.com</a><br>
              <a moz-do-not-send="true"
href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss"
                target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
              <br>
              <span class="HOEnZb"><font color="#888888">
                </font></span></blockquote>
            <span class="HOEnZb"><font color="#888888">
                <br>
                <br>
                -- <br>
                Simon MacMullen<br>
                RabbitMQ, Pivotal<br>
              </font></span></blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
rabbitmq-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a>
<a class="moz-txt-link-freetext" href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>