perform the upgrade again.
Cheers,
Shashi
-Original Message-
From: Kelven Yang [mailto:kelven.y...@citrix.com]
Sent: 10 April 2013 00:41
To: users@cloudstack.apache.org
Subject: Re: issue after upgrade from 2.2.14 to 4.0.0 "Unable to find or
allocate console proxy resource"
ot; wrote:
>
>>HI Kelvin,
>>
>>Since the console proxy was not working , I deleted it hoping that it
>>would be recreated. Now it is not being re-created and all I have is
>>the "Unable to find or allocate console proxy resource" in the logs.
>>
>
On Tue, Apr 09, 2013 at 07:17:48AM +, Shashi Dahal wrote:
> Hi kelven,
>
> Log level is set to ALL.
The loglevels are INFO,WARN,DEBUG,TRACE. Find
/etc/cloud/management/log4j-cloud.xml and s/DEBUG/TRACE/g to enable
trace logs for all modules. This will write a lot of logs and can
consume dis
: issue after upgrade from 2.2.14 to 4.0.0 "Unable to find or
allocate console proxy resource"
You need to turn on management server log level instead of that in
agent.properties. (do it at /etc/cloud/management-server/log4j-cloud.xml"
). Need to more log info to find what's go
t;
>
>From: Kelven Yang [kelven.y...@citrix.com]
>Sent: Monday, April 08, 2013 7:05 PM
>To: users@cloudstack.apache.org
>Subject: Re: issue after upgrade from 2.2.14 to 4.0.0 "Unable to find or
>allocate console proxy resource"
>
rs,
Shashi
From: Kelven Yang [kelven.y...@citrix.com]
Sent: Monday, April 08, 2013 7:05 PM
To: users@cloudstack.apache.org
Subject: Re: issue after upgrade from 2.2.14 to 4.0.0 "Unable to find or
allocate console proxy resource"
What do you see from CloudStack
What do you see from CloudStack management UI about the running status of
console proxy VM?
If you can login into console proxy VM, try to find log from within it
under /var/log/cloud/systemvm.log
Kelven
On 4/8/13 6:15 AM, "Shashi Dahal" wrote:
>Hi,
>
>I did an upgrade from cloudstack 2.2.14 t
Hi,
I did an upgrade from cloudstack 2.2.14 to 4.0.0 following the release notes
"Upgrade from 2.2.14 to 4.0.0-incubating" . I did not had any issues with the
upgrade itself.
I had to change the command : cloud-sysvmadm -d 192.168.1.5 -u cloud -p
password -c -r to cloud-sysvmadm -d 192.168
