karaf-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <barry.barn...@wellsfargo.com>
Subject RE: Cellar clustering issue
Date Fri, 11 Dec 2015 16:26:03 GMT
Ok, I'm able to telnet host1 5701 from host2.  I'm able to telnet host2 5701 from host1.  So
no firewall issue.

I went into the hazelcast.xml file and tried multicast, which also failed.  So I reset that
back to 'false', and set tcp and interface to 'true'.  I tried adding the 5701 port on both
the members and the interface.

<tcp-ip enabled="true">
                <member>host1:5701</member>
                <member>host2:5701</member>
            </tcp-ip>

<interfaces enabled="true">
            <interface>hostIP:5701</interface>
        </interfaces>
 When I tried to issue a cluster:node-list, I received the following:

cluster:node-list
Error executing command: No matching service for optional OSGi service reference: (objectClass=org.apache.karaf.cellar.core.ClusterManager)

I then went back into the hazelcast.xml file and removed the 5701 port from the interfaces:
<interfaces enabled="true">
            <interface>hostIP</interface>
        </interfaces>

I was then able to issue the cluster:node-list command, but once again, it only showed the
local host in the node list, and not the remote instance.  Having no luck here.
We are at Karaf v2.4.3, and Cellar is at v2.3.6.  Is this the issue?

Regards,

Barry 

-----Original Message-----
From: Jean-Baptiste Onofré [mailto:jb@nanthrax.net] 
Sent: Thursday, December 10, 2015 11:06 AM
To: user@karaf.apache.org
Subject: Re: Cellar clustering issue

Honestly, it smells firewalls iptables or SElinux !

Regards
JB

