brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aled Sage (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BROOKLYN-311) Problems with RiakCluster on Centos 7
Date Thu, 27 Apr 2017 20:59:05 GMT

    [ https://issues.apache.org/jira/browse/BROOKLYN-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15987662#comment-15987662
] 

Aled Sage commented on BROOKLYN-311:
------------------------------------

[~geomacy] do you know if this was fixed ever?

If not, then I think it's reasonable we can expect some things to be on the OS when we try
to install Riak. If someone wants to install into a docker container (like it was a light-weight
VM), we can expect the user to prepare a container image that has {{systemd}} and stuff like
that.

Writing our Riak node/cluster entity to work with a very cut-down container I think is an
"improvement", rather than a "bug".

I'm going to change the title (from "Problems with RiakCluster on Centos 7" to "RiakCluster
fails on CentOS 7 docker containers"), and change it to an "improvement" rather than a "bug".
Please change it back if you think that's the wrong thing to do.

> Problems with RiakCluster on Centos 7
> -------------------------------------
>
>                 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)

Mime
View raw message