A look into the log-files of the hosts where the router shall be deployed to might be helpfull as well. Even if it is not "running" on the host - it might be that the host has some trouble to start the job. Regards,
Chris Am Fr., 8. Juli 2022 um 14:30 Uhr schrieb Ricardo Pertuz < ricardo.per...@kuasar.co>: > Hi, > > Thanks for the quick reply, these would be the answers: > > 0. yes, full reboot Management Server and Hosts > > 1. MS Servers are UP (we have 2) > 2. The affected VM is a virtual router, still in starting state, no > running on any host > 3. Capacity is less than 10% at the moment > 4. I am able to launch new instances without error but in other VPC, not > in the affected one as the VR is in starting state, so not VPC cleanup is > possible > > I have restarted the MS to check if I filter some logs from this VR, none > so far. > > BR, > > Ricardo > > On 7/07/22, 10:23 PM, "Harikrishna Patnala" < > harikrishna.patn...@shapeblue.com> wrote: > > Hi Ricardo, > > I assume the complete reboot means the CloudStack management server > restart/reboot or is it a KVM host reboot ? > > Please check for the following if anything can be found. > > 1. Check for hosts status from CloudStack UI if it is UP > 2. Check if these VMs are there and running on the host > 3. Check if hosts have enough capacity > 4. Check if new VMs can be deployed as well > > You can focus on one of the VM's id and look for the last log related > to the VM wrt any operation, which may give us some hints. > > Thanks, > Harikrishna > ________________________________ > From: Ricardo Pertuz <ricardo.per...@kuasar.co> > Sent: Friday, July 8, 2022 8:12 AM > To: users@cloudstack.apache.org <users@cloudstack.apache.org> > Subject: endless starting state > > Hi team, > > After a complete reboot, many vms are stuck in an endless starting > state, no error in logs, what else can be checked? > > ACS: 4.15.2 > Hyp: KVM > > Regards, > > > > > >
