OK, so got back into work and a new SSVM had randomly started after multiple hours, using the new systemVM template.
The console server is in the starting state and has been since I got back to it. I can't stop or change anything via the API or the UI, but thats currently a minor issue. So emergency is currently over, I'll wait on the console server to hopefully eventually give up, or kill it in the database. Thanks for the guidance. Still a little perturbed that it broke and then fixed itself many hours later. On 8 July 2014 09:15, Nick Wales <n...@nickwales.co.uk> wrote: > I have CentOS 6 everywhere. KVM, basic network. > > The previous systemVM template is also showing the same 'No space left on > device' error. > > I can't currently upload any new templates because my SSVM is down and > won't start up because its template is unavailable. There is a ton of space > available on the NFS share used for secondary storage. > > > > > On 8 July 2014 06:43, Rafael Weingartner <rafaelweingart...@gmail.com> > wrote: > >> I had the same problem, at the end I had to shutdown MS, then destroy the >> .vhd file that was created by the CS in the local storage of the clusters >> it used to start system vms. Then, you just need to start MS, and destroy >> the system vms that were already created. >> I was using Xen. >> >> >> >> On Tue, Jul 8, 2014 at 12:56 AM, Carlos Reátegui <create...@gmail.com> >> wrote: >> >> > What is your environment? i.e. what management server os and hypervisors >> > are you using? >> > >> > >> > On Jul 7, 2014, at 6:42 PM, Nick Wales <n...@nickwales.co.uk> wrote: >> > >> > > I upgraded following the guide exactly. >> > > >> > > >> > >> https://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.1/html/Release_Notes/upgrade-instructions.html#upgrade-from-4.1-to-4.2.1 >> > > >> > > Everything went fine until running the script to restart the system >> VM's. >> > > >> > > cloudstack-sysvmadm -u cloud -p <password> -a >> > > >> > > >> > > The console vm restarted but the agent stayed disconnected. The SSVM >> > failed >> > > to restart, the VR restarted ok. >> > > >> > > I couldn't work out why the agent wouldn't connect so decided to >> destroy >> > > console and SSVM's so they would come back happy as they usually do. >> > > >> > > They didn't come back. Now my secondary storage is showing up as 0KB >> in >> > > size, and the system templates status is 'No space left on device' >> so I >> > > can't start any new systemvm's. >> > > >> > > I don't know where to begin to fix this, any ideas? >> > >> > >> >> >> -- >> Rafael Weingärtner >> > >
