[
https://issues.apache.org/jira/browse/CLOUDSTACK-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13926315#comment-13926315
]
ASF subversion and git services commented on CLOUDSTACK-6220:
-------------------------------------------------------------
Commit f0a7a7f23e0ac334fab3a3e58de10f0bd07da819 in cloudstack's branch
refs/heads/resize-root from [~mlsorensen]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f0a7a7f ]
CLOUDSTACK-6220: Take 2, Fix cloudstack init scripts so that they
don't use fully qualified path as script name. Fix for
commit 9dd57c22b02afcddb1d6c8ddc3e1b578961454e3
> Cloudstack agent fails to start due to broken init script
> ---------------------------------------------------------
>
> Key: CLOUDSTACK-6220
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6220
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup
> Affects Versions: 4.4.0
> Environment: CentOS 6.5 KVM/libvirt
> Reporter: Nux
> Labels: agent
>
> Hello,
> On 4.4 `service cloudstack-agent start` fails with:
> # service cloudstack-agent start
> Starting Cloud Agent:
> touch: cannot touch `/var/lock/subsys//etc/init.d/cloudstack-agent': No such
> file or directory
> /etc/init.d/cloudstack-agent used to have this which worked fine:
> whatami=cloudstack-agent
> SHORTNAME="$whatami"
> Now it has been replaced with this which fails:
> SHORTNAME="$0"
> A possible solution is to replace "$0" with `basename "$0"`
--
This message was sent by Atlassian JIRA
(v6.2#6252)
