Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1324488 - rabbitmq-server unable to start due to /usr/lib/rabbitmq/bin/ being missing in 3.6.1-1
Summary: rabbitmq-server unable to start due to /usr/lib/rabbitmq/bin/ being missing i...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rabbitmq-server
Version: 23
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Peter Lemenkov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-06 13:04 UTC by Lee Yarwood
Modified: 2016-04-12 09:40 UTC (History)
8 users (show)

Fixed In Version: rabbitmq-server-3.6.1-2.fc23 rabbitmq-server-3.6.1-2.fc24
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-08 15:50:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Lee Yarwood 2016-04-06 13:04:57 UTC
Description of problem:

# rpm -qi rabbitmq-server
Name        : rabbitmq-server
Version     : 3.6.1
Release     : 1.fc23
Architecture: noarch
Install Date: Tue 05 Apr 2016 06:48:32 AM EDT
Group       : Development/Libraries
Size        : 5686669
License     : MPLv1.1
Signature   : RSA/SHA256, Thu 24 Mar 2016 04:17:59 PM EDT, Key ID 32474cf834ec9cba
Source RPM  : rabbitmq-server-3.6.1-1.fc23.src.rpm
Build Date  : Thu 24 Mar 2016 03:46:27 PM EDT
Build Host  : buildvm-15.phx2.fedoraproject.org
Relocations : (not relocatable)
Packager    : Fedora Project
Vendor      : Fedora Project
URL         : http://www.rabbitmq.com/
Summary     : The RabbitMQ server
Description :
RabbitMQ is an implementation of AMQP, the emerging standard for high
performance enterprise messaging. The RabbitMQ server is a robust and
scalable implementation of an AMQP broker.

