Not able to start rabbitmq-server in RHEL 7.2

[odu...@hawk.iit.edu]

I recently upgraded from RHEL 6.7 to RHEL 7.2 and have not

been able to startup rabbitmq-server in RHEL7.2. In RHEL 6.7, there was no issue.

I did google and looks like most of the rabbitmq-server start issues

are normally related to SElinux or firewalld blocking port.

I'm not using SElinux in my configuration:

        # cat /etc/sysconfig/selinux

        cat: /etc/sysconfig/selinux: No such file or directory

Firewalld is not installed either:

        # systemctl status firewalld

        â firewalld.service

           Loaded: not-found (Reason: No such file or directory)

           Active: inactive (dead)

I have the following OS and packages installed:

        Red Hat Enterprise Linux Server release 7.2 (Maipo)

        erlang-18.2-1.el7.centos.x86_64

        rabbitmq-server-3.6.1-1.noarch

 

# systemctl enable rabbitmq-server.service

rabbitmq-server.service is not a native service, redirecting to /sbin/chkconfig.

Executing /sbin/chkconfig rabbitmq-server on

<TestNode-a:root>/root:

# systemctl start rabbitmq-server.service

Job for rabbitmq-server.service failed because the control process exited with error code. See "systemctl status rabbitmq-server.service" and "j

ournalctl -xe" for details.

 

<TestNode-a:root>/root:

 

# journalctl -xe

-- Unit rabbitmq-server.service has begun starting up.

Sep 10 19:52:38 TestNode-a audispd[520]: node=TestNode-a type=USER_AUTH msg=audit(1473537158.651:3196): pid=28001 uid=0 auid=42949672

Sep 10 19:52:38 TestNode-a audispd[520]: node=TestNode-a type=USER_AUTH msg=audit(1473537158.682:3197): pid=28027 uid=0 auid=42949672

Sep 10 19:52:38 TestNode-a audispd[520]: node=TestNode-a type=USER_AUTH msg=audit(1473537158.687:3198): pid=28029 uid=0 auid=42949672

Sep 10 19:52:38 TestNode-a rabbitmq-server[27929]: Starting rabbitmq-server: FAILED - check /var/log/rabbitmq/startup_{log, _err}

Sep 10 19:52:38 TestNode-a rabbitmq-server[27929]: rabbitmq-server.

Sep 10 19:52:38 TestNode-a audispd[520]: node=TestNode-a type=SERVICE_START msg=audit(1473537158.696:3199): pid=1 uid=0 auid=42949672

Sep 10 19:52:38 TestNode-a systemd[1]: rabbitmq-server.service: control process exited, code=exited status=1

Sep 10 19:52:38 TestNode-a systemd[1]: Failed to start LSB: Enable AMQP service provided by RabbitMQ broker.

-- Subject: Unit rabbitmq-server.service has failed

-- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- Unit rabbitmq-server.service has failed.

--

-- The result is failed.

Sep 10 19:52:38 TestNode-a systemd[1]: Unit rabbitmq-server.service entered failed state.

Sep 10 19:52:38 TestNode-a systemd[1]: rabbitmq-server.service failed.

# ls -ltr /var/log/rabbitmq/

total 8

-rw-r----- 1 root root 79 Sep 10 19:52 startup_err

-rw-r----- 1 root root  9 Sep 10 19:52 startup_log

<TestNode-a:root>/root:

# cat /var/log/rabbitmq/startup_err

su: cannot open session: Cannot make/remove an entry for the specified session

<TestNode-a:root>/root:

# cat /var/log/rabbitmq/startup_log

 

 

[Michael Klishin]

RabbitMQ 3.6.1 RPM package doesn't have systemd support. Starting with 3.6.6 there will be a separate package for CentOS 7.

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[odu...@hawk.iit.edu]

Thanks for responding to my query.

Do you know when 3.6.6 might be available?

[Michael Klishin]

In a week or two. 

> > /root:
> > # systemctl start rabbitmq-server.service
> >
> > Job for rabbitmq-server.service failed because the control process exited
> > with error code. See "systemctl status rabbitmq-server.service" and "j
> > ournalctl -xe" for details.
> >
> >

> > /root:
> > # cat /var/log/rabbitmq/startup_err
> >
> > su: cannot open session: Cannot make/remove an entry for the specified
> > session
> >

> > /root:
> > # cat /var/log/rabbitmq/startup_log
> >
> >
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "rabbitmq-users" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to rabbitmq-user...@googlegroups.com .
> > To post to this group, send email to rabbitm...@googlegroups.com
> > .
> > For more options, visit https://groups.google.com/d/optout.
> >
> >
>
> --
> You received this message because you are subscribed to the Google Groups "rabbitmq-users"
> group.
> To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.

> To post to this group, send an email to rabbitm...@googlegroups.com.

> For more options, visit https://groups.google.com/d/optout.
>

--
MK

Staff Software Engineer, Pivotal/RabbitMQ

[Honghao Sun]

Hi Michael,

systemd should be back-compatible with init.d, 

1. could you please let me know what's the changes between 3.6.6 for centos7 and centos6 packages with regard to systemd?

2. do we have a workaround or something to let rabbitmq 3.6.1 running centos 7?

Thanks.

Regards,

Joey

[Michael Klishin]

systemd is definitely not backwards compatible with init.d because packages must

provide a separate set of scripts/metadata.

See https://github.com/rabbitmq/rabbitmq-server/pull/913. The only workaround is to build

your own RPM package.

To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.