rabbitmq-server can not start on rhel 7.0

[xuga...@cn.ibm.com]

Hi all,

I am new to rabbitmq.

We project used erlang R16B03 and RabbitMQ 3.3.4 on rhel 6.5 in the past.
They worked very well.

Now due to our OS changed to rhel 7.0, we found our rabbitmq-server can not be started

It always report timeout. I did not know how to debug.

Could you support?

Thanks!

Below is some system info here

[root@localhost rabbitmq]# uname -a
Linux localhost 3.10.0-123.el7.x86_64 #1 SMP Mon May 5 11:16:57 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux

[root@localhost rabbitmq]# hostname
localhost
[root@localhost rabbitmq]# rpm -qa | grep kernel
kernel-tools-3.10.0-123.9.3.el7.x86_64
kernel-3.10.0-123.el7.x86_64
kernel-3.10.0-123.9.3.el7.x86_64
kernel-tools-libs-3.10.0-123.9.3.el7.x86_64

[root@localhost rabbitmq]# rpm -qa | grep erlang
erlang-tools-R16B-03.2.ibm.el7.x86_64
erlang-dialyzer-R16B-03.2.ibm.el7.x86_64
erlang-stdlib-R16B-03.2.ibm.el7.x86_64
erlang-asn1-R16B-03.2.ibm.el7.x86_64
erlang-cosProperty-R16B-03.2.ibm.el7.x86_64
erlang-percept-R16B-03.2.ibm.el7.x86_64
erlang-erl_interface-R16B-03.2.ibm.el7.x86_64
erlang-et-R16B-03.2.ibm.el7.x86_64
erlang-sasl-R16B-03.2.ibm.el7.x86_64
erlang-os_mon-R16B-03.2.ibm.el7.x86_64
erlang-typer-R16B-03.2.ibm.el7.x86_64
erlang-crypto-R16B-03.2.ibm.el7.x86_64
erlang-hipe-R16B-03.2.ibm.el7.x86_64
erlang-xmerl-R16B-03.2.ibm.el7.x86_64
erlang-inets-R16B-03.2.ibm.el7.x86_64
erlang-cosNotification-R16B-03.2.ibm.el7.x86_64
erlang-otp_mibs-R16B-03.2.ibm.el7.x86_64
erlang-cosTransactions-R16B-03.2.ibm.el7.x86_64
erlang-ic-R16B-03.2.ibm.el7.x86_64
erlang-jinterface-R16B-03.2.ibm.el7.x86_64
erlang-pman-R16B-03.2.ibm.el7.x86_64
erlang-webtool-R16B-03.2.ibm.el7.x86_64
erlang-test_server-R16B-03.2.ibm.el7.x86_64
erlang-megaco-R16B-03.2.ibm.el7.x86_64
erlang-examples-R16B-03.2.ibm.el7.x86_64
erlang-kernel-R16B-03.2.ibm.el7.x86_64
erlang-compiler-R16B-03.2.ibm.el7.x86_64
erlang-snmp-R16B-03.2.ibm.el7.x86_64
erlang-ssl-R16B-03.2.ibm.el7.x86_64
erlang-cosTime-R16B-03.2.ibm.el7.x86_64
erlang-ssh-R16B-03.2.ibm.el7.x86_64
erlang-cosEventDomain-R16B-03.2.ibm.el7.x86_64
erlang-eldap-R16B-03.2.ibm.el7.x86_64
erlang-parsetools-R16B-03.2.ibm.el7.x86_64
erlang-gs-R16B-03.2.ibm.el7.x86_64
erlang-toolbar-R16B-03.2.ibm.el7.x86_64
erlang-wx-R16B-03.2.ibm.el7.x86_64
erlang-observer-R16B-03.2.ibm.el7.x86_64
erlang-common_test-R16B-03.2.ibm.el7.x86_64
erlang-R16B-03.2.ibm.el7.x86_64
erlang-erts-R16B-03.2.ibm.el7.x86_64
erlang-syntax_tools-R16B-03.2.ibm.el7.x86_64
erlang-runtime_tools-R16B-03.2.ibm.el7.x86_64
erlang-public_key-R16B-03.2.ibm.el7.x86_64
erlang-cosEvent-R16B-03.2.ibm.el7.x86_64
erlang-edoc-R16B-03.2.ibm.el7.x86_64
erlang-cosFileTransfer-R16B-03.2.ibm.el7.x86_64
erlang-diameter-R16B-03.2.ibm.el7.x86_64
erlang-eunit-R16B-03.2.ibm.el7.x86_64
erlang-appmon-R16B-03.2.ibm.el7.x86_64
erlang-debugger-R16B-03.2.ibm.el7.x86_64
erlang-reltool-R16B-03.2.ibm.el7.x86_64
erlang-mnesia-R16B-03.2.ibm.el7.x86_64
erlang-orber-R16B-03.2.ibm.el7.x86_64
erlang-erl_docgen-R16B-03.2.ibm.el7.x86_64
erlang-odbc-R16B-03.2.ibm.el7.x86_64
erlang-tv-R16B-03.2.ibm.el7.x86_64

