Dear all, The script failed to restart the system VMs. See below.
All my system VMs (except one virtual router) are in "Starting" state but it never got started. Any idea how to resolve this issue? === nohup: ignoring input /usr/bin/cloudstack-sysvmadm: line 21: /etc/rc.d/init.d/functions: No such file or directory Stopping and starting 1 secondary storage vm(s)... Done stopping and starting secondary storage vm(s) Stopping and starting 1 console proxy vm(s)... ERROR: Failed to start console proxy vm with id 1903 Done stopping and starting console proxy vm(s) . Stopping and starting 2 running routing vm(s)... ERROR: Failed to restart domainRouter with id 1931 ERROR: Failed to restart domainRouter with id 1930 Done restarting router(s). === Looking forward to your reply, thank you. Cheers. On Tue, Sep 24, 2013 at 2:54 AM, Indra Pramana <in...@sg.or.id> wrote: > Is it normal for the cloudstack-sysvmadm script to take very long to run? > It has been more than 30 minutes and it's still restarting the second > system VM. > > === > root@cs-mgmt-01:~/cloudstack3# tail -f sysvm.log > nohup: ignoring input > /usr/bin/cloudstack-sysvmadm: line 21: /etc/rc.d/init.d/functions: No such > file > > Stopping and starting 1 secondary storage vm(s)... > Done stopping and starting secondary storage vm(s) > > Stopping and starting 1 console proxy vm(s)... > === > > If it's normal, any reason why? I presume restarting a VM shouldn't take > that long in normal circumstances? > > Any insight is appreciated. :) > > Thank you. >
