Home Forums Hortonworks Sandbox Connecting to Sanbox Problem

Tagged: 

This topic contains 3 replies, has 2 voices, and was last updated by  Michael Peterson 1 year, 1 month ago.

  • Creator
    Topic
  • #34347

    I have a downloaded a 1.3 sandbox VM for vmware.It didn’t open up in vmware workstation and since I didn’t have any server,I used the Open Virtualization Format Tool,to convert it to a .vmx virtual machine.
    It runs successfuly.but when its is starting services.It shows an error:
    INFO ipc.Client: Retrying connect to server: sandbox/192.168.159.128:8020. Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=50, sleepTime=1 SECONDS)
    this error happened up to 4 times and then didn’t show up.

    After it is ready to use.It shows an ip address and says:
    To initiate your Hortonworks Sandbox session,please open a browser and enter this address in the browser’s address field:

    http://192.168.159.129/

    The ip address of my physical computer is in subnet 192.168.1.0.
    and every where is said: “just enter the ip address ,shown by sandbox in browser to enter to webGUI”.
    but It doesn’t work!(since they are in different subnets!)
    what should I do?
    does it really work? :D

    tnx

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.

  • Author
    Replies
  • #34519

    I can’t count the number of times I’ve done something similar and it’s driven me nuts for days! Glad you found it and it was an easy fix.

    Collapse
    #34516

    hi Michael!
    You’re right! the problem was with the network adapters!
    I had disabled the network adapter of vmware(VMnet 8) for a while,but I had forgot to enable it again.
    I enabled it,and then It worked fine ;-)

    Collapse
    #34386

    I believe that “INFO ipc.Client:” warning is perfectly normal. It looks like it’s part of the normal startup process testing a connection as a service is starting up, thus the 50 retries. I might be a little off on the reason, but I get the exact same message (usually 5-6 times) and my sandbox works fine.

    For me, my IP subnet is 192.168.117.0 and my sandbox is http://192.168.253.128 This works fine for me though, despite being on different subnets. I’m using VMWare and it looks like it creates 2 virtual network adapters. If I start command prompt and do “IPCONFIG /all” there is a VMnet1 and VMnet8.

    Maybe start by seeing if these virtual adapters were created on your physical machine. Without a virtual adapter, I can’t imagine how it would create a network connection to begin with. If those are there it may give you more insight into whats going on. My VMnet8 lists an IP address of 192.168.253.1 so if I knew my VM box was somewhere in the 253 subnet, I could use an IP tool or make a quick script to ping all 255 IP addresses there and output the results. If one of them pings good you’ve found it.

    Another option is, once you log into the sandbox, run “ifconfig -a” which should tell you what network adapters are running (linux ipconfig /all equivalent). This should give you the ip address of your box on the second line, right after “inet addr:”. So you can double check that what the main sandbox screen is telling you is correct.

    Collapse
Viewing 3 replies - 1 through 3 (of 3 total)