incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Grizzanti <david.grizza...@sungard.com>
Subject Re: Question about SSVM errors/outbound internet connection
Date Fri, 22 Feb 2013 17:22:07 GMT
Thanks all for the tips - looks like I can't ping 8.8.8.8 from within the SSVM and 192.168.56.1
doesn't provide DNS in this case.

In terms of devcloud vs devcloud2, what's the main difference between the two?  Just wondering
if it's worth me switching to devcloud from devcloud2.

Marcus - were the suggestions you made for a particular devcloud or would these work on both?

Thanks

-- 
David Grizzanti
Software Engineer - SunGard Availability Services
401 N. Broad Street, Philadelphia, PA 19108
o: 215-446-1431 - e: david.grizzanti@sungard.com

On Feb 22, 2013, at 1:01 AM, Marcus Sorensen wrote:

> I usually do "apt-get update && apt-get install dnsmasq" on the devcloud.
> The issue is that the ssvm wants to use your internal or safe management
> network for DNS servers. I wonder what your routes show, normally I see
> static routes for the DNS servers to the management net.
> On Feb 21, 2013 6:33 PM, "Dave Cahill" <dcahill@midokura.com> wrote:
> 
>> Hi David,
>> 
>> For DNS, it looks like your SSVM can contact 192.168.56.1, but can't
>> resolve download.cloud.com using that server.
>> 
>> Maybe 192.168.56.1 isn't actually providing DNS services - what do you get
>> if you run "dig @192.168.56.1 download.cloud.com" ? I would have thought
>> it
>> would fall back to 8.8.8.8 next either way though, since that's listed in
>> your resolv.conf, but maybe external connectivity isn't working - can you
>> ping 8.8.8.8 from the SSVM?
>> 
>> Thanks,
>> Dave.
>> 
>> 
>> 
>> On Fri, Feb 22, 2013 at 7:03 AM, David Grizzanti <
>> david.grizzanti@sungard.com> wrote:
>> 
>>> Hi All,
>>> 
>>> I had a question about the SSVM and it's ability to communicate out to
>> the
>>> internet.  I'm currently using the DevCloud2 appliance inside Virtualbox
>>> with the Management Server and database running on my laptop (OS X).
>> This
>>> is with the 4.1 version of the code, pulled from the branch.
>>> 
>>> I've gotten to the point where I've built the source, deployed the
>>> database, and am running the management server all w/o any apparent
>> issues.
>>> System VMs come up without issues and tinyLinux template is registered
>>> with the management server as well.  However, the state of the SSVM is
>> such
>>> that no other templates will download since it's having trouble
>> connecting
>>> to external sites.
>>> 
>>> I was following some of the steps on the wiki here
>>> https://cwiki.apache.org/CLOUDSTACK/ssvm-troubleshooting.html and one of
>>> the troubleshooting steps it mentions is to run
>>> /usr/local/cloud/systemvm/ssvm-check.sh.  This fails on the second step
>>> with the following:
>>> 
>>> root@s-1-VM:~# /usr/local/cloud/systemvm/ssvm-check.sh
>>> ================================================
>>> First DNS server is  192.168.56.1
>>> PING 192.168.56.1 (192.168.56.1): 56 data bytes
>>> 64 bytes from 192.168.56.1: icmp_seq=0 ttl=64 time=2.685 ms
>>> 64 bytes from 192.168.56.1: icmp_seq=1 ttl=64 time=0.413 ms
>>> --- 192.168.56.1 ping statistics ---
>>> 2 packets transmitted, 2 packets received, 0% packet loss
>>> round-trip min/avg/max/stddev = 0.413/1.549/2.685/1.136 ms
>>> Good: Can ping DNS server
>>> ================================================
>>> ERROR: DNS not resolving download.cloud.com
>>> resolv.conf follows
>>> nameserver 192.168.56.1
>>> nameserver 8.8.8.8
>>> nameserver 4.4.4.4
>>> 
>>> Also both cloud.out and systemvm.log in /var/log/cloud seem to give
>> errors
>>> indicating issues with connecting to remote sites as well.  I can connect
>>> back to mgmt server on 8250 so I don't think that is the issue.
>>> 
>>> root@s-1-VM:/var/log/cloud# tail -2 systemvm.log
>>> 2013-02-21 22:01:17,523 INFO  [utils.nio.NioClient] (Agent-Selector:)
>>> Connecting to localhost:8250
>>> 2013-02-21 22:01:17,525 ERROR [utils.nio.NioConnection] (Agent-Selector:)
>>> Unable to connect to remote
>>> 
>>> root@s-1-VM:/var/log/cloud# tail -2 cloud.out
>>> 22:01:17,525 ERROR NioConnection:110 - Unable to connect to remote
>>> 22:01:23,614 ERROR NioConnection:110 - Unable to connect to remote
>>> 
>>> root@s-1-VM:/var/log/cloud# telnet 192.168.56.1 8250
>>> Trying 192.168.56.1...
>>> Connected to 192.168.56.1.
>>> 
>>> Is this a known limitation of the DevCloud setup or is there maybe
>>> something else wrong with my setup?
>>> 
>>> Thanks,
>>> 
>>> --
>>> David Grizzanti
>>> Software Engineer - SunGard Availability Services
>>> 401 N. Broad Street, Philadelphia, PA 19108
>>> o: 215-446-1431 - e: david.grizzanti@sungard.com
>>> 
>>> 
>> 


Mime
View raw message