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 disk
From the log, your zone is not back to ready status, you may want to check
if all your hosts, primary storage and secondary storage are UP, this
prevents system to launch console proxy
Kelven
On 4/9/13 12:17 AM, Shashi Dahal s.da...@leaseweb.com wrote:
Hi kelven,
Log level is set to ALL.
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
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.
I do not have any console proxy now.
Cheers,
Shashi