[root@localhost rabbitmq]# rpm -qa | grep rabbitmq
rabbitmq-server-3.3.4-2.ibm.el7.noarch

[root@localhost ~]# systemctl status rabbitmq-server.service
rabbitmq-server.service - RabbitMQ broker
   Loaded: loaded (/usr/lib/systemd/system/rabbitmq-server.service; enabled)
   Active: failed (Result: timeout) since Wed 2014-11-12 01:28:08 CST; 12min ago
  Process: 3218 ExecStartPre=/bin/sh -c /usr/lib/rabbitmq/bin/rabbitmqctl status > /dev/null 2>&1 (code=exited, status=2)
 Main PID: 3258
   CGroup: /system.slice/rabbitmq-server.service

Nov 12 01:26:39 localhost rabbitmq-server[3258]: RabbitMQ 3.3.4. Copyright (C) 2007-2014 GoPivotal, Inc.
Nov 12 01:26:39 localhost rabbitmq-server[3258]: ##  ##      Licensed under the MPL.  See http://www.rabbitmq.com/
Nov 12 01:26:39 localhost rabbitmq-server[3258]: ##  ##
Nov 12 01:26:39 localhost rabbitmq-server[3258]: ##########  Logs: /var/log/rabbitmq/rab...@localhost.log
Nov 12 01:26:39 localhost rabbitmq-server[3258]: ######  ##        /var/log/rabbitmq/rab...@localhost-sasl.log
Nov 12 01:26:39 localhost rabbitmq-server[3258]: ##########
Nov 12 01:26:40 localhost rabbitmq-server[3258]: Starting broker... completed with 7 plugins.
Nov 12 01:28:08 localhost systemd[1]: rabbitmq-server.service operation timed out. Terminating.
Nov 12 01:28:08 localhost systemd[1]: Failed to start RabbitMQ broker.
Nov 12 01:28:08 localhost systemd[1]: Unit rabbitmq-server.service entered failed state.

[root@localhost ~]# systemctl start rabbitmq-server.service
Job for rabbitmq-server.service failed. See 'systemctl status rabbitmq-server.service' and 'journalctl -xn' for details.