On 12/10/2015 05:03 PM, barry.barnett@wellsfargo.com wrote:
> Ok, I set multicast to true on both, and left tcp and aws as false.  I also had interfaces
set to true.  And this still did not work.
>
> Regards,
>
> Barry
>
>
> -----Original Message-----
> From: Jean-Baptiste Onofré [mailto:jb@nanthrax.net]
> Sent: Thursday, December 10, 2015 11:02 AM
> To: user@karaf.apache.org
> Subject: Re: Cellar clustering issue
>
> Correct.
>
> Regards
> JB
>
> On 12/10/2015 04:57 PM, barry.barnett@wellsfargo.com wrote:
>> Multicast true, but tcp and aws false, right?
>>
>> Regards,
>>
>> Barry
>>
>>
>> -----Original Message-----
>> From: Jean-Baptiste Onofré [mailto:jb@nanthrax.net]
>> Sent: Thursday, December 10, 2015 10:40 AM
>> To: user@karaf.apache.org
>> Subject: Re: Cellar clustering issue
>>
>> Yes, please try multicast.
>>
>> And for sure let me know, but it should work straight forward.
>>
>> Thanks,
>> Regards
>> JB
>>
>> On 12/10/2015 01:49 PM, barry.barnett@wellsfargo.com wrote:
>>> Same group and password.  Should I try multicast instead?  If so, what IP/Port
do I use for that as I can't locate it in the guide if its default, or the localhost IP/Port.
>>>
>>> Regards,
>>>
>>> Barry
>>>
>>>
>>> -----Original Message-----
>>> From: Jean-Baptiste Onofré [mailto:jb@nanthrax.net]
>>> Sent: Tuesday, December 08, 2015 2:23 PM
>>> To: user@karaf.apache.org
>>> Subject: Re: Cellar clustering issue
>>>
>>> Same group name and password on both, right ?
>>>
>>> On 12/08/2015 08:08 PM, barry.barnett@wellsfargo.com wrote:
>>>> This is host2:
>>>>
>>>> <?xml version="1.0" encoding="UTF-8"?> <hazelcast 
>>>> xsi:schemaLocation="http://www.hazelcast.com/schema/config hazelcast-config-2.5.xsd"
>>>>                xmlns="http://www.hazelcast.com/schema/config"
>>>>                xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
>>>>         <group>
>>>>             <name>dev</name>
>>>>             <password>pass</password>
>>>>         </group>
>>>>         <management-center enabled="false">http://localhost:8080/mancenter</management-center>
>>>>         <network>
>>>>             <port auto-increment="true">5701</port>
>>>>             <outbound-ports>
>>>>                 <!--
>>>>                     Allowed port range when connecting to other nodes.
>>>>                     0 or * means use system provided port.
>>>>                 -->
>>>>                 <ports>0</ports>
>>>>             </outbound-ports>
>>>>             <join>
>>>>                 <multicast enabled="false">
>>>>                     <multicast-group>224.2.2.3</multicast-group>
>>>>                     <multicast-port>54327</multicast-port>
>>>>                 </multicast>
>>>>                 <tcp-ip enabled="true">
>>>>                     <member>host1IP</member>
>>>>                     <member>host2IP</member>
>>>>                 </tcp-ip>
>>>>                 <aws enabled="false">
>>>>                     <access-key>my-access-key</access-key>
>>>>                     <secret-key>my-secret-key</secret-key>
>>>>                     <!--optional, default is us-east-1 -->
>>>>                     <region>us-west-1</region>
>>>>                     <!--optional, default is ec2.amazonaws.com. If set,
region shouldn't be set as it will override this property -->
>>>>                     <hostHeader>ec2.amazonaws.com</hostHeader>
>>>>                     <!-- optional, only instances belonging to this group
will be discovered, default will try all running instances -->
>>>>                     <security-group-name>hazelcast-sg</security-group-name>
>>>>                     <tag-key>type</tag-key>
>>>>                     <tag-value>hz-nodes</tag-value>
>>>>
>>>>                 </aws>
>>>>             </join>
>>>>             <interfaces enabled="true">
>>>>                 <interface>host2IP</interface>
>>>>             </interfaces>
>>>>             <ssl enabled="false"/>
>>>>
>>>> Regards,
>>>>
>>>> Barry
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: Jean-Baptiste Onofré [mailto:jb@nanthrax.net]
>>>> Sent: Tuesday, December 08, 2015 1:42 PM
>>>> To: user@karaf.apache.org
>>>> Subject: Re: Cellar clustering issue
>>>>
>>>> Hi Barry,
>>>>
>>>> can you try:
>>>>
>>>> on host1:
>>>>
>>>> <multicast enabled="false"/>
>>>> <tcp-ip enabled="true">
>>>> 	<member>host1</member>
>>>> 	<member>host2</member>
>>>> </tcp-ip>
>>>> ...
>>>> <interfaces enabled="true">
>>>> 	<interface>host1</interface>
>>>> </interfaces>
>>>>
>>>> on host2:
>>>>
>>>>
>>>> <multicast enabled="false"/>
>>>> <tcp-ip enabled="true">
>>>> 	<member>host1</member>
>>>> 	<member>host2</member>
>>>> </tcp-ip>
>>>> ...
>>>> <interfaces enabled="true">
>>>> 	<interface>host2</interface>
>>>> </interfaces>
>>>>
>>>> Thanks,
>>>> Regards
>>>> JB
>>>>
>>>> On 12/08/2015 02:27 PM, barry.barnett@wellsfargo.com wrote:
>>>>> Host2 Server hazelcast.xml tcp stanza:
>>>>>
>>>>> <tcp-ip enabled="true">
>>>>>                      <interface>IP for Host2 here</interface>
>>>>>                  </tcp-ip>
>>>>>
>>>>> Host1 Server hazelcast.xml tcp stanza:
>>>>>
>>>>> <tcp-ip enabled="true">
>>>>>                      <interface>IP for Host1 here</interface>
>>>>>                  </tcp-ip>
>>>>>
>>>>> Regards,
>>>>>
>>>>> Barry
>>>>>
>>>>> -----Original Message-----
>>>>> From: Jean-Baptiste Onofré [mailto:jb@nanthrax.net]
>>>>> Sent: Monday, December 07, 2015 2:47 PM
>>>>> To: user@karaf.apache.org
>>>>> Subject: Re: Cellar clustering issue
>>>>>
>>>>> Can you share the <tcp-ip/> section from both hosts ?
>>>>>
>>>>> Thanks,
>>>>> Regards
>>>>> JB
>>>>>
>>>>> On 12/07/2015 08:39 PM, barry.barnett@wellsfargo.com wrote:
>>>>>> Yes.  Node 1 and Node 2 I don’t have the /member now, but just
the /interface, listed as the hostIP of that particular server.  Should I put member back
in?  That didn't work last time though.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Barry
>>>>>>
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Jean-Baptiste Onofré [mailto:jb@nanthrax.net]
>>>>>> Sent: Monday, December 07, 2015 2:37 PM
>>>>>> To: user@karaf.apache.org
>>>>>> Subject: Re: Cellar clustering issue
>>>>>>
>>>>>> If cluster:node-list doesn't show the host1, it's the issue.
>>>>>>
>>>>>> Did you change hazelcast.xml on both host1 and 2 ?
>>>>>>
>>>>>> Regards
>>>>>> JB
>>>>>>
>>>>>> On 12/07/2015 08:19 PM, barry.barnett@wellsfargo.com wrote:
>>>>>>> I tried the below, and still:
>>>>>>>
>>>>>>> * [host2IP:5701] [host2IP] [ 5701] karaf@root> cluster:group-list
>>>>>>>           Group                  Members
>>>>>>> * [dev                 ] [host2IP:5701* ]
>>>>>>>          [default             ] []
>>>>>>> karaf@root> cluster:group-set dev host1IP:5701 Cluster node
>>>>>>> host1IP:5701 doesn't exist
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Barry
>>>>>>>
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Jean-Baptiste Onofré [mailto:jb@nanthrax.net]
>>>>>>> Sent: Monday, December 07, 2015 2:13 PM
>>>>>>> To: user@karaf.apache.org
>>>>>>> Subject: Re: Cellar clustering issue
>>>>>>>
>>>>>>> Can you try to put only the public interface (no member) ?
>>>>>>>
>>>>>>> Regards
>>>>>>> JB
>>>>>>>
>>>>>>> On 12/07/2015 08:10 PM, barry.barnett@wellsfargo.com wrote:
>>>>>>>> This is what im getting now:
>>>>>>>>
>>>>>>>> karaf@root> cluster:group-list
>>>>>>>>            Group                  Members
>>>>>>>> * [dev                 ] [host1.xxx.com:5701* ]
>>>>>>>>           [default             ] []
>>>>>>>> karaf@root> cluster:group-set dev host2IP:5701 Cluster
node
>>>>>>>> host2IP:5701 doesn't exist
>>>>>>>>
>>>>>>>> My hazelcast shows the following on host2:
>>>>>>>> <multicast enabled="false">
>>>>>>>>                         <multicast-group>224.2.2.3</multicast-group>
>>>>>>>>                         <multicast-port>54327</multicast-port>
>>>>>>>>                     </multicast>
>>>>>>>>                     <tcp-ip enabled="true">
>>>>>>>>                         <interface>host2IP</interface>
>>>>>>>>                         <member>host1IP</member>
>>>>>>>>                     </tcp-ip>
>>>>>>>>
>>>>>>>> Still not working....
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> Barry
>>>>>>>>
>>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Jean-Baptiste Onofré [mailto:jb@nanthrax.net]
>>>>>>>> Sent: Monday, December 07, 2015 2:02 PM
>>>>>>>> To: user@karaf.apache.org
>>>>>>>> Subject: Re: Cellar clustering issue
>>>>>>>>
>>>>>>>> Hi Barry,
>>>>>>>>
>>>>>>>> in your case, you should have:
>>>>>>>>
>>>>>>>> <tcp-ip enabled="true">
>>>>>>>>            <interface>196.168.134.2</interface>
>>>>>>>>            <member>192.168.134.10</member> </tcp-ip>
>>>>>>>>
>>>>>>>> where 192.168.134.2 is the public IP address of node1, and
>>>>>>>> 192.168.134.10 is the IP address of node2 for instance.
>>>>>>>>
>>>>>>>> Regards
>>>>>>>> JB
>>>>>>>>
>>>>>>>> On 12/07/2015 07:54 PM, barry.barnett@wellsfargo.com wrote:
>>>>>>>>> Ok, but do I put:
>>>>>>>>>
>>>>>>>>> <tcp-ip enabled="true">
>>>>>>>>>
>>>>>>>>>                          <interface>127.0.0.1</interface>
>>>>>>>>>
>>>>>>>>>                          <interface>remoteserver1

