laxy S®III
Original message
From: Ana Paula de Sousa
Date:04/17/2014 6:07 PM (GMT-05:00)
To: users@cloudstack.apache.org
Subject: Re: Unable to ping System VMs
The result of "route -n" is:
http://pastebin.com/dUkueCCF
2014-04-17 19:02 GMT-03:00 Ana Paula de Sousa :
>
I know that you cannot login, however that is at least a good sign.
I had a problem that the OS was taking too long to boot, and that was the
problem to lost pings.
On Thu, Apr 17, 2014 at 7:12 PM, Ana Paula de Sousa wrote:
> Hi Rafael,
>
> The problem is that if I try to access through console
Hi Rafael,
The problem is that if I try to access through console any of the system
vms I get a message asking me the systemvm login and the password, so I
can't actually know if the OS is up or running. All I can know is that
they're up.
2014-04-17 19:07 GMT-03:00 Ana Paula de Sousa :
> The re
The result of "route -n" is:
http://pastebin.com/dUkueCCF
2014-04-17 19:02 GMT-03:00 Ana Paula de Sousa :
> Hi Rafael,
>
> I tried to connect into the console but it asks me a login and password
> which I don't have. I tried the default password I used in the installation
> but I didn't succee
to my knowledge they do not have password.
Well, if connecting into the console worked and the OS is up and running,
the script must have ran and the IP should have been set up.
What hypervisor are you using?
On Thu, Apr 17, 2014 at 7:02 PM, Ana Paula de Sousa wrote:
> Hi Rafael,
>
> I tried to
Hi Rafael,
I tried to connect into the console but it asks me a login and password
which I don't have. I tried the default password I used in the installation
but I didn't succeeded.
2014-04-17 18:59 GMT-03:00 Ana Paula de Sousa :
> Hello,
>
> I tried ssh to both VMs through the hypervisor but
Hello,
I tried ssh to both VMs through the hypervisor but I just can't. It keeps
giving me the message "ssh: connect to host 169.254.0.** port 3922: No
route to host". I can't access the VMs in any way.
2014-04-17 18:54 GMT-03:00 Rafael Weingartner :
> could you try to connect into the VMs cons
could you try to connect into the VMs console? and check if the OS booted
properly.
On Thu, Apr 17, 2014 at 6:49 PM, Ana Paula de Sousa wrote:
> Hi,
>
> The output of "iptables-save" is:
>
> http://pastebin.com/fhA8UdSm
>
> When I typed "ebtables-save" I got the message "bash: ebtables-save:
> c
Hi,
The output of "iptables-save" is:
http://pastebin.com/fhA8UdSm
When I typed "ebtables-save" I got the message "bash: ebtables-save:
comando não encontrado", but I verified if I had ebtables installed and I
have.
Hi,
The two are not strictly related, you should be able to connect to the VMs
(link) local IP regardless of external connectivity. I have done this
multiple times and it's common for troubleshooting these kind of issues.
Can I check you are running the SSH command on your hypervisor?
In the mea
On 17.04.2014 22:30, Ana Paula de Sousa wrote:
Hello,
As I can't ping to the System VMs I also can't ssh to them. When I try
this
troubleshooting I receive the message:
"ssh: connect to host 169.254.0.** port 3922: No route to host"
Can you send the output of "iptables-save" and "ebtables-s
Hello,
As I can't ping to the System VMs I also can't ssh to them. When I try this
troubleshooting I receive the message:
"ssh: connect to host 169.254.0.** port 3922: No route to host"
2014-04-17 17:29 GMT-03:00 Marty Sweet :
> Hi,
>
> Have you tried pinging the Console Proxy from the SSVM?
>
Hi,
Have you tried pinging the Console Proxy from the SSVM?
It is possible to login to these VMs using the following guidance.
http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Admin_Guide/accessing-system-vms.html
Sorry about the old link, couldn't find this in the new docume
13 matches
Mail list logo