[root@localhost ~]# journalctl -xn
-- Logs begin at Wed 2014-11-12 01:23:13 CST, end at Wed 2014-11-12 01:47:08 CST. --
Nov 12 01:47:05 localhost systemd[1]: Cannot find unit for notify message of PID 4188.
Nov 12 01:47:05 localhost systemd[1]: rabbitmq-server.service: Got notification message from PID 4189, but reception only permitted for PID 414
Nov 12 01:47:05 localhost systemd[1]: rabbitmq-server.service: Got notification message from PID 4190, but reception only permitted for PID 414
Nov 12 01:47:07 localhost rabbitmq-server[4141]: RabbitMQ 3.3.4. Copyright (C) 2007-2014 GoPivotal, Inc.
Nov 12 01:47:07 localhost rabbitmq-server[4141]: ##  ##      Licensed under the MPL.  See http://www.rabbitmq.com/
Nov 12 01:47:07 localhost rabbitmq-server[4141]: ##  ##
Nov 12 01:47:07 localhost rabbitmq-server[4141]: ##########  Logs: /var/log/rabbitmq/rab...@localhost.log
Nov 12 01:47:07 localhost rabbitmq-server[4141]: ######  ##        /var/log/rabbitmq/rab...@localhost-sasl.log
Nov 12 01:47:07 localhost rabbitmq-server[4141]: ##########
Nov 12 01:47:08 localhost rabbitmq-server[4141]: Starting broker... completed with 7 plugins

Below is some log form /var/log/rabbitmq/

=INFO REPORT==== 12-Nov-2014::02:25:02 ===
Starting RabbitMQ 3.3.4 on Erlang R16B03-1
Copyright (C) 2007-2014 GoPivotal, Inc.
Licensed under the MPL.  See http://www.rabbitmq.com/

=INFO REPORT==== 12-Nov-2014::02:25:02 ===
node           : rabbit@localhost
home dir       : /var/lib/rabbitmq
config file(s) : /etc/rabbitmq/rabbitmq.config
cookie hash    : aebDquuyU6K+hG/0e8kZgQ==
log            : /var/log/rabbitmq/rab...@localhost.log
sasl log       : /var/log/rabbitmq/rab...@localhost-sasl.log
database dir   : /var/lib/rabbitmq/mnesia/rabbit@localhost

=INFO REPORT==== 12-Nov-2014::02:25:02 ===
Limiting to approx 924 file handles (829 sockets)

=INFO REPORT==== 12-Nov-2014::02:25:02 ===
Memory limit set to 2916MB of 7292MB total.

=INFO REPORT==== 12-Nov-2014::02:25:02 ===
Disk free limit set to 50MB

=INFO REPORT==== 12-Nov-2014::02:25:02 ===
msg_store_transient: using rabbit_msg_store_ets_index to provide index

=INFO REPORT==== 12-Nov-2014::02:25:02 ===
msg_store_persistent: using rabbit_msg_store_ets_index to provide index

=WARNING REPORT==== 12-Nov-2014::02:25:02 ===
msg_store_persistent: rebuilding indices from scratch

=INFO REPORT==== 12-Nov-2014::02:25:03 ===
started TCP Listener on 9.123.105.137:5672

=INFO REPORT==== 12-Nov-2014::02:25:03 ===
started SSL Listener on [::]:5671

=INFO REPORT==== 12-Nov-2014::02:25:03 ===
Management plugin started. Port: 15672

=INFO REPORT==== 12-Nov-2014::02:25:03 ===
Statistics database started.

=INFO REPORT==== 12-Nov-2014::02:25:03 ===
Server startup complete; 7 plugins started.
 * amqp_client
 * mochiweb
 * rabbitmq_management
 * rabbitmq_management_agent
 * rabbitmq_management_visualiser
 * rabbitmq_web_dispatch
 * webmachine

[Michael Klishin]

On 12 November 2014 at 11:32:58, xuga...@cn.ibm.com (xuga...@cn.ibm.com) wrote:
> Nov 12 01:47:05 localhost systemd[1]: Cannot find unit for
> notify message of PID 4188.
> Nov 12 01:47:05 localhost systemd[1]: rabbitmq-server.service:
> Got notification message from PID 4189, but reception only permitted
> for PID 414
> Nov 12 01:47:05 localhost systemd[1]: rabbitmq-server.service:
> Got notification message from PID 4190, but reception only permitted
> for PID 414

These seem suspicious as other logs indicate that RabbitMQ did start and bind to
ports 5672, 5671, 15672.

A quick search brings up
https://bugzilla.redhat.com/show_bug.cgi?id=1047304

and

https://bugzilla.redhat.com/show_bug.cgi?id=1104193#c6

In the latter case, re-trying the operation may be sufficient.
--
MK

Staff Software Engineer, Pivotal/RabbitMQ

[Peter Lemenkov]

Hello All!

2014-11-12 11:32 GMT+03:00 <xuga...@cn.ibm.com>:

> [root@localhost rabbitmq]# rpm -qa | grep erlang

> erlang-R16B-03.2.ibm.el7.x86_64

...

> [root@localhost rabbitmq]# rpm -qa | grep rabbitmq
> rabbitmq-server-3.3.4-2.ibm.el7.noarch
>
> [root@localhost ~]# systemctl status rabbitmq-server.service
> rabbitmq-server.service - RabbitMQ broker
> Loaded: loaded (/usr/lib/systemd/system/rabbitmq-server.service; enabled)
> Active: failed (Result: timeout) since Wed 2014-11-12 01:28:08 CST; 12min
> ago
> Process: 3218 ExecStartPre=/bin/sh -c /usr/lib/rabbitmq/bin/rabbitmqctl
> status > /dev/null 2>&1 (code=exited, status=2)

I see you're using an outdated package. We've added a lot of new great
stuff into Erlang package since R16B-03.2 build (namely we started
adding system socket activation since erlang-R16B-03.3).

Please rebase your work on top of (at least) erlang-R16B-03.7 and
RabbitMQ from Fedora Rawhide. This should work with systemd much more
reliable than before.

* http://mirror.yandex.ru/epel/7/SRPMS/e/erlang-R16B-03.7.el7.src.rpm
* http://mirror.yandex.ru/fedora/linux/development/rawhide/source/SRPMS/r/rabbitmq-server-3.4.1-1.fc22.src.rpm


--
With best regards, Peter Lemenkov.

[Gang U Xu]

Hi

My systemd version is below
Installed Packages
systemd.x86_64                                               208-11.el7_0.4                                               @rhel-x86_64-server-7
Available Packages
systemd.x86_64                                               208-11.el7                                                   rhel-x86_64-server-7
systemd.x86_64                                               208-11.el7_0.2                                               rhel-x86_64-server-7
systemd.x86_64                                               208-11.el7_0.4                                               rhel-x86_64-server-7

Seemed this one is the latest one I can find.

I tried use R16B03 from epel and rabbitmq-server 3.1.5 from epel too.

They worked well too.

erlang-R16B-03.7.el7.x86_64

http://ftp.sjtu.edu.cn/fedora/epel/7/x86_64/r/rabbitmq-server-3.1.5-7.el7.noarch.rpm

Is that mean the problem maybe not rabbitmq rpm package?

Thanks!

[Gang U Xu]

Hi,

Really thanks your info.

I have one simple question,

As I can not find root cause, I used to install erlang and rabbitmq from epel on our another rhel 7.0
But they worked well.

http://ftp.sjtu.edu.cn/fedora/epel/7/x86_64/

http://ftp.sjtu.edu.cn/fedora/epel/7/x86_64/e/erlang-R16B-03.7.el7.x86_64.rpm
http://ftp.sjtu.edu.cn/fedora/epel/7/x86_64/r/rabbitmq-server-3.1.5-7.el7.noarch.rpm

I will try to rebase our erlang and test again.
Thanks!

From:        Peter Lemenkov <leme...@gmail.com>
To:        Gang U Xu/China/IBM@IBMCN
Cc:        rabbitm...@googlegroups.com
Date:        2014/11/12 16:51
Subject:        Re: [rabbitmq-users] rabbitmq-server can not start on rhel 7.0

--
You received this message because you are subscribed to a topic in the Google Groups "rabbitmq-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/rabbitmq-users/EptsgSjFq7k/unsubscribe.
To unsubscribe from this group and all its topics, 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.

[xuga...@cn.ibm.com]

Hi Peter

I tried to build erlang on 17.3 and install it on rhel 7.0. Then install rabbitmq-server 3.3, still failed.

[root@localhost ~]# systemctl start rabbitmq-server.service
Job for rabbitmq-server.service failed. See 'systemctl status rabbitmq-server.service' and 'journalctl -xn' for details.

[root@localhost ~]# systemctl status rabbitmq-server.service
rabbitmq-server.service - RabbitMQ broker

   Loaded: loaded (/usr/lib/systemd/system/rabbitmq-server.service; disabled)
   Active: failed (Result: timeout) since Thu 2014-11-13 09:43:20 EST; 6s ago
 Main PID: 2580

Nov 13 09:41:54 localhost.localdomain rabbitmq-server[2580]: RabbitMQ 3.3.4. Copyright (C) 2007-2014 GoPivotal, Inc.
Nov 13 09:41:54 localhost.localdomain rabbitmq-server[2580]: ##  ##      Licensed under the MPL.  See http://www.rabbitmq.com/
Nov 13 09:41:54 localhost.localdomain rabbitmq-server[2580]: ##  ##
Nov 13 09:41:54 localhost.localdomain rabbitmq-server[2580]: ##########  Logs: /var/log/rabbitmq/rab...@localhost.log
Nov 13 09:41:54 localhost.localdomain rabbitmq-server[2580]: ######  ##        /var/log/rabbitmq/rab...@localhost-sasl.log
Nov 13 09:41:54 localhost.localdomain rabbitmq-server[2580]: ##########
Nov 13 09:41:55 localhost.localdomain rabbitmq-server[2580]: Starting broker... completed with 0 plugins.
Nov 13 09:43:20 localhost.localdomain systemd[1]: rabbitmq-server.service operation timed out. Terminating.
Nov 13 09:43:20 localhost.localdomain systemd[1]: Failed to start RabbitMQ broker.
Nov 13 09:43:20 localhost.localdomain systemd[1]: Unit rabbitmq-server.service entered failed state.

[root@localhost ~]# journalctl -xn

-- Logs begin at Thu 2014-11-13 09:37:50 EST, end at Thu 2014-11-13 09:43:20 EST. --
Nov 13 09:41:55 localhost.localdomain rabbitmq-server[2580]: Starting broker... completed with 0 plugins.
Nov 13 09:42:04 localhost.localdomain sshd[2681]: Accepted password for root from 9.111.30.197 port 55938 ssh2
Nov 13 09:42:04 localhost.localdomain systemd[1]: Starting Session 4 of user root.
-- Subject: Unit session-4.scope has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-4.scope has begun starting up.
Nov 13 09:42:04 localhost.localdomain systemd-logind[763]: New session 4 of user root.
-- Subject: A new session 4 has been created for user root
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
--
-- A new session with the ID 4 has been created for the user root.
--
-- The leading process of the session is 2681.
Nov 13 09:42:04 localhost.localdomain systemd[1]: Started Session 4 of user root.
-- Subject: Unit session-4.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-4.scope has finished starting up.
--
-- The start-up result is done.
Nov 13 09:42:04 localhost.localdomain systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument
Nov 13 09:42:04 localhost.localdomain sshd[2681]: pam_unix(sshd:session): session opened for user root by (uid=0)
Nov 13 09:43:20 localhost.localdomain systemd[1]: rabbitmq-server.service operation timed out. Terminating.
Nov 13 09:43:20 localhost.localdomain systemd[1]: Failed to start 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.
Nov 13 09:43:20 localhost.localdomain systemd[1]: Unit rabbitmq-server.service entered failed state.

But when I try to read /var/log/rabbitmq/*.log

[root@localhost rabbitmq]# more rab...@localhost.log. Seemed RabbitMq started, but with unkown problems,it failed to start finally.

=INFO REPORT==== 13-Nov-2014::09:41:54 ===
Starting RabbitMQ 3.3.4 on Erlang 17

Copyright (C) 2007-2014 GoPivotal, Inc.
Licensed under the MPL.  See http://www.rabbitmq.com/

=INFO REPORT==== 13-Nov-2014::09:41:54 ===

node           : rabbit@localhost
home dir       : /var/lib/rabbitmq

config file(s) : (none)
cookie hash    : 45uWwvaZ6oGe1mC1uY2hqg==

log            : /var/log/rabbitmq/rab...@localhost.log
sasl log       : /var/log/rabbitmq/rab...@localhost-sasl.log
database dir   : /var/lib/rabbitmq/mnesia/rabbit@localhost

=INFO REPORT==== 13-Nov-2014::09:41:55 ===

Limiting to approx 924 file handles (829 sockets)

=INFO REPORT==== 13-Nov-2014::09:41:55 ===
Memory limit set to 3000MB of 7500MB total.

=INFO REPORT==== 13-Nov-2014::09:41:55 ===

Disk free limit set to 50MB

=INFO REPORT==== 13-Nov-2014::09:41:55 ===
Adding vhost '/'

=INFO REPORT==== 13-Nov-2014::09:41:55 ===
Creating user 'guest'

=INFO REPORT==== 13-Nov-2014::09:41:55 ===
Setting user tags for user 'guest' to [administrator]

=INFO REPORT==== 13-Nov-2014::09:41:55 ===
Setting permissions for 'guest' in '/' to '.*', '.*', '.*'

=INFO REPORT==== 13-Nov-2014::09:41:55 ===

msg_store_transient: using rabbit_msg_store_ets_index to provide index

=INFO REPORT==== 13-Nov-2014::09:41:55 ===

msg_store_persistent: using rabbit_msg_store_ets_index to provide index

=WARNING REPORT==== 13-Nov-2014::09:41:55 ===

msg_store_persistent: rebuilding indices from scratch

=INFO REPORT==== 13-Nov-2014::09:41:55 ===
started TCP Listener on [::]:5672

=INFO REPORT==== 13-Nov-2014::09:41:55 ===
Server startup complete; 0 plugins started.

BTW, I use journalctl to output all log and found below info which I did not know if it is problem.

Nov 13 09:41:50 localhost.localdomain systemd[1]: Starting RabbitMQ broker...
Nov 13 09:41:51 localhost.localdomain systemd[1]: rabbitmq-server.service: Got notification message from PID 2593, but reception only permitted
 for PID 2580
Nov 13 09:41:51 localhost.localdomain systemd[1]: rabbitmq-server.service: Got notification message from PID 2594, but reception only permitted
 for PID 2580
Nov 13 09:41:51 localhost.localdomain systemd[1]: rabbitmq-server.service: Got notification message from PID 2595, but reception only permitted
 for PID 2580
Nov 13 09:41:52 localhost.localdomain systemd[1]: rabbitmq-server.service: Got notification message from PID 2623, but reception only permitted
 for PID 2580
Nov 13 09:41:52 localhost.localdomain systemd[1]: rabbitmq-server.service: Got notification message from PID 2624, but reception only permitted
 for PID 2580
Nov 13 09:41:52 localhost.localdomain systemd[1]: rabbitmq-server.service: Got notification message from PID 2625, but reception only permitted
 for PID 2580
Nov 13 09:41:54 localhost.localdomain rabbitmq-server[2580]: RabbitMQ 3.3.4. Copyright (C) 2007-2014 GoPivotal, Inc.
Nov 13 09:41:54 localhost.localdomain rabbitmq-server[2580]: ##  ##      Licensed under the MPL.  See http://www.rabbitmq.com/
Nov 13 09:41:54 localhost.localdomain rabbitmq-server[2580]: ##  ##
Nov 13 09:41:54 localhost.localdomain rabbitmq-server[2580]: ##########  Logs: /var/log/rabbitmq/rab...@localhost.log
Nov 13 09:41:54 localhost.localdomain rabbitmq-server[2580]: ######  ##        /var/log/rabbitmq/rab...@localhost-sasl.log
Nov 13 09:41:54 localhost.localdomain rabbitmq-server[2580]: ##########
Nov 13 09:41:55 localhost.localdomain rabbitmq-server[2580]: Starting broker... completed with 0 plugins.
Nov 13 09:42:04 localhost.localdomain sshd[2681]: Accepted password for root from 9.111.30.197 port 55938 ssh2
Nov 13 09:42:04 localhost.localdomain systemd[1]: Starting Session 4 of user root.
Nov 13 09:42:04 localhost.localdomain systemd-logind[763]: New session 4 of user root.
Nov 13 09:42:04 localhost.localdomain systemd[1]: Started Session 4 of user root.
Nov 13 09:42:04 localhost.localdomain systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument
Nov 13 09:42:04 localhost.localdomain sshd[2681]: pam_unix(sshd:session): session opened for user root by (uid=0)
Nov 13 09:43:20 localhost.localdomain systemd[1]: rabbitmq-server.service operation timed out. Terminating.
Nov 13 09:43:20 localhost.localdomain systemd[1]: Failed to start RabbitMQ broker.
Nov 13 09:43:20 localhost.localdomain systemd[1]: Unit rabbitmq-server.service entered failed state.

Is there any timeout settings or config not correct? Or any comments?

Thanks!

[Gang U Xu]

Hi Peter,

A good news that I can start rabbitmq-server on erlang 17.3 on rhel 7.0

Last question, I found in most spec for rabbitmq-server which need erlang-sd_notify
Is that running dep mandatory for rabbitmq-server?

Seemed not, as we can update our system unit file like below
[Service]
Type=simple

Ofcourse, if we add erlang-sd_notify in rabbitmq-server spec,
We have to update it to below
[Service]
Type=notify

I did not understand which is better.
Could you support?

Thanks!





From:        Peter Lemenkov <leme...@gmail.com>
To:        Gang U Xu/China/IBM@IBMCN
Cc:        rabbitm...@googlegroups.com
Date:        2014/11/12 16:51
Subject:        Re: [rabbitmq-users] rabbitmq-server can not start on rhel 7.0
Sent by:        rabbitm...@googlegroups.com

---

--
You received this message because you are subscribed to a topic in the Google Groups "rabbitmq-users" group.
To unsubscribe from this topic, visit

https://groups.google.com/d/topic/rabbitmq-users/EptsgSjFq7k/unsubscribe.

To unsubscribe from this group and all its topics, 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.

[Peter Lemenkov]

2014-11-14 6:23 GMT+03:00 Gang U Xu <xuga...@cn.ibm.com>:
>
> Hi Peter,
>
> A good news that I can start rabbitmq-server on erlang 17.3 on rhel 7.0

Great!

> Last question, I found in most spec for rabbitmq-server which need erlang-sd_notify
> Is that running dep mandatory for rabbitmq-server?
>
> Seemed not, as we can update our system unit file like below
> [Service]
> Type=simple
>
> Ofcourse, if we add erlang-sd_notify in rabbitmq-server spec,
> We have to update it to below
> [Service]
> Type=notify
>
> I did not understand which is better.
> Could you support?

If you use a packages from EPEL (not ones rebuilt by you and/or your
teammates) which are patched to support systemd then sd_notify package
will be installed automatically. In this case you have to use
Type=notify. Otherwise you must use Type=simple. But beware of some
hidden issues of SysV-scripts - you have to rearrange SysV-scripts
startup order manually.

If Type=simpe works for you then it's fine.