cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rajesh Battala <rajesh.batt...@citrix.com>
Subject RE: Make vnc bind to 0.0.0.0 insted of localhost on XenServer 6 with CS 3.0.2
Date Mon, 05 Nov 2012 10:40:26 GMT
Hi France,
For which kind of instances you are getting the error message? [Newly created or old vm's
]
Were you able to view the console for the system VM's?

Thanks
Rajesh Battala

From: France [mailto:mailinglists@isg.si]
Sent: Monday, November 05, 2012 3:36 PM
To: cloudstack-users@incubator.apache.org
Cc: Rajesh Battala
Subject: Re: Make vnc bind to 0.0.0.0 insted of localhost on XenServer 6 with CS 3.0.2

Hi Rajesh,

thank you for your explanation.
What is the proposed solution to get the proxy web console back/working in CloudStack 3.0.2
web GUI?

Currently i'm getting error: " Unable to start console session as connection is refused by
the machine you are accessing"

Regards,
M.
On 5/11/12 10:50 AM, Rajesh Battala wrote:

Hi  France,

We had modified the vnc config on xenserver hosts to listen on localhost instead of 0.0.0.0
because of security reasons.

In your 3.0.2 environment, CS uses https console url provided by the xenserver host to stream
the VNC to the Ajax client.



Thanks

Rajesh Battala





-----Original Message-----

From: France [mailto:mailinglists@isg.si]

Sent: Monday, November 05, 2012 3:11 PM

To: cloudstack-users@incubator.apache.org<mailto:cloudstack-users@incubator.apache.org>

Subject: Make vnc bind to 0.0.0.0 insted of localhost on XenServer 6 with CS 3.0.2



Hi,



i'm using CloudStack 3.0.2 (as per last official release) and XenServer 6.0.2-53456p (xenenterprise).



After installing some of these hotfixes:

[root@x4 ~]# xe patch-list | grep XS6

               name-label ( RO): XS602E002

               name-label ( RO): XS602E005

               name-label ( RO): XS602E006

               name-label ( RO): XS602E003

               name-label ( RO): XS602E001

               name-label ( RO): XS602E008

               name-label ( RO): XS602E009

               name-label ( RO): XS602E004

               name-label ( RO): XS602E007



VNC terminal get's binded to 127.0.0.1 or localhost instead of binding to 0.0.0.0, which in
turn means, that newly created (restarted?) virtual instances can not be accessed with WEB
proxy console, because connection to hipervisor host is refused.

[root@x4 ~]# netstat -apltn | grep vnc

tcp        0      0 127.0.0.1:9504 0.0.0.0:*

LISTEN      11695/vncterm

tcp        0      0 127.0.0.1:9505 0.0.0.0:*

LISTEN      12269/vncterm

tcp        0      0 127.0.0.1:5901 0.0.0.0:*

LISTEN      8128/vncterm

tcp        0      0 0.0.0.0:5902 0.0.0.0:*                   LISTEN

28166/vncterm

tcp        0      0 127.0.0.1:5903 0.0.0.0:*

LISTEN      11251/vncterm

tcp        0      0 127.0.0.1:5904 0.0.0.0:*

LISTEN      11695/vncterm

tcp        0      0 127.0.0.1:5905 0.0.0.0:*

LISTEN      12269/vncterm

tcp        0      0 127.0.0.1:9501 0.0.0.0:*

LISTEN      8128/vncterm

tcp        0      0 0.0.0.0:9502 0.0.0.0:*                   LISTEN

28166/vncterm

tcp        0      0 127.0.0.1:9503 0.0.0.0:*

LISTEN      11251/vncterm



#####

How can i make newly created (restarted?) virtual instances to bind to

0.0.0.0 again?

#####





We've had a lot of other problems after the upgrade(s), most of them

solved bo manually copying files from cloudstack management server to

hipervisors. Like: NFSSR.py to fix storage template problems. This

problem might be related to files:

/opt/xensource/libexec/vncterm-wrapper or qemu-dm-wrapper but i don't

want to screw around with these on production system myself.

Please advise. Thank you.



Regards,

France


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message