cloudstack-users-cn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jijun <jiju...@gmail.com>
Subject Re: 回复: Re: Re: help:通过控制台访问VM失败
Date Mon, 05 Aug 2013 04:27:45 GMT
hello,发现你的问题是xenserver6.0的一个bug,你可以升级到 6.1,或者安装
hotfix。
bug描述:xapi session leaks.
参考:
http://support.citrix.com/article/CTX135636
安装hotfix。


On 08/05/2013 11:53 AM, sunko2014 wrote:
> thank you,在CPVM下检查如下:
> 1.ping 网关   ping管理网络(172.16.101.1) OK,ping public(192.168.45.1)ok
> 2.ping management server ping管理IP(172.168.101.1) ok,ping public
> ip(192.168.45.248)ok
> 3.telnet management server 8250 ok
> 4.ip route 查看路由 ok
> 5.检查/var/log/cloud/cloud.out日志。确认java已经启动。ok,且ps能看到java进程:
> root      1784  0.6  2.7 958332 27968 ?        Sl   03:38   0:04 java
> -Djavax.net.ssl.trustStore=./certs/realhostip.keystore -mx805m -cp
> ./:./conf:apache-log4j-extras-1.1.jar:axis-1.4.jar:axis-jaxrpc-1.4.jar:cglib-nodep-2.2.2.jar:cloud-agent.jar:cloud-api.jar:cloud-console-proxy.jar:cloud-core.jar:cloud-utils.jar:cloud-vmware-base.jar:cloud-vmware.jar:commons-codec-1.6.jar:commons-collections-3.2.1.jar:commons-discovery-0.5.jar:commons-httpclient-3.1.jar:commons-logging-1.1.1.jar:commons-pool-1.6.jar:ejb-api-3.0.jar:gson-1.7.1.jar:log4j-1.2.16.jar:log4j-over-slf4j-1.6.1.jar:vmware-apputils.jar:vmware-vim.jar:ws-commons-util-1.0.2.jar:wsdl4j-1.6.2.jar:xmlrpc-client-3.1.3.jar:xmlrpc-common-3.1.3.jar
> com.cloud.agent.AgentShell root=LABEL console=tty0 xencons=ttyS0,115200
> console=hvc0 console=hvc0 template=domP type=consoleproxy
> host=192.168.45.248 port=8250 name=v-2-VM premium=true zone=1 pod=1
> guid=Proxy.2 proxy_vm=2 disable_rp_filter=true eth2ip=192.168.45.151
> eth2mask=255.255.255.0 gateway=192.168.45.1 eth0ip=169.254.2.10
> eth0mask=255.255.0.0 eth1ip=172.16.101.2 eth1mask=255.255.255.0 mgmtcidr=
> 192.168.45.0/24 localgw=172.16.101.1 internaldns1=192.168.13.31
> dns1=192.168.13.31
>
>
> 2013/8/5 Jijun <jijunlx@gmail.com>
>
>> 看了下你8月2号的邮件,console proxy vm无法连接到管理节点的8250端口。
>> 进CPVM检查以下选项:
>> 1.ping 网关
>> 2.ping management server
>> 3.telnet management server 8250
>> 4.ip route 查看路由
>> 5.检查/var/log/cloud/cloud.out日志。确认java已经启动。
>>
>>
>>
>>
>>
>> On 08/05/2013 11:10 AM, sunko2014 wrote:
>>> sorry,我在公司,无法登陆QQ,能否指点下check事项,或者关于view
console的资料,thanks
>>>
>>>
>>> 2013/8/5 Jijun <jijunlx@gmail.com>
>>>
>>>> 这个问题,你加qq群,找个人给你远程看下就解决了。中文邮件列表就这个好处。
>>>> 群:236581725
>>>>
>>>> On 08/05/2013 10:57 AM, sunko2014 wrote:
>>>>> ok。
>>>>> 通过管理节点的public IP访问UI:http://192.168.45.248:8080/client/#
>>>>> chrome提示错误:请求超时,IE6提示:Internet Explorer 无法显示该网页
>>>>> 通过管理节点的管理网络访问:http://172.16.101.1:8080/client/#<
>>>> http://192.168.45.248:8080/client/#>
>>>>> firefox提示:The connection has timed out The server at
>>>>> 192-168-45-151.realhostip.com is taking too long to respond.
>>>>>
>>>>>
>>>>> 2013/8/5 tanthalas <tanthalas510@hotmail.com>
>>>>>
>>>>>> 你打开console,浏览器给你的报错信息是什么,你再提供一下,不能截图,就复制信息过来就好。
>>>>>> CPVM的作用其实就是能提供给用户,在浏览器上也能管理VM的方式,比如用ISO安装的时候。
>>>>>> 另外就是在公有云的时候,通过SSL加密的方式访问,保护用户的数据安全。
>>>>>>
>>>>>> 2013-08-05
>>>>>> 刘宇超  Richard Liu
>>>>>>
>>>>>>
>>>>>> 发件人: WXR
>>>>>> 发送时间: 2013-08-05 10:35:57
>>>>>> 收件人: users-cn
>>>>>> 抄送:
>>>>>> 主题: 回复: Re: Re: help:通过控制台访问VM失败
>>>>>>
>>>>>> 同求,我这里是想要知道cloudstack通过控制台登录虚拟机的方法,然后直接把链接提供给用户访问,不通过cloudstack。
>>>>>> ------------------ 原始邮件 ------------------
>>>>>> 发件人: "sunko2014"<sunko2014@gmail.com>;
>>>>>> 发送时间: 2013年8月5日(星期一) 上午10:33
>>>>>> 收件人: "users-cn"<users-cn@cloudstack.apache.org>;
>>>>>> 主题: Re: Re: Re: help:通过控制台访问VM失败
>>>>>> 是否有介绍CloudStack的view console业务流程或者原理的,我想通过log和check配置的方式,一步一步找到问题点
>>>>>> 之前玩openstack的时候,有很多关于这方面的bolg,CloudStack感觉要少很多,也可能是我没有找到,请指教下
>>>>>> On Mon, Aug 5, 2013 at 9:16 AM, tanthalas <tanthalas510@hotmail.com>
>>>>>> wrote:
>>>>>>> 你试试拿管理节点的public ip去打开UI,访问console
>>>>>>>
>>>>>>> 2013-08-05
>>>>>>> 刘宇超  Richard Liu
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 发件人: sunko2014
>>>>>>> 发送时间: 2013-08-02 18:00:09
>>>>>>> 收件人: users-cn
>>>>>>> 抄送:
>>>>>>> 主题: Re: Re: help:通过控制台访问VM失败
>>>>>>>
>>>>>>> 尝试的是高级部署,我的部署方案是:
>>>>>>>
>>>>>>>
>>  1、管理和存储走一个交换机网络(172.16.100.x),Public和Guest走一个交换机网络,Pulic是公司内网(192.168.45.x),guest是自定义网络(10.1.1.x)
>>>>>>>            2、1台主机跑Manage
>>>>>>>
>>>>>>>
>> Server,网卡接管理存储网络,1台主机跑XENServer,2张网卡,1张接管理存储网络,1张接Public&Guest网络,1台主机跑NFS(提供Secondary
>>>>>>> Storage),接网络存储网络
>>>>>>> 浏览器访问console我是通过管理网络(172.168.100.x)访问的,且添加了本地解析域名
>>>> X-X-X-X.realhostip.com<
>>>>>>> http://x-x-x-x.realhostip.com/>
>>>>>>> 我的guest VLAN是随便指定的一个访问200-300,public和manage都没有指定VLAN,我的交换机没有VLAN功能。
>>>>>>> On Fri, Aug 2, 2013 at 3:39 PM, tanthalas <tanthalas510@hotmail.com>
>>>>>>> wrote:
>>>>>>>> 还有些东西不是很清楚,你再排查一下
>>>>>>>> 浏览器上用管理节点的外网地址访问的console还是内网?
>>>>>>>> 能否解析console想要打开的域名X-X-X-X.realhostip.com
>>>>>>>> guest/public/manage vlan是怎么设定的的,交换机又是怎么设定的?
>>>>>>>>
>>>>>>>> 2013-08-02
>>>>>>>> 刘宇超  Richard Liu
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> 发件人: sunko2014
>>>>>>>> 发送时间: 2013-08-02 14:24:03
>>>>>>>> 收件人: users-cn
>>>>>>>> 抄送:
>>>>>>>> 主题: Re: help:通过控制台访问VM失败
>>>>>>>>
>>>>>>>> hello:
>>>>>>>>
>>>>>>>>
>>  在host的xensource.log中,有一些异常的log,但是我不太会分析,贴出来,请大侠指教,log都是tail出来的,应该能直接反映错误情形:
>>>>>>>> [20130802T06:17:14.108Z|debug|xenserver01|110080
>>>>>>> inet-RPC|host.call_plugin
>>>>>>>> R:44a2bf2503e5|audit] Host.call_plugin host =
>>>>>>>> '8be3cea2-8fae-49a8-b482-9b26e7e0303e (xenserver01)'; plugin
=
>> 'echo';
>>>>>>> fn =
>>>>>>>> 'main'; args = [  ]
>>>>>>>> [20130802T06:17:14.273Z|debug|xenserver01|110080
>>>>>>> inet-RPC|host.call_plugin
>>>>>>>> R:7e1eaa7080eb|audit] Host.call_plugin host =
>>>>>>>> '8be3cea2-8fae-49a8-b482-9b26e7e0303e (xenserver01)'; plugin
=
>>>> 'vmops';
>>>>>>> fn
>>>>>>>> = 'getvncport'; args = [ domID: 7; hvm: false; version: 6.0.0
]
>>>>>>>> [20130802T06:17:24.548Z|debug|xenserver01|110080
>>>>>> inet-RPC||http_critical]
>>>>>>>> Connection terminated
>>>>>>>> [20130802T06:17:37.529Z|debug|xenserver01|110083
>>>>>>> inet-RPC|host.call_plugin
>>>>>>>> R:b4fa965ed255|audit] Host.call_plugin host =
>>>>>>>> '8be3cea2-8fae-49a8-b482-9b26e7e0303e (xenserver01)'; plugin
=
>> 'echo';
>>>>>>> fn =
>>>>>>>> 'main'; args = [  ]
>>>>>>>> [20130802T06:17:37.671Z|debug|xenserver01|110083
>>>>>>> inet-RPC|host.call_plugin
>>>>>>>> R:97ee28cb30b7|audit] Host.call_plugin host =
>>>>>>>> '8be3cea2-8fae-49a8-b482-9b26e7e0303e (xenserver01)'; plugin
=
>>>> 'vmops';
>>>>>>> fn
>>>>>>>> = 'gethostvmstats'; args = [ startTime: 1375423126; interval:
60;
>>>>>>>> consolidationFunction: AVERAGE; collectHostStats: true ]
>>>>>>>> [20130802T06:17:38.821Z|debug|xenserver01|110083
>>>>>>> inet-RPC|host.call_plugin
>>>>>>>> R:2be88dbb76b5|audit] Host.call_plugin host =
>>>>>>>> '8be3cea2-8fae-49a8-b482-9b26e7e0303e (xenserver01)'; plugin
=
>> 'echo';
>>>>>>> fn =
>>>>>>>> 'main'; args = [  ]
>>>>>>>> [20130802T06:17:38.978Z|debug|xenserver01|110083
>>>>>>> inet-RPC|host.call_plugin
>>>>>>>> R:b2fd88645012|audit] Host.call_plugin host =
>>>>>>>> '8be3cea2-8fae-49a8-b482-9b26e7e0303e (xenserver01)'; plugin
=
>>>> 'vmops';
>>>>>>> fn
>>>>>>>> = 'gethostvmstats'; args = [ startTime: 1375423127; interval:
60;
>>>>>>>> consolidationFunction: AVERAGE; collectHostStats: false ]
>>>>>>>> [20130802T06:17:43.686Z|debug|xenserver01|110083
>>>>>>> inet-RPC|host.call_plugin
>>>>>>>> R:7a4a1a7a1fd2|audit] Host.call_plugin host =
>>>>>>>> '8be3cea2-8fae-49a8-b482-9b26e7e0303e (xenserver01)'; plugin
=
>> 'echo';
>>>>>>> fn =
>>>>>>>> 'main'; args = [  ]
>>>>>>>> [20130802T06:17:43.824Z|debug|xenserver01|110083 inet-RPC|SR.scan
>>>>>>>> R:c9f359be2ed5|audit] SR.scan: SR =
>>>>>> 'c296108a-f6a1-c2c5-d1af-47954009e595
>>>>>>>> (c296108a-f6a1-c2c5-d1af-47954009e595)'
>>>>>>>> [20130802T06:17:43.825Z|debug|xenserver01|110083 inet-RPC|SR.scan
>>>>>>>> R:c9f359be2ed5|xapi] Marking SR for SR.scan
>>>>>>>> (task=OpaqueRef:c9f359be-2ed5-f093-f773-1607e299bafc)
>>>>>>>> [20130802T06:17:43.828Z|debug|xenserver01|110083 inet-RPC|SR.scan
>>>>>>>> R:c9f359be2ed5|sm] SM ext sr_scan
>>>>>>>> sr=OpaqueRef:f2e01272-b702-3184-f414-079f0378d780
>>>>>>>> [20130802T06:17:43.832Z| info|xenserver01|110083 inet-RPC|sm_exec
>>>>>>>> D:771114be114c|xapi] Session.create
>>>>>>>> trackid=e0e1ea2bdbab599d134c73f1144ebd47 pool=false uname=
>>>>>>>> is_local_superuser=true auth_user_sid=
>>>>>>>> parent=trackid=9834f5af41c964e225f24279aefe4e49
>>>>>>>> [20130802T06:17:43.833Z|debug|xenserver01|110083 inet-RPC|sm_exec
>>>>>>>> D:771114be114c|xapi] Attempting to open /var/xapi/xapi
>>>>>>>> [20130802T06:17:43.836Z|debug|xenserver01|110086
>>>>>>> unix-RPC||dummytaskhelper]
>>>>>>>> task dispatch:session.get_uuid D:c000c3fb5d6d created by
task
>>>>>>>> D:771114be114c
>>>>>>>> [20130802T06:17:44.000Z|debug|xenserver01|110087
>>>>>>> unix-RPC||dummytaskhelper]
>>>>>>>> task dispatch:host.get_other_config D:2f1b2f203332 created
by task
>>>>>>>> R:c9f359be2ed5
>>>>>>>> [20130802T06:17:44.151Z|debug|xenserver01|110088
>>>>>>> unix-RPC||dummytaskhelper]
>>>>>>>> task dispatch:SR.get_by_uuid D:e9e9c9a9a6b3 created by task
>>>>>>> R:c9f359be2ed5
>>>>>>>> [20130802T06:17:44.154Z| info|xenserver01|110089
>>>>>>>> unix-RPC|session.login_with_password D:0d015bacc72f|xapi]
>>>>>> Session.create
>>>>>>>> trackid=ee2b04c7d293cfba87dd34a8c1cae443 pool=false uname=root
>>>>>>>> is_local_superuser=true auth_user_sid=
>>>>>>>> parent=trackid=9834f5af41c964e225f24279aefe4e49
>>>>>>>> [20130802T06:17:44.156Z|debug|xenserver01|110089
>>>>>>>> unix-RPC|session.login_with_password D:0d015bacc72f|xapi]
Attempting
>>>> to
>>>>>>>> open /var/xapi/xapi
>>>>>>>> [20130802T06:17:44.160Z|debug|xenserver01|110090
>>>>>>> unix-RPC||dummytaskhelper]
>>>>>>>> task dispatch:session.get_uuid D:bf607dd8e2d9 created by
task
>>>>>>>> D:0d015bacc72f
>>>>>>>> [20130802T06:17:44.162Z|debug|xenserver01|110091
>>>>>>> unix-RPC||dummytaskhelper]
>>>>>>>> task dispatch:SR.set_virtual_allocation D:eef45d3c3f67 created
by
>> task
>>>>>>>> R:c9f359be2ed5
>>>>>>>> [20130802T06:17:44.175Z|debug|xenserver01|110093
>>>>>>> unix-RPC||dummytaskhelper]
>>>>>>>> task dispatch:SR.set_physical_size D:0afe660f638b created
by task
>>>>>>>> R:c9f359be2ed5
>>>>>>>> [20130802T06:17:44.189Z|debug|xenserver01|110095
>>>>>>> unix-RPC||dummytaskhelper]
>>>>>>>> task dispatch:SR.set_physical_utilisation D:7f5aa0a77fcf
created by
>>>>>> task
>>>>>>>> R:c9f359be2ed5
>>>>>>>> [20130802T06:17:44.199Z|debug|xenserver01|110097
>>>>>>> unix-RPC||dummytaskhelper]
>>>>>>>> task dispatch:SR.get_by_uuid D:988be0727d0e created by task
>>>>>>> R:c9f359be2ed5
>>>>>>>> [20130802T06:17:44.210Z|debug|xenserver01|110099
>>>>>>> unix-RPC||dummytaskhelper]
>>>>>>>> task dispatch:VDI.get_all_records_where D:c10fa84b19c2 created
by
>> task
>>>>>>>> R:c9f359be2ed5
>>>>>>>> [20130802T06:17:44.265Z| info|xenserver01|110083 inet-RPC|sm_exec
>>>>>>>> D:771114be114c|xapi] Session.destroy
>>>>>>>> trackid=e0e1ea2bdbab599d134c73f1144ebd47
>>>>>>>> [20130802T06:17:44.269Z|debug|xenserver01|110083 inet-RPC|SR.scan
>>>>>>>> R:c9f359be2ed5|xapi] Unmarking SR after SR.scan
>>>>>>>> (task=OpaqueRef:c9f359be-2ed5-f093-f773-1607e299bafc)
>>>>>>>> [20130802T06:17:49.645Z|debug|xenserver01|18 db_gc|DB GC
>>>>>>>> D:6c04debde0ec|db_gc] Number of disposable sessions in database
>>>>>> (401/401)
>>>>>>>> exceeds limit (400): will delete the oldest
>>>>>>>> [20130802T06:17:49.645Z|debug|xenserver01|18 db_gc|DB GC
>>>>>>>> D:6c04debde0ec|db_gc] Session.destroy
>>>>>>>> _ref=OpaqueRef:f983ae3f-cf7f-578a-f7e1-4c05acd0faa1
>>>>>>>> uuid=ba0c8578-6739-781c-18b2-b8ef69fbb92d
>>>>>>>> trackid=e92b21bebc07e26201fc9234170d9df6 (last active
>>>>>>> 20130802T00:02:01Z):
>>>>>>>> Timed out session because max number of sessions was exceeded
>>>>>>>> [20130802T06:17:49.646Z| info|xenserver01|18 db_gc|DB GC
>>>>>>>> D:6c04debde0ec|xapi] Session.destroy
>>>>>>>> trackid=e92b21bebc07e26201fc9234170d9df6
>>>>>>>> [20130802T06:17:52.520Z|debug|xenserver01|110083
>>>>>> inet-RPC||http_critical]
>>>>>>>> Connection terminated
>>>>>>>> On Fri, Aug 2, 2013 at 2:15 PM, sunko2014 <sunko2014@gmail.com>
>>>> wrote:
>>>>>>>>> ok,找了一下,把里面的两个log都贴出来:
>>>>>>>>> systmvm.log:
>>>>>>>>> 2013-08-02 06:02:58,529 DEBUG [cloud.agent.Agent] (UgentTask-5:)
>>>>>>> Sending
>>>>>>>>> ping: Seq 3-2596:  { Cmd , MgmtId: -1, via: 3, Ver: v1,
Flags: 11,
>>>>>>>>> [{"PingCommand":{"hostType":"ConsoleProxy","hostId":3,"wait":0}}]
}
>>>>>>>>> 2013-08-02 06:02:58,574 DEBUG [cloud.agent.Agent]
>> (Agent-Handler-4:)
>>>>>>>>> Received response: Seq 3-2596:  { Ans: , MgmtId: 260071274268429,
>>>>>> via:
>>>>>>> 3,
>>>>>>>>> Ver: v1, Flags: 100010,
>>>>>>>>>
>> [{"PingAnswer":{"_command":{"hostType":"ConsoleProxy","hostId":3,"wait":0},"result":true,"wait":0}}]
>>>>>>>>> }
>>>>>>>>> 2013-08-02 06:03:58,529 DEBUG [cloud.agent.Agent] (UgentTask-5:)
>>>>>>> Sending
>>>>>>>>> ping: Seq 3-2597:  { Cmd , MgmtId: -1, via: 3, Ver: v1,
Flags: 11,
>>>>>>>>> [{"PingCommand":{"hostType":"ConsoleProxy","hostId":3,"wait":0}}]
}
>>>>>>>>> 2013-08-02 06:03:58,575 DEBUG [cloud.agent.Agent]
>> (Agent-Handler-5:)
>>>>>>>>> Received response: Seq 3-2597:  { Ans: , MgmtId: 260071274268429,
>>>>>> via:
>>>>>>> 3,
>>>>>>>>> Ver: v1, Flags: 100010,
>>>>>>>>>
>> [{"PingAnswer":{"_command":{"hostType":"ConsoleProxy","hostId":3,"wait":0},"result":true,"wait":0}}]
>>>>>>>>> }
>>>>>>>>> 2013-08-02 06:04:58,530 DEBUG [cloud.agent.Agent] (UgentTask-5:)
>>>>>>> Sending
>>>>>>>>> ping: Seq 3-2598:  { Cmd , MgmtId: -1, via: 3, Ver: v1,
Flags: 11,
>>>>>>>>> [{"PingCommand":{"hostType":"ConsoleProxy","hostId":3,"wait":0}}]
}
>>>>>>>>> 2013-08-02 06:04:58,575 DEBUG [cloud.agent.Agent]
>> (Agent-Handler-1:)
>>>>>>>>> Received response: Seq 3-2598:  { Ans: , MgmtId: 260071274268429,
>>>>>> via:
>>>>>>> 3,
>>>>>>>>> Ver: v1, Flags: 100010,
>>>>>>>>>
>> [{"PingAnswer":{"_command":{"hostType":"ConsoleProxy","hostId":3,"wait":0},"result":true,"wait":0}}]
>>>>>>>>> }
>>>>>>>>> 2013-08-02 06:05:58,530 DEBUG [cloud.agent.Agent] (UgentTask-5:)
>>>>>>> Sending
>>>>>>>>> ping: Seq 3-2599:  { Cmd , MgmtId: -1, via: 3, Ver: v1,
Flags: 11,
>>>>>>>>> [{"PingCommand":{"hostType":"ConsoleProxy","hostId":3,"wait":0}}]
}
>>>>>>>>> 2013-08-02 06:05:58,576 DEBUG [cloud.agent.Agent]
>> (Agent-Handler-2:)
>>>>>>>>> Received response: Seq 3-2599:  { Ans: , MgmtId: 260071274268429,
>>>>>> via:
>>>>>>> 3,
>>>>>>>>> Ver: v1, Flags: 100010,
>>>>>>>>>
>> [{"PingAnswer":{"_command":{"hostType":"ConsoleProxy","hostId":3,"wait":0},"result":true,"wait":0}}]
>>>>>>>>> }
>>>>>>>>>
>>>>>>>>> cloud.out:
>>>>>>>>> Context property pod: 1
>>>>>>>>> Context property proxy_vm: 2
>>>>>>>>> Context property guid: Proxy.2
>>>>>>>>> Context property root: LABEL
>>>>>>>>> Context property console: hvc0
>>>>>>>>> Context property eth2mask: 255.255.255.0
>>>>>>>>> Context property public.network.device: eth2
>>>>>>>>> Context property private.network.device: eth1
>>>>>>>>> Context property dns1: 192.168.13.31
>>>>>>>>> Context property zone: 1
>>>>>>>>> Context property eth1ip: 172.16.101.2
>>>>>>>>> Context property instance: ConsoleProxy
>>>>>>>>> Context property localgw: 172.16.101.1
>>>>>>>>> Context property premium: true
>>>>>>>>> Context property template: domP
>>>>>>>>> Context property name: v-2-VM
>>>>>>>>> Configure log4j using
>>>>>>> file:/usr/local/cloud/systemvm/conf/log4j-cloud.xml
>>>>>>>>> Log4j configuration from :
>>>>>>> /usr/local/cloud/systemvm/conf/log4j-cloud.xml
>>>>>>>>> 11:01:53,367 ERROR NioConnection:110 - Unable to connect
to remote
>>>>>>>>> 11:01:58,398 ERROR NioConnection:110 - Unable to connect
to remote
>>>>>>>>> 11:35:07,643 ERROR NioConnection:110 - Unable to connect
to remote
>>>>>>>>> 11:35:12,650 ERROR NioConnection:110 - Unable to connect
to remote
>>>>>>>>> 11:35:17,694 ERROR NioConnection:110 - Unable to connect
to remote
>>>>>>>>> 05:43:40,243 ERROR NioConnection:110 - Unable to connect
to remote
>>>>>>>>> 05:43:45,247 ERROR NioConnection:110 - Unable to connect
to remote
>>>>>>>>> 05:43:50,254 ERROR NioConnection:110 - Unable to connect
to remote
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Fri, Aug 2, 2013 at 1:56 PM, Wei ZHOU <ustcweizhou@gmail.com>
>>>>>>> wrote:
>>>>>>>>>> 在host上运行ssh -p 3922 -i /root/.ssh/id_rsa.cloud
>> 169.254.2.100进console
>>>>>>>> proxy
>>>>>>>>>> 看看/var/log/systemvm/下的日志
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2013/8/2 sunko2014 <sunko2014@gmail.com>
>>>>>>>>>>
>>>>>>>>>>> 各位:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>  问题如题,部署环境cloudStack4.02,+xenserver6.0,通过iso方式创建VM后,在chorme、IE6上通过控制台访问VM均失败,下面是management
>>>>>>>>>>> server的log:
>>>>>>>>>>> ... ...
>>>>>>>>>>>          2013-08-02 11:11:50,167 DEBUG [agent.transport.Request]
>>>>>>>>>>> (DirectAgent-393:null) Seq 1-659951545: Processing:
 { Ans: ,
>>>>>>> MgmtId:
>>>>>>>>>>> 260071274268429, via: 1, Ver: v1, Flags: 10,
>>>>>>>>>>> [{"GetVncPortAnswer":{"address":"consoleurl=
>>>>>>>>>>>
>>>>>>>>>>>
>> https://172.16.101.100/console?uuid=2242d3f7-ad5c-134a-652a-b1644f00313d&sessionref=OpaqueRef:f4f1a6a4-5fc7-eab4-96fc-b4043c3e5cf5
>>>>>>>>>>> ","port":5905,"result":true,"wait":0}}]
>>>>>>>>>>> }
>>>>>>>>>>> 2013-08-02 11:11:50,167 DEBUG [agent.transport.Request]
>>>>>>>>>>> (catalina-exec-17:null) Seq 1-659951545: Received:
 { Ans: ,
>>>>>> MgmtId:
>>>>>>>>>>> 260071274268429, via: 1, Ver: v1, Flags: 10,
{ GetVncPortAnswer }
>>>>>> }
>>>>>>>>>>> 2013-08-02 11:11:50,167 DEBUG [cloud.servlet.ConsoleProxyServlet]
>>>>>>>>>>> (catalina-exec-17:null) Port info consoleurl=
>>>>>>>>>>>
>>>>>>>>>>>
>> https://172.16.101.100/console?uuid=2242d3f7-ad5c-134a-652a-b1644f00313d&sessionref=OpaqueRef:f4f1a6a4-5fc7-eab4-96fc-b4043c3e5cf5
>>>>>>>>>>> 2013-08-02<
>> https://172.16.101.100/console?uuid=2242d3f7-ad5c-134a-652a-b1644f00313d&sessionref=OpaqueRef:f4f1a6a4-5fc7-eab4-96fc-b4043c3e5cf52013-08-02
>>>>>>>>> 11:11:50,167
>>>>>>>>>> INFO  [cloud.servlet.ConsoleProxyServlet]
>>>>>>>>>>> (catalina-exec-17:null) Parse host info returned
from executing
>>>>>>>>>>> GetVNCPortCommand. host info: consoleurl=
>>>>>>>>>>>
>>>>>>>>>>>
>> https://172.16.101.100/console?uuid=2242d3f7-ad5c-134a-652a-b1644f00313d&sessionref=OpaqueRef:f4f1a6a4-5fc7-eab4-96fc-b4043c3e5cf5
>>>>>>>>>>> 2013-08-02<
>> https://172.16.101.100/console?uuid=2242d3f7-ad5c-134a-652a-b1644f00313d&sessionref=OpaqueRef:f4f1a6a4-5fc7-eab4-96fc-b4043c3e5cf52013-08-02
>>>>>>>>> 11:11:50,174
>>>>>>>>>> DEBUG [cloud.servlet.ConsoleProxyServlet]
>>>>>>>>>>> (catalina-exec-17:null) Compose console url:
>>>>>>>>>>>
>>>>>>>>>>>
>> https://192-168-45-151.realhostip.com/ajax?token=tsl1xX_XA22fT8WGySZVyWSrZhWM13kgOMdgCRJQJjorDfux2-SSoUWFOJgHQpgBp0ZptEq2Xg3GwFqUGR4BZoTni6p6PhTry5lATbs34ZurK5VBp3S8BnR95AlDgb-xpUbimHYL3cGR7QaZCLPrx2AJOktrEFEoh-FSDyXbiMuyrL2ums3LISK79NVMr6W8flw0odbLopKv9a3BaRzyC-GKmgVzGDqONhUDalbteoiZv9c0LCnWXnTixdj6vzt0rLpY4xgF_9KCxIj191SC1XpFO6lZRBt-hJDa8N73KIkUCnKwwB8tZC34veUjOyBCFuYg5rEIysaJP47D3yQXl3HeBP6YjbMHvZNwwXwa1QbFoKe926CrppkTdIR5B6XIXAm_J3Fv32rAUnqYegKTN2ZV7aF9el2P5bHB_Kw0au6xq-FJtmZwAhskQICDQ5dLnbsUd4048TKw-eIC80sZ5xpyklT1bBSZH45PyacmUag
>>>>>>>>>>> 2013-08-02<
>> https://192-168-45-151.realhostip.com/ajax?token=tsl1xX_XA22fT8WGySZVyWSrZhWM13kgOMdgCRJQJjorDfux2-SSoUWFOJgHQpgBp0ZptEq2Xg3GwFqUGR4BZoTni6p6PhTry5lATbs34ZurK5VBp3S8BnR95AlDgb-xpUbimHYL3cGR7QaZCLPrx2AJOktrEFEoh-FSDyXbiMuyrL2ums3LISK79NVMr6W8flw0odbLopKv9a3BaRzyC-GKmgVzGDqONhUDalbteoiZv9c0LCnWXnTixdj6vzt0rLpY4xgF_9KCxIj191SC1XpFO6lZRBt-hJDa8N73KIkUCnKwwB8tZC34veUjOyBCFuYg5rEIysaJP47D3yQXl3HeBP6YjbMHvZNwwXwa1QbFoKe926CrppkTdIR5B6XIXAm_J3Fv32rAUnqYegKTN2ZV7aF9el2P5bHB_Kw0au6xq-FJtmZwAhskQICDQ5dLnbsUd4048TKw-eIC80sZ5xpyklT1bBSZH45PyacmUag2013-08-02
>>>>>>>>> 11:11:50,175
>>>>>>>>>> DEBUG [cloud.servlet.ConsoleProxyServlet]
>>>>>>>>>>> (catalina-exec-17:null) the console url is ::
>>>>>>>>>>> <html><title>test07</title><frameset><frame
src="
>>>>>>>>>>>
>>>>>>>>>>>
>> https://192-168-45-151.realhostip.com/ajax?token=tsl1xX_XA22fT8WGySZVyWSrZhWM13kgOMdgCRJQJjorDfux2-SSoUWFOJgHQpgBp0ZptEq2Xg3GwFqUGR4BZoTni6p6PhTry5lATbs34ZurK5VBp3S8BnR95AlDgb-xpUbimHYL3cGR7QaZCLPrx2AJOktrEFEoh-FSDyXbiMuyrL2ums3LISK79NVMr6W8flw0odbLopKv9a3BaRzyC-GKmgVzGDqONhUDalbteoiZv9c0LCnWXnTixdj6vzt0rLpY4xgF_9KCxIj191SC1XpFO6lZRBt-hJDa8N73KIkUCnKwwB8tZC34veUjOyBCFuYg5rEIysaJP47D3yQXl3HeBP6YjbMHvZNwwXwa1QbFoKe926CrppkTdIR5B6XIXAm_J3Fv32rAUnqYegKTN2ZV7aF9el2P5bHB_Kw0au6xq-FJtmZwAhskQICDQ5dLnbsUd4048TKw-eIC80sZ5xpyklT1bBSZH45PyacmUag
>>>>>>>>>>> "></frame></frameset></html>
>>>>>>>>>>> 2013-08-02 11:11:53,595 DEBUG [agent.manager.DirectAgentAttache]
>>>>>>>>>>> (DirectAgent-66:null) Ping from 1
>>>>>>>>>>> ... ...
>>>>>>>>>>>        我是部署的高级网络模式,proxy
console system
>>>>>>>>>> vm有三个网卡,net1:192.168.45.151(public
>>>>>>> ip,公司内网,类似公网IP),net2:172.16.101.2(自建的管理网络),net3:169.254.2.100(local)。
>>>>>>>>>>>        从v-2-VM通过管理网络可以访问到xenserver。
>>>>>>>>>>>        对于console的访问流程我不懂,如果需要提供什么log,或者跟踪信息,请指教下。
>>>>>>>>>>>
>>>> --
>>>> Thanks,
>>>> Jijun
>>>>
>>>>
>>
>> --
>> Thanks,
>> Jijun
>>
>>


-- 
Thanks,
Jijun


Mime
View raw message