You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Tony Scheffer (JIRA)" <ji...@apache.org> on 2015/04/18 18:07:58 UTC
[jira] [Created] (CLOUDSTACK-8391) Secondary VM not properly
configured after install
Tony Scheffer created CLOUDSTACK-8391:
-----------------------------------------
Summary: Secondary VM not properly configured after install
Key: CLOUDSTACK-8391
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8391
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.4.2
Environment: CentOS 6.6, KVM.
[root@nas ~]# rpm -qa | grep cloud
cloudstack-awsapi-4.4.2-NONOSS_1.el6.x86_64
cloudstack-common-4.4.2-NONOSS_1.el6.x86_64
cloudstack-management-4.4.2-NONOSS_1.el6.x86_64
cloudstack-agent-4.4.2-NONOSS_1.el6.x86_64
Reporter: Tony Scheffer
After installing and deploying CloudStack, the secondary VM does not have the agent running.
Trying the init script;
root@s-1-VM:~# /etc/init.d/cloud status
Failed
/etc/init.d/cloud: line 130: get_pids: command not found
CloudStack cloud service is not running
The troubleshoot script also seems to be absent;
root@s-1-VM:~# ls -l /usr/local/cloud/systemvm/ssvm-check.sh
ls: cannot access /usr/local/cloud/systemvm/ssvm-check.sh: No such file or directory
find / -name ssvm-check.sh
results in nothing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)