>>>>>>>>> IP</interface>
>>>>>>>>>
>>>>>>>>> <interface>remoteserver2 IP</interface>….
 etc
>>>>>>>>>
>>>>>>>>>                      </tcp-ip>
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>>
>>>>>>>>> Barry
>>>>>>>>>
>>>>>>>>> *From:*Achim Nierbeck [mailto:bcanhome@googlemail.com]
>>>>>>>>> *Sent:* Monday, December 07, 2015 1:43 PM
>>>>>>>>> *To:* user@karaf.apache.org
>>>>>>>>> *Subject:* Re: Cellar clustering issue
>>>>>>>>>
>>>>>>>>> actually you need to configure every IP on macs for it
to work properly.
>>>>>>>>>
>>>>>>>>> regards, Achim
>>>>>>>>>
>>>>>>>>> 2015-12-07 19:40 GMT+01:00 <barry.barnett@wellsfargo.com
>>>>>>>>> <mailto:barry.barnett@wellsfargo.com>>:
>>>>>>>>>
>>>>>>>>> Change it to multicast?
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>>
>>>>>>>>> Barry
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: Jean-Baptiste Onofré [mailto:jb@nanthrax.net 
>>>>>>>>> <mailto:jb@nanthrax.net>]
>>>>>>>>>
>>>>>>>>> Sent: Monday, December 07, 2015 12:09 PM
>>>>>>>>> To: user@karaf.apache.org <mailto:user@karaf.apache.org>
>>>>>>>>> Subject: Re: Cellar clustering issue
>>>>>>>>>
>>>>>>>>> Hi Barry,
>>>>>>>>>
>>>>>>>>> it's probably because the Cellar hazelcast instances
don't 
>>>>>>>>> show each other (maybe firewall between the nodes, or
so).
>>>>>>>>>
>>>>>>>>> You can change the network discovery mechanism in 
>>>>>>>>> etc/hazelcast.xml of each instance.
>>>>>>>>>
>>>>>>>>> Regards
>>>>>>>>> JB
>>>>>>>>>
>>>>>>>>> On 12/07/2015 05:49 PM, barry.barnett@wellsfargo.com

