Good point. Check out the Locator log in the working directory created for the Locator process. If there is something weird going on from a port point of view it will be there.
On Sun, Feb 14, 2016 at 1:34 PM, Jim Campbell <[email protected]> wrote: > Do you have a port conflict? > > > > On Sunday, February 14, 2016, Luke Shannon <[email protected]> wrote: > >> This might be easier to figure out if I could see your set up. If you are >> interested email me directly and I could take a look in a short screen >> share. >> >> On Sun, Feb 14, 2016 at 12:22 PM, Luke Shannon <[email protected]> >> wrote: >> >>> Sorry, I should have been more clear. I was referring to the Locator. Is >>> it also a separate machine (ie: not the machine you are working on)? >>> >>> On Sun, Feb 14, 2016 at 11:42 AM, Alan Kash <[email protected]> wrote: >>> >>>> These are two different physical machines. >>>> >>>> 192.168.20.109 - Machine 1 >>>> 192.168.20.100 - Machine 2 >>>> >>>> >>>> >>>> On Sun, Feb 14, 2016 at 11:20 AM, Luke Shannon <[email protected]> >>>> wrote: >>>> >>>>> I think this is happening because you are running and connecting on >>>>> the same machine, if the locator was on a different machine you would use >>>>> that IP. Try connecting to your locator using 127.0.0.1 or updated your >>>>> host file so 192.168.20.109 points to localhost. >>>>> >>>>> On Sun, Feb 14, 2016 at 11:02 AM, Alan Kash <[email protected]> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I am creating a small 2 node distributed prototype, I am getting >>>>>> locator "Connection Refused" error. >>>>>> >>>>>> Source - Build from develop branch - M2.SNAPSHOT >>>>>> >>>>>> Here is the setup : >>>>>> >>>>>> 1. 192.168.20.109 >>>>>> 2. 192.168.20.100 >>>>>> >>>>>> # NODE 1 - Start Locator & Server on - 192.168.20.109 >>>>>> >>>>>> gfsh>start locator --name=l1 >>>>>> gfsh>start server --name=l1s1 >>>>>> >>>>>> gfsh>list members; >>>>>> Name | Id >>>>>> ---- | ------------------------------------------- >>>>>> l1 | 192.168.20.109(l1:948:locator)<ec><v0>:1024 >>>>>> l1s1 | 192.168.20.109(l1s1:1076)<ec><v1>:1025 >>>>>> >>>>>> >>>>>> # NODE 2 - Connect to Locator - 192.168.20.100 >>>>>> >>>>>> gfsh>connect --locator=192.168.20.109[10334] >>>>>> Connecting to Locator at [host=192.168.20.109, port=10334] .. >>>>>> Connecting to Manager at [host=192.168.20.109, port=1099] .. >>>>>> Connection refused to host: 127.0.0.1; nested exception is: >>>>>> java.net.ConnectException: Connection refused >>>>>> >>>>>> I went through the complete documentation there are no examples of >>>>>> distributed setup/storage/queries. >>>>>> >>>>>> What am I missing here? >>>>>> >>>>>> Thanks, >>>>>> Alan >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Luke Shannon | Field Engineering | Pivotal >>>>> >>>>> ------------------------------------------------------------------------- >>>>> Mobile:416-571-9495 >>>>> Join the Toronto Pivotal Usergroup: >>>>> http://www.meetup.com/Toronto-Pivotal-User-Group/ >>>>> >>>> >>>> >>> >>> >>> -- >>> Luke Shannon | Field Engineering | Pivotal >>> >>> ------------------------------------------------------------------------- >>> Mobile:416-571-9495 >>> Join the Toronto Pivotal Usergroup: >>> http://www.meetup.com/Toronto-Pivotal-User-Group/ >>> >> >> >> >> -- >> Luke Shannon | Field Engineering | Pivotal >> ------------------------------------------------------------------------- >> Mobile:416-571-9495 >> Join the Toronto Pivotal Usergroup: >> http://www.meetup.com/Toronto-Pivotal-User-Group/ >> > > > -- > Sincerely, > > Jim Campbell > [email protected] > > -- Luke Shannon | Field Engineering | Pivotal ------------------------------------------------------------------------- Mobile:416-571-9495 Join the Toronto Pivotal Usergroup: http://www.meetup.com/Toronto-Pivotal-User-Group/
