Re: ConsoleProxy not starting up
Seems there was some issue like that and hence HA kicked in, but finally seems like the CS stopped the vm and then tried starting it. Can you please put more logs to see what happened post sending the startcommand On 06/04/13 7:12 PM, "CK" wrote: >The XS is a brand new setup and I have checked the files mentioned and >they >are there. However, I have noticed the in the logs (in the original email) >that there may be a connectivity issue. What do you think? > > >On 2 April 2013 09:39, Pranav Saxena wrote: > >> Can you check if your systemvm.iso is copied to your host and also try >>to >> copy vhd-util to your XS host at /opt/xensource/bin if your XS host is a >> brand new setup . Sometimes the systemvm.iso is not found on your host >> when you build the repo and the systemVM's continue to remain in the >> starting state. >> >> Thanks, >> Pranav >> >> -Original Message- >> From: CK [mailto:cloudw...@gmail.com] >> Sent: Tuesday, April 02, 2013 2:31 AM >> To: cloudstack-us...@incubator.apache.org >> Subject: ConsoleProxy not starting up >> >> Hi, >> I am having a problem with the ConsoleProxy VM starting up, in the CS UI >> the consoleproxy is showing as "Starting up" and remains in this state. >>I >> have restarted the cloud-management service as well as the console VM on >> the host, but still appears to be hung. >> >> I am unable to restart or destroy the console VM in the UI, as no such >> option. >> >> Any help would be appreciated. >> >> The CS management log shows the following: >> >> >> 2013-04-01 21:35:35,553 INFO [utils.component.ComponentLocator] >> (Thread-5:null) Asking ConsoleProxyAlert to shutdown. >> 2013-04-01 21:35:36,626 INFO [utils.component.ComponentLocator] >> (Thread-5:null) Asking Manager ConsoleProxyManager to shutdown. >> 2013-04-01 21:35:36,626 INFO >>[cloud.consoleproxy.ConsoleProxyManagerImpl] >> (Thread-5:null) Stop console proxy manager >> 2013-04-01 21:35:37,626 INFO [utils.component.ComponentLocator] >> (Thread-5:null) Skipping Manager ConsoleProxyManager because it is not >>in >> a state to shutdown. >> 2013-04-01 21:35:47,256 DEBUG [utils.component.ComponentLocator] >> (main:null) Looking for class >> com.cloud.consoleproxy.ConsoleProxyBalanceAllocator >> 2013-04-01 21:35:47,257 INFO [utils.component.ComponentLocator] >> (main:null) Found component: >>com.cloud.consoleproxy.ConsoleProxyAllocator >> in com.cloud.consoleproxy.ConsoleProxyBalanceAllocator - Balance >> 2013-04-01 21:35:47,333 DEBUG [utils.component.ComponentLocator] >> (main:null) Looking for class com.cloud.alert.ConsoleProxyAlertAdapter >> 2013-04-01 21:35:47,334 INFO [utils.component.ComponentLocator] >> (main:null) Found component: com.cloud.alert.AlertAdapter in >> com.cloud.alert.ConsoleProxyAlertAdapter - ConsoleProxyAlert >> 2013-04-01 21:35:47,518 INFO [utils.component.ComponentLocator] >> (main:null) Found component: com.cloud.vm.dao.ConsoleProxyDao in >> com.cloud.vm.dao.ConsoleProxyDaoImpl - ConsoleProxyDao >> 2013-04-01 21:35:47,697 INFO [utils.component.ComponentLocator] >> (main:null) Found component: com.cloud.consoleproxy.ConsoleProxyManager >>in >> com.cloud.consoleproxy.ConsoleProxyManagerImpl - ConsoleProxyManager >> 2013-04-01 21:35:47,697 INFO [utils.component.ComponentLocator] >> (main:null) Found component: com.cloud.consoleproxy.ConsoleProxyService >>in >> com.cloud.consoleproxy.ConsoleProxyManagerImpl - ConsoleProxyManager >> 2013-04-01 21:35:50,355 INFO [utils.component.ComponentLocator] >> (main:null) Starting singleton DAO: ConsoleProxyDao >> 2013-04-01 21:35:52,284 INFO [utils.component.ComponentLocator] >> (main:null) Instantiating Adapter: ConsoleProxyAlert >> 2013-04-01 21:35:52,682 INFO [utils.component.ComponentLocator] >> (main:null) Instantiating Manager: ConsoleProxyManager >> 2013-04-01 21:35:52,937 DEBUG [utils.component.ComponentLocator] >> (main:null) Injecting singleton Manager: ConsoleProxyManager >> 2013-04-01 21:35:53,364 INFO [utils.component.ComponentLocator] >> (main:null) Configuring singleton Manager: ConsoleProxyManager >> 2013-04-01 21:35:53,364 INFO >>[cloud.consoleproxy.ConsoleProxyManagerImpl] >> (main:null) Start configuring console proxy manager : >>ConsoleProxyManager >> 2013-04-01 21:35:53,364 INFO >>[cloud.consoleproxy.ConsoleProxyManagerImpl] >> (main:null) Console proxy max session soft limit : 50 >> 2013-04-01 21:35:53,364 INFO >>[cloud.consoleproxy.ConsoleProxyManagerImpl] >> (main:null) Console proxy standby capacity : 10 >> 2013-04-01 21:35:53,380 DEBUG [agent.manager.AgentManagerImpl] >>(main:null) >> Registering listener ConsoleProxyListener with id 12 >> 2013-04-01 21:35:53,383 INFO >>[cloud.consoleproxy.ConsoleProxyManagerImpl] >> (main:null) Console Proxy Manager is configured. >> 2013-04-01 21:35:53,511 INFO [utils.component.ComponentLocator] >> (main:null) Injecting singleton Adapter: ConsoleProxyAlert >> 2013-04-01 21:35:53,511 INFO [utils.component.ComponentLocator] >> (main:null) Configuring singleton Adapter:
Re: ConsoleProxy not starting up
The XS is a brand new setup and I have checked the files mentioned and they are there. However, I have noticed the in the logs (in the original email) that there may be a connectivity issue. What do you think? On 2 April 2013 09:39, Pranav Saxena wrote: > Can you check if your systemvm.iso is copied to your host and also try to > copy vhd-util to your XS host at /opt/xensource/bin if your XS host is a > brand new setup . Sometimes the systemvm.iso is not found on your host > when you build the repo and the systemVM's continue to remain in the > starting state. > > Thanks, > Pranav > > -Original Message- > From: CK [mailto:cloudw...@gmail.com] > Sent: Tuesday, April 02, 2013 2:31 AM > To: cloudstack-us...@incubator.apache.org > Subject: ConsoleProxy not starting up > > Hi, > I am having a problem with the ConsoleProxy VM starting up, in the CS UI > the consoleproxy is showing as "Starting up" and remains in this state. I > have restarted the cloud-management service as well as the console VM on > the host, but still appears to be hung. > > I am unable to restart or destroy the console VM in the UI, as no such > option. > > Any help would be appreciated. > > The CS management log shows the following: > > > 2013-04-01 21:35:35,553 INFO [utils.component.ComponentLocator] > (Thread-5:null) Asking ConsoleProxyAlert to shutdown. > 2013-04-01 21:35:36,626 INFO [utils.component.ComponentLocator] > (Thread-5:null) Asking Manager ConsoleProxyManager to shutdown. > 2013-04-01 21:35:36,626 INFO [cloud.consoleproxy.ConsoleProxyManagerImpl] > (Thread-5:null) Stop console proxy manager > 2013-04-01 21:35:37,626 INFO [utils.component.ComponentLocator] > (Thread-5:null) Skipping Manager ConsoleProxyManager because it is not in > a state to shutdown. > 2013-04-01 21:35:47,256 DEBUG [utils.component.ComponentLocator] > (main:null) Looking for class > com.cloud.consoleproxy.ConsoleProxyBalanceAllocator > 2013-04-01 21:35:47,257 INFO [utils.component.ComponentLocator] > (main:null) Found component: com.cloud.consoleproxy.ConsoleProxyAllocator > in com.cloud.consoleproxy.ConsoleProxyBalanceAllocator - Balance > 2013-04-01 21:35:47,333 DEBUG [utils.component.ComponentLocator] > (main:null) Looking for class com.cloud.alert.ConsoleProxyAlertAdapter > 2013-04-01 21:35:47,334 INFO [utils.component.ComponentLocator] > (main:null) Found component: com.cloud.alert.AlertAdapter in > com.cloud.alert.ConsoleProxyAlertAdapter - ConsoleProxyAlert > 2013-04-01 21:35:47,518 INFO [utils.component.ComponentLocator] > (main:null) Found component: com.cloud.vm.dao.ConsoleProxyDao in > com.cloud.vm.dao.ConsoleProxyDaoImpl - ConsoleProxyDao > 2013-04-01 21:35:47,697 INFO [utils.component.ComponentLocator] > (main:null) Found component: com.cloud.consoleproxy.ConsoleProxyManager in > com.cloud.consoleproxy.ConsoleProxyManagerImpl - ConsoleProxyManager > 2013-04-01 21:35:47,697 INFO [utils.component.ComponentLocator] > (main:null) Found component: com.cloud.consoleproxy.ConsoleProxyService in > com.cloud.consoleproxy.ConsoleProxyManagerImpl - ConsoleProxyManager > 2013-04-01 21:35:50,355 INFO [utils.component.ComponentLocator] > (main:null) Starting singleton DAO: ConsoleProxyDao > 2013-04-01 21:35:52,284 INFO [utils.component.ComponentLocator] > (main:null) Instantiating Adapter: ConsoleProxyAlert > 2013-04-01 21:35:52,682 INFO [utils.component.ComponentLocator] > (main:null) Instantiating Manager: ConsoleProxyManager > 2013-04-01 21:35:52,937 DEBUG [utils.component.ComponentLocator] > (main:null) Injecting singleton Manager: ConsoleProxyManager > 2013-04-01 21:35:53,364 INFO [utils.component.ComponentLocator] > (main:null) Configuring singleton Manager: ConsoleProxyManager > 2013-04-01 21:35:53,364 INFO [cloud.consoleproxy.ConsoleProxyManagerImpl] > (main:null) Start configuring console proxy manager : ConsoleProxyManager > 2013-04-01 21:35:53,364 INFO [cloud.consoleproxy.ConsoleProxyManagerImpl] > (main:null) Console proxy max session soft limit : 50 > 2013-04-01 21:35:53,364 INFO [cloud.consoleproxy.ConsoleProxyManagerImpl] > (main:null) Console proxy standby capacity : 10 > 2013-04-01 21:35:53,380 DEBUG [agent.manager.AgentManagerImpl] (main:null) > Registering listener ConsoleProxyListener with id 12 > 2013-04-01 21:35:53,383 INFO [cloud.consoleproxy.ConsoleProxyManagerImpl] > (main:null) Console Proxy Manager is configured. > 2013-04-01 21:35:53,511 INFO [utils.component.ComponentLocator] > (main:null) Injecting singleton Adapter: ConsoleProxyAlert > 2013-04-01 21:35:53,511 INFO [utils.component.ComponentLocator] > (main:null) Configuring singleton Adapter: ConsoleProxyAlert > 2013-04-01 21:35:53,511 INFO [cloud.alert.ConsoleProxyAlertAdapter] > (main:null) Start configuring console proxy alert manager : > ConsoleProxyAlert > 2013-04-01 21:35:53,838 INFO [cloud.ha.HighAvailabilityManagerImpl] > (main:null) Schedule vm for HA: VM[ConsoleProxy|v-2-VM] > 2013-04-01 21:35:53,880 INFO [cloud.ha.HighAvailabilityMa
RE: ConsoleProxy not starting up
Can you check if your systemvm.iso is copied to your host and also try to copy vhd-util to your XS host at /opt/xensource/bin if your XS host is a brand new setup . Sometimes the systemvm.iso is not found on your host when you build the repo and the systemVM's continue to remain in the starting state. Thanks, Pranav -Original Message- From: CK [mailto:cloudw...@gmail.com] Sent: Tuesday, April 02, 2013 2:31 AM To: cloudstack-us...@incubator.apache.org Subject: ConsoleProxy not starting up Hi, I am having a problem with the ConsoleProxy VM starting up, in the CS UI the consoleproxy is showing as "Starting up" and remains in this state. I have restarted the cloud-management service as well as the console VM on the host, but still appears to be hung. I am unable to restart or destroy the console VM in the UI, as no such option. Any help would be appreciated. The CS management log shows the following: 2013-04-01 21:35:35,553 INFO [utils.component.ComponentLocator] (Thread-5:null) Asking ConsoleProxyAlert to shutdown. 2013-04-01 21:35:36,626 INFO [utils.component.ComponentLocator] (Thread-5:null) Asking Manager ConsoleProxyManager to shutdown. 2013-04-01 21:35:36,626 INFO [cloud.consoleproxy.ConsoleProxyManagerImpl] (Thread-5:null) Stop console proxy manager 2013-04-01 21:35:37,626 INFO [utils.component.ComponentLocator] (Thread-5:null) Skipping Manager ConsoleProxyManager because it is not in a state to shutdown. 2013-04-01 21:35:47,256 DEBUG [utils.component.ComponentLocator] (main:null) Looking for class com.cloud.consoleproxy.ConsoleProxyBalanceAllocator 2013-04-01 21:35:47,257 INFO [utils.component.ComponentLocator] (main:null) Found component: com.cloud.consoleproxy.ConsoleProxyAllocator in com.cloud.consoleproxy.ConsoleProxyBalanceAllocator - Balance 2013-04-01 21:35:47,333 DEBUG [utils.component.ComponentLocator] (main:null) Looking for class com.cloud.alert.ConsoleProxyAlertAdapter 2013-04-01 21:35:47,334 INFO [utils.component.ComponentLocator] (main:null) Found component: com.cloud.alert.AlertAdapter in com.cloud.alert.ConsoleProxyAlertAdapter - ConsoleProxyAlert 2013-04-01 21:35:47,518 INFO [utils.component.ComponentLocator] (main:null) Found component: com.cloud.vm.dao.ConsoleProxyDao in com.cloud.vm.dao.ConsoleProxyDaoImpl - ConsoleProxyDao 2013-04-01 21:35:47,697 INFO [utils.component.ComponentLocator] (main:null) Found component: com.cloud.consoleproxy.ConsoleProxyManager in com.cloud.consoleproxy.ConsoleProxyManagerImpl - ConsoleProxyManager 2013-04-01 21:35:47,697 INFO [utils.component.ComponentLocator] (main:null) Found component: com.cloud.consoleproxy.ConsoleProxyService in com.cloud.consoleproxy.ConsoleProxyManagerImpl - ConsoleProxyManager 2013-04-01 21:35:50,355 INFO [utils.component.ComponentLocator] (main:null) Starting singleton DAO: ConsoleProxyDao 2013-04-01 21:35:52,284 INFO [utils.component.ComponentLocator] (main:null) Instantiating Adapter: ConsoleProxyAlert 2013-04-01 21:35:52,682 INFO [utils.component.ComponentLocator] (main:null) Instantiating Manager: ConsoleProxyManager 2013-04-01 21:35:52,937 DEBUG [utils.component.ComponentLocator] (main:null) Injecting singleton Manager: ConsoleProxyManager 2013-04-01 21:35:53,364 INFO [utils.component.ComponentLocator] (main:null) Configuring singleton Manager: ConsoleProxyManager 2013-04-01 21:35:53,364 INFO [cloud.consoleproxy.ConsoleProxyManagerImpl] (main:null) Start configuring console proxy manager : ConsoleProxyManager 2013-04-01 21:35:53,364 INFO [cloud.consoleproxy.ConsoleProxyManagerImpl] (main:null) Console proxy max session soft limit : 50 2013-04-01 21:35:53,364 INFO [cloud.consoleproxy.ConsoleProxyManagerImpl] (main:null) Console proxy standby capacity : 10 2013-04-01 21:35:53,380 DEBUG [agent.manager.AgentManagerImpl] (main:null) Registering listener ConsoleProxyListener with id 12 2013-04-01 21:35:53,383 INFO [cloud.consoleproxy.ConsoleProxyManagerImpl] (main:null) Console Proxy Manager is configured. 2013-04-01 21:35:53,511 INFO [utils.component.ComponentLocator] (main:null) Injecting singleton Adapter: ConsoleProxyAlert 2013-04-01 21:35:53,511 INFO [utils.component.ComponentLocator] (main:null) Configuring singleton Adapter: ConsoleProxyAlert 2013-04-01 21:35:53,511 INFO [cloud.alert.ConsoleProxyAlertAdapter] (main:null) Start configuring console proxy alert manager : ConsoleProxyAlert 2013-04-01 21:35:53,838 INFO [cloud.ha.HighAvailabilityManagerImpl] (main:null) Schedule vm for HA: VM[ConsoleProxy|v-2-VM] 2013-04-01 21:35:53,880 INFO [cloud.ha.HighAvailabilityManagerImpl] (main:null) Schedule vm for HA: VM[ConsoleProxy|v-2-VM] 2013-04-01 21:35:53,886 INFO [utils.component.ComponentLocator] (main:null) Starting singleton Manager: ConsoleProxyManager 2013-04-01 21:35:53,886 INFO [cloud.consoleproxy.ConsoleProxyManagerImpl] (main:null) Start console proxy manager 2013-04-01 21:35:53,886 INFO [utils.component.ComponentLocator] (main:null) Started Manager: ConsoleProx
