Re: [Xen-API] XCP 1.6 BETA compatibility issue with XVP

[Black Bird <blackbird1758@xxxxxxxxx>]

Should the installer be able to upgrade from Beta 2 to Beta 3?

On Thu, Nov 1, 2012 at 2:50 AM, Mike McClurg <mike.mcclurg@xxxxxxxxxx> wrote:
> On 30/10/12 12:28, Black Bird wrote:
>> I omitted to mention that does not seem to be anything interesting in
>> xvp.log on the xvpappliance, however in xensource.log on the XCP
>> master I found the following sequence:
>
> That just looks like XVP is asking the XCP host to report back
> information, which doesn't seem to be erroring out. I don't think that
> anything below indicates a problem with XCP. The premature termination
> of connection is harmless.
>
> I have no idea who maintains XVP, but you would probably be best
> emailing them and asking for XCP 1.6 support.
>
>>
>> Oct 30 22:22:52 xen1 xapi: [debug|xen1|38213 INET
>> 0.0.0.0:80|session.login_with_password D:2cec560e9164|xapi] Successful
>> local authentication user root from HTTP request from Internet with
>> User-Agent: XML-RPC for PHP 2.2.2
>> Oct 30 22:22:52 xen1 xapi: [ info|xen1|38213 INET
>> 0.0.0.0:80|session.login_with_password D:2cec560e9164|xapi]
>> Session.create trackid=8ff947eeca15341a508d30865da3b6ca pool=false
>> uname=root is_local_superuser=true auth_user_sid=
>> parent=trackid=9834f5af41c964e225f24279aefe4e49
>> Oct 30 22:22:52 xen1 xapi: [debug|xen1|38213 INET
>> 0.0.0.0:80|session.login_with_password D:2cec560e9164|mscgen]
>> xapi=>xapi 
>> [label="<methodCall><methodName>session.get_uuid</methodName><params><param><value>OpaqueRef:e4dd64e0-387b-7434-f36a-2a0b247213b2</value></param><param><value>OpaqueRef:e4dd64e0-387b-7434-f36a-2a0b247213b2</value></param></params></methodCall>"];
>> Oct 30 22:22:52 xen1 xapi: [debug|xen1|38214 UNIX
>> /var/xapi/xapi||dummytaskhelper] task dispatch:session.get_uuid
>> D:0eac765dd856 created by task D:2cec560e9164
>> Oct 30 22:22:52 xen1 xapi: [debug|xen1|38214 UNIX
>> /var/xapi/xapi|dispatch:session.get_uuid D:0eac765dd856|api_readonly]
>> session.get_uuid
>> Oct 30 22:22:52 xen1 xapi: [debug|xen1|38213 INET
>> 0.0.0.0:80|dispatch:session.get_this_host D:8b8ccb87798d|api_readonly]
>> session.get_this_host
>> Oct 30 22:22:52 xen1 xapi: [debug|xen1|38213 INET
>> 0.0.0.0:80|dispatch:host.get_by_name_label
>> D:9062e466be36|api_readonly] host.get_by_name_label
>> Oct 30 22:22:52 xen1 xapi: [debug|xen1|38213 INET
>> 0.0.0.0:80|dispatch:host.get_enabled D:fc6b7fc3f4aa|api_readonly]
>> host.get_enabled
>> Oct 30 22:22:52 xen1 xapi: [debug|xen1|38213 INET
>> 0.0.0.0:80|host.compute_free_memory R:299b6bedf05f|audit]
>> Host.compute_free_memory: host = 'a53d1a5a-a9a3-4314-8295-1af5584cf02b
>> (xen1)'
>> Oct 30 22:22:52 xen1 xapi: [debug|xen1|38213 INET
>> 0.0.0.0:80|dispatch:host.get_metrics D:95e96b3be98e|api_readonly]
>> host.get_metrics
>> Oct 30 22:22:52 xen1 xapi: [debug|xen1|38213 INET
>> 0.0.0.0:80|dispatch:host_metrics.get_memory_total
>> D:a6095306d906|api_readonly] host_metrics.get_memory_total
>> Oct 30 22:22:52 xen1 xapi: [debug|xen1|38213 INET
>> 0.0.0.0:80|dispatch:host.get_software_version
>> D:88220f079807|api_readonly] host.get_software_version
>> Oct 30 22:22:52 xen1 xapi: [debug|xen1|38213 INET
>> 0.0.0.0:80||http_critical] Premature termination of connection!
>>
>> This sequence of log entries is repeated whenever the xvp screen refreshes.
>>
>>
>> On Tue, Oct 30, 2012 at 9:58 PM, Black Bird <blackbird1758@xxxxxxxxx> wrote:
>>> Hi all
>>>
>>> I'm not sure this is the right forum for this.
>>>
>>> I use the XVP utility to manage my XCP pool, the main use being the vm
>>> status and remote console.  I've used the xvpappliance 1.12.0-1 to
>>> manage my XCP1.1 pool successfully for many months.
>>>
>>> Recently I upgraded my XCP pool to 1.6.06-61002c and the xvpappliance
>>> stopped working.  Specifically, after logging into the https
>>> interface, I get the message 'Error: Problem handing response: Cannot
>>> call method 'getElementsByTagName' of null'.
>>>
>>> Looking up the xvp tool homepage, I realised there was a new xvp
>>> version 1.14.0, whose features included 'The xvp daemon and related
>>> utilities are now built against version 6.0.0 of Citrix's
>>> libxenserver, instead of version 5.6.100.'
>>>
>>> There's my answer I thought.  I downloaded the zip, unzipped, xe
>>> vm-imported, modified vif as usual, configured appliance from
>>> xenconsole, during which the pool was connected to without any
>>> apparent error.  When finished, I logged into the https interface as
>>> before, and I got exactly the same error.
>>>
>>> Has anyone had any luck with XVP1.14 and XCP 1.6?
>>
>> _______________________________________________
>> Xen-api mailing list
>> Xen-api@xxxxxxxxxxxxx
>> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
>>
>
>
> _______________________________________________
> Xen-api mailing list
> Xen-api@xxxxxxxxxxxxx
> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api