>>>>>>>>> <mailto:barry.barnett@wellsfargo.com> wrote:
>>>>>>>>>          > I use whatever the default is set to...
 should I change something?
>>>>>>>>> Node list only shows aaa.aaa.aaa on the aaa server. 
And 
>>>>>>>>> bbb.bbb.bbb on the bbb server.  Can't get either to show
the other node in the list.
>>>>>>>>>          >
>>>>>>>>>          > Regards,
>>>>>>>>>          >
>>>>>>>>>          > Barry
>>>>>>>>>          >
>>>>>>>>>          >
>>>>>>>>>          >
>>>>>>>>>          > -----Original Message-----
>>>>>>>>>          > From: Jean-Baptiste Onofré [mailto:jb@nanthrax.net

>>>>>>>>> <mailto:jb@nanthrax.net>]  > Sent: Monday, December
07, 2015
>>>>>>>>> 11:28 AM
>>>>>>>>>> To: user@karaf.apache.org <mailto:user@karaf.apache.org>
 > Subject:
>>>>>>>>> Re: Cellar clustering issue  >  > Hi Barry,  >
 > what do you 
>>>>>>>>> have with cellar:node-list ?
>>>>>>>>>          >
>>>>>>>>>          > Do you use multicast or "static" tcp-ip
in etc/hazelcast.xml ?
>>>>>>>>>          >
>>>>>>>>>          > Thanks,
>>>>>>>>>          > Regards
>>>>>>>>>          > JB
>>>>>>>>>          >
>>>>>>>>>          > On 12/07/2015 04:54 PM, 
>>>>>>>>> barry.barnett@wellsfargo.com <mailto:barry.barnett@wellsfargo.com>
wrote:
>>>>>>>>>          >> Hello,
>>>>>>>>>          >> I am have installed Cellar v2.3.6 in
each of my Karaf instances.
>>>>>>>>>          >> Karaf1 - IP aaa.aaa.aaa, port bbbb
 >> Karaf2 - IP 
>>>>>>>>> bbb.bbb.bbb, port cccc  >> Why is it that when
I issue the 
>>>>>>>>> following on Karaf1, I get 'Cluster  >> node bbb.bbb.bbb
doesn't exit':
>>>>>>>>>          >> Karaf root> cluster:group-set dev
bbb.bbb.bbb:cccc 
>>>>>>>>> I thought it would  >> pick it up right away.
>>>>>>>>>          >> Regards,
>>>>>>>>>          >> Barry
>>>>>>>>>          >
>>>>>>>>>          > --
>>>>>>>>>          > Jean-Baptiste Onofré
>>>>>>>>>          > jbonofre@apache.org <mailto:jbonofre@apache.org>
 > 
>>>>>>>>> http://blog.nanthrax.net  > Talend - http://www.talend.com
 >
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Jean-Baptiste Onofré
>>>>>>>>> jbonofre@apache.org <mailto:jbonofre@apache.org>

>>>>>>>>> http://blog.nanthrax.net Talend - http://www.talend.com
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Apache Member
>>>>>>>>>
>>>>>>>>> Apache Karaf <http://karaf.apache.org/> Committer
& PMC OPS4J 
>>>>>>>>> Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
>>>>>>>>> Committer & Project Lead blog <http://notizblog.nierbeck.de/>
>>>>>>>>>
>>>>>>>>> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
>>>>>>>>>
>>>>>>>>> Software Architect / Project Manager / Scrum Master
>>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Jean-Baptiste Onofré
>>>>>>>> jbonofre@apache.org
>>>>>>>> http://blog.nanthrax.net
>>>>>>>> Talend - http://www.talend.com
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Jean-Baptiste Onofré
>>>>>>> jbonofre@apache.org
>>>>>>> http://blog.nanthrax.net
>>>>>>> Talend - http://www.talend.com
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Jean-Baptiste Onofré
>>>>>> jbonofre@apache.org
>>>>>> http://blog.nanthrax.net
>>>>>> Talend - http://www.talend.com
>>>>>>
>>>>>
>>>>> --
>>>>> Jean-Baptiste Onofré
>>>>> jbonofre@apache.org
>>>>> http://blog.nanthrax.net
>>>>> Talend - http://www.talend.com
>>>>>
>>>>
>>>> --
>>>> Jean-Baptiste Onofré
>>>> jbonofre@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>
>>> --
>>> Jean-Baptiste Onofré
>>> jbonofre@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Mime
View raw message