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.1.5 -u cloud -p password -s -r
as the -c is not valid , and accordingly all system VMs were restarted

-------
Stopping and starting 1 secondary storage vm(s)...
Done stopping and starting secondary storage vm(s)

Stopping and starting 1 console proxy vm(s)...
Done stopping and starting console proxy vm(s).

Stopping and starting 1 running routing vm(s)...
Done restarting router(s).
-------

I was able to login to the console proxy and run 
/usr/local/cloud/systemvm/ssvm-check.sh  and it reported everything working 
fine.
But console did not worked, so I destroyed the console-proxy , as it would 
recreate it again.

Now, I end up with this line in the logs:
WARN  [cloud.consoleproxy.ConsoleProxyManagerImpl] (catalina-exec-20:null) 
Unable to find or allocate console proxy resource

I edited the debug level from INFO to DEBUG in agent.properties in the 
hypervisors hoping it will show more lines, but that is the only line I end up 
with regarding console proxy.
I also doubled the value in consoleproxy.capacity.standby  compared to 
consoleproxy.session.max so that it would create a new console proxy, which it 
is not.

If you have faced this issue before, please do let me know how to proceed.


Cheers,
Shashi

Reply via email to