hi all,

After upgrading from 4.9.3 to 4.11.2rc3 on centos7/KVM,  the old SSMV were
running and working fine until I destroyed them to get them on the current
version (I uploaded the 4.11.2rc3 template before the upgrade)

Now whatever I do there's nothing running on the new Console proxy VM

Oct 18 20:30:53 v-15-VM systemd[1]: Starting /etc/rc.local Compatibility...
Oct 18 20:30:53 v-15-VM systemd[788]: rc-local.service: Failed at step EXEC
spawning /etc/rc.local: Exec format error
Oct 18 20:30:53 v-15-VM systemd[783]: cloud.service: Failed at step CHROOT
spawning /usr/local/cloud/systemvm/_run.sh: No such file or directory

root@v-15-VM:~# systemctl status cloud --no-pager -l
● cloud.service - CloudStack Agent service
   Loaded: loaded (/etc/systemd/system/cloud.service; enabled; vendor
preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Thu
2018-10-18 20:36:45 UTC; 881ms ago
  Process: 1244 ExecStart=/usr/local/cloud/systemvm/_run.sh (code=exited,
status=210/CHROOT)
 Main PID: 1244 (code=exited, status=210/CHROOT)

Oct 18 20:36:45 v-15-VM systemd[1]: cloud.service: Unit entered failed
state.
Oct 18 20:36:45 v-15-VM systemd[1]: cloud.service: Failed with result
'exit-code'.


I that systemvm build valid ?

root@v-15-VM:~# cat /etc/cloudstack-release
Cloudstack Release 4.11.2 Wed Oct 17 19:09:25 UTC 2018

thanks !

Reply via email to