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 21:37:04 UTC

[jira] [Commented] (BROOKLYN-288) RabbitMQ fails on CentOS7

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

Aled Sage commented on BROOKLYN-288:
------------------------------------

The test at https://github.com/brooklyncentral/brooklyn-rabbitmq-broker/blob/master/catalog.tests.bom is now run regularly, so I'm confident that RabbitMQ does work on CentOS 7.

I also successfully deployed the blueprint below with 0.11.0-rc2:
{noformat}
name: rabbitmq@aws
location:
  jclouds:aws-ec2:eu-west-1:
    osFamily: centos
    osVersion: 7.*
services:
- type: org.apache.brooklyn.entity.messaging.rabbit.RabbitBroker
{noformat}

> RabbitMQ fails on CentOS7
> -------------------------
>
>                 Key: BROOKLYN-288
>                 URL: https://issues.apache.org/jira/browse/BROOKLYN-288
>             Project: Brooklyn
>          Issue Type: Bug
>         Environment: CentOS7
>            Reporter: Duncan Godwin
>
> The RabbitMQ entity fails to install on CentOS7 
> The launching stage fails with the stderr:
> grep: console-out.log: No such file or directory



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)