You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by "Aled Sage (JIRA)" <ji...@apache.org> on 2017/04/27 20:59:05 UTC
[jira] [Updated] (BROOKLYN-311) RiakCluster fails on CentOS 7
docker containers
[ https://issues.apache.org/jira/browse/BROOKLYN-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aled Sage updated BROOKLYN-311:
-------------------------------
Summary: RiakCluster fails on CentOS 7 docker containers (was: Problems with RiakCluster on Centos 7)
> RiakCluster fails on CentOS 7 docker containers
> -----------------------------------------------
>
> Key: BROOKLYN-311
> URL: https://issues.apache.org/jira/browse/BROOKLYN-311
> Project: Brooklyn
> Issue Type: Bug
> Reporter: Geoff Macartney
> Priority: Minor
>
> I tried to get a RiakCluster entity going on a Centos 7 Docker image based on centos:7 and ran into problems.
> The immediate cause of failure was in the launch stage
> {code}
> d4HlHNpa ssh: launching RiakNodeImpl{id=t02d2i... Mon Jun 20 04:53:30 CDT 2016 Failed env,stderr,stdin,stdout
> ...
> $ br app riak-on-swarm-master ent t02d2ihg3z activity d4HlHNpa stderr
> sh: service: command not found
> {code}
> I worked around that manually by installing 'initscripts' in order to get the service command, but Riak still failed to start, with a less immediately obvious error:
> {code}
> # service riak start
> Failed to get D-Bus connection: Operation not permitted
> Failed to get D-Bus connection: Operation not permitted
> Starting riak (via systemctl): Failed to get D-Bus connection: Operation not permitted
> [FAILED]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)