# ll /usr/lib/rabbitmq/bin/
ls: cannot access /usr/lib/rabbitmq/bin/: No such file or directory
# systemctl status rabbitmq-server
● rabbitmq-server.service - RabbitMQ broker
   Loaded: loaded (/usr/lib/systemd/system/rabbitmq-server.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Wed 2016-04-06 09:03:33 EDT; 2s ago
  Process: 6146 ExecStop=/usr/lib/rabbitmq/bin/rabbitmqctl stop (code=exited, status=203/EXEC)
  Process: 6142 ExecStart=/usr/lib/rabbitmq/bin/rabbitmq-server (code=exited, status=203/EXEC)
 Main PID: 6142 (code=exited, status=203/EXEC)

Apr 06 09:03:33 stable-devices.example.com systemd[1]: Starting RabbitMQ broker...
Apr 06 09:03:33 stable-devices.example.com systemd[1]: rabbitmq-server.service: Main process exited, code=exited, status=203/EXEC
Apr 06 09:03:33 stable-devices.example.com systemd[6146]: rabbitmq-server.service: Failed at step EXEC spawning /usr/lib/rabbitmq/bin/rabbitmqctl: No such file or directory
Apr 06 09:03:33 stable-devices.example.com systemd[1]: rabbitmq-server.service: Control process exited, code=exited status=203
Apr 06 09:03:33 stable-devices.example.com systemd[1]: Failed to start RabbitMQ broker.
Apr 06 09:03:33 stable-devices.example.com systemd[1]: rabbitmq-server.service: Unit entered failed state.
Apr 06 09:03:33 stable-devices.example.com systemd[1]: rabbitmq-server.service: Failed with result 'exit-code'.


# dnf downgrade rabbitmq-server -y
[..]
# ll /usr/lib/rabbitmq/bin/
total 0
lrwxrwxrwx. 1 root root 45 Sep  3  2015 rabbitmqctl -> ../lib/rabbitmq_server-3.5.4/sbin/rabbitmqctl
lrwxrwxrwx. 1 root root 51 Sep  3  2015 rabbitmq-defaults -> ../lib/rabbitmq_server-3.5.4/sbin/rabbitmq-defaults
lrwxrwxrwx. 1 root root 46 Sep  3  2015 rabbitmq-env -> ../lib/rabbitmq_server-3.5.4/sbin/rabbitmq-env
lrwxrwxrwx. 1 root root 50 Sep  3  2015 rabbitmq-plugins -> ../lib/rabbitmq_server-3.5.4/sbin/rabbitmq-plugins
lrwxrwxrwx. 1 root root 49 Sep  3  2015 rabbitmq-server -> ../lib/rabbitmq_server-3.5.4/sbin/rabbitmq-server


# systemctl restart rabbitmq-server
# systemctl status rabbitmq-server
● rabbitmq-server.service - RabbitMQ broker
   Loaded: loaded (/usr/lib/systemd/system/rabbitmq-server.service; disabled; vendor preset: disabled)
   Active: active (running) since Wed 2016-04-06 09:04:14 EDT; 6s ago
 Main PID: 6407 (beam.smp)
   CGroup: /system.slice/rabbitmq-server.service
           ├─6407 /usr/lib64/erlang/erts-6.3/bin/beam.smp -W w -A 64 -P 1048576 -K true -- -root /usr/lib64/erlang -progname erl -- -home /var/lib/rabbitmq -- -pa /usr/lib/rabbitmq/lib/rabbitmq_server-3.5.4/sbin/../ebin -noshell -noinput -s rabbit boot -sname rabbit@st...
           ├─6545 inet_gethost 4
           └─6546 inet_gethost 4

Apr 06 09:04:13 stable-devices.example.com systemd[1]: rabbitmq-server.service: Got notification message from PID 6467, but reception only permitted for main PID 6407
Apr 06 09:04:13 stable-devices.example.com systemd[1]: rabbitmq-server.service: Got notification message from PID 6468, but reception only permitted for main PID 6407
Apr 06 09:04:13 stable-devices.example.com rabbitmq-server[6407]: RabbitMQ 3.5.4. Copyright (C) 2007-2015 Pivotal Software, Inc.
Apr 06 09:04:13 stable-devices.example.com rabbitmq-server[6407]: ##  ##      Licensed under the MPL.  See http://www.rabbitmq.com/
Apr 06 09:04:13 stable-devices.example.com rabbitmq-server[6407]: ##  ##
Apr 06 09:04:13 stable-devices.example.com rabbitmq-server[6407]: ##########  Logs: /var/log/rabbitmq/rabbit
Apr 06 09:04:13 stable-devices.example.com rabbitmq-server[6407]: ######  ##        /var/log/rabbitmq/rabbit
Apr 06 09:04:13 stable-devices.example.com rabbitmq-server[6407]: ##########
Apr 06 09:04:14 stable-devices.example.com systemd[1]: Started RabbitMQ broker.
Apr 06 09:04:14 stable-devices.example.com rabbitmq-server[6407]: Starting broker... completed with 0 plugins.

Version-Release number of selected component (if applicable):
rabbitmq-server-3.6.1-1.fc23.noarch

How reproducible:
Always

Steps to Reproduce:
1. Install rabbitmq-server-3.6.1-1.fc23.noarch
2. Try to start the rabbitmq-server service

Actual results:
rabbitmq-server service fails as  /usr/lib/rabbitmq/bin/ and the various symlinks within it are missing.

Expected results:
rabbitmq-server is able to start.

Additional info:
http://pkgs.fedoraproject.org/cgit/rpms/rabbitmq-server.git/commit/?h=f23&id=021856d323764f4cb16a4f7c38068c7995733f9d

Comment 1 Fedora Update System 2016-04-06 14:48:16 UTC
rabbitmq-server-3.6.1-2.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-30fd051fe6

Comment 2 Fedora Update System 2016-04-06 14:48:29 UTC
rabbitmq-server-3.6.1-2.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-e11ed0dea9

Comment 3 Fedora Update System 2016-04-07 16:54:04 UTC
rabbitmq-server-3.6.1-2.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-e11ed0dea9

Comment 4 Fedora Update System 2016-04-07 21:19:37 UTC
rabbitmq-server-3.6.1-2.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-30fd051fe6

Comment 5 Fedora Update System 2016-04-08 15:50:18 UTC
rabbitmq-server-3.6.1-2.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.

Comment 6 Fedora Update System 2016-04-12 09:40:18 UTC
rabbitmq-server-3.6.1-2.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.