Hi, Even if you recreate and it shows alert, then you need to first find out the hypervisor where its running, and connect to it locally using the "Link Local IP Address" shown in the management interface. It is in the format 169.254.x.x
Login to the hypervisor as root # ssh -i /root/.ssh/.id_rsa.cloud -p 3922 root@169.254.x.x It's a standard Debian template. Some commands: To check the systemVM version: cat /etc/cloudstack-release To do a basic troubleshooting: /usr/local/cloud/systemvm/ssvm-check.sh You can apt-get install <package> to install tools to troubleshoot, but when you re-create the systemVM, these packages will be lost. Alert state could be due to networking, or disk-space being full ( logs ) or something went corrupt and the file-system went to read-only mode. All systemVM are safe to be destroyed and they will get re-created again. Cheers, Shashi -----Original Message----- From: Jake G. [mailto:dj_dark_jungl...@yahoo.com] Sent: maandag, 02 december, 2013 10:33 To: users@cloudstack.apache.org Subject: SSVM showing alert status Hi all, My SSVM is showing ALERT as its status. How can I troubleshoot this? Also, Any tips on how to log into the SSVM and CPVM? Thanks, Jake
