Ask Your Question
0

console is currently unavailable... cirros-0.3.2-x86_64 --- Instance [closed]

asked 2015-01-09 20:17:50 -0500

Pradipta_OS_M gravatar image

Hi All,

Please suggest me the reason for unable to open the console for cirros OS.. Below is the Console log..

image description

VNC Console failed status...

image description

Console Log:
~~~~~~~~~~~
Jan  9 19:01:22 cirros kern.info kernel: [    4.149595] acpiphp: Slot [29] registered
Jan  9 19:01:22 cirros kern.info kernel: [    4.149788] acpiphp: Slot [30] registered
Jan  9 19:01:22 cirros kern.info kernel: [    4.149977] acpiphp: Slot [31] registered
Jan  9 19:01:22 cirros kern.info kernel: [    4.205320] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
Jan  9 19:01:22 cirros kern.info kernel: [    4.205353] e1000: Copyright (c) 1999-2006 Intel Corporation.
Jan  9 19:01:22 cirros kern.info kernel: [    4.249755] ne2k-pci.c:v1.03 9/22/2003 D. Becker/P. Gortmaker
Jan  9 19:01:22 cirros kern.info kernel: [    4.281953] 8139cp: 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
Jan  9 19:01:23 cirros kern.info kernel: [    4.322328] pcnet32: pcnet32.c:v1.35 21.Apr.2008 tsbogend@alpha.franken.de
Jan  9 19:01:23 cirros kern.info kernel: [    4.362770] ip_tables: (C) 2000-2006 Netfilter Core Team
Jan  9 19:01:35 cirros kern.debug kernel: [   16.456764] eth0: no IPv6 routers present
Jan  9 19:05:09 cirros authpriv.info dropbear[288]: Running in background
############ debug end   ##############
  ____               ____  ____
 / __/ __ ____ ____ / __ \/ __/
/ /__ / // __// __// /_/ /\ \ 
\___//_//_/  /_/   \____/___/ 
   http://cirros-cloud.net


login as 'cirros' user. default password: 'cubswin:)'. use 'sudo' for root.
cirros login:
edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by Pradipta_OS_M
close date 2015-01-10 11:46:25.871231

add a comment

2 answers

Sort by » oldest newest most voted
0

answered 2015-01-10 11:05:50 -0500

Pradipta_OS_M gravatar image

Hi Yatin,

Thank you for your update.. I got the solution.. In my Cloud setup I used all nova packages in a dedicated hosts. I missed to start the "openstack-nova-consoleauth" service.. The issue has been fixed after started the service..

image description

edit flag offensive delete link more
add a comment
1

answered 2015-01-10 05:32:09 -0500

yatin gravatar image

check nova-novncproxy service is running and listning on port 6080:

netstat -tnlp | grep 6080   // At 192.168.2.52

If not running start it:

If it is running then check nova at compute node and controller node is configured properly: At controller node:

[DEFAULT]
...
my_ip = 192.168.2.52
vncserver_listen = 192.168.2.52
vncserver_proxyclient_address = 192.168.2.52

At compute node:

my_ip = <replace with compute_node ip>
vnc_enabled = True
vncserver_listen = 0.0.0.0
vncserver_proxyclient_address = <replace with compute_node ip>
novncproxy_base_url = http://192.168.2.52:6080/vnc_auto.html

If both compute and controller node are same then configure accordingly

edit flag offensive delete link more
add a comment

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

subscribe to rss feed

Stats

Asked: 2015-01-09 20:17:50 -0500

Seen: 1,326 times

Last updated: Jan 10 '15

Related questions

Overcommitting of CPUs on Qemu?

Authentication strategy

nova fails to start server

how does nova decide the VM nic type?

post creation failing

magnum创建cluster失败

Setting cores per vcpu

instance spawn error

Designate API Changes

Cannot access instance