https://bugzilla.redhat.com/show_bug.cgi?id=1148604
Bug ID: 1148604 Summary: rabbitmq-server does not start due to missing symbols Product: Fedora Version: 21 Component: rabbitmq-server Assignee: lemenkov@gmail.com Reporter: lars@redhat.com QA Contact: extras-qa@fedoraproject.org CC: erlang@lists.fedoraproject.org, hubert.plociniczak@gmail.com, jeckersb@redhat.com, lemenkov@gmail.com, rjones@redhat.com, s@shk.io
Trying to start rabbitmq-server (rabbitmq-server-3.1.5-9.fc21.noarch) yields the following:
# /sbin/service rabbitmq-server start Redirecting to /bin/systemctl start rabbitmq-server.service Job for rabbitmq-server.service failed. See 'systemctl status rabbitmq-server.service' and 'journalctl -xn' for details.
Running "journalctl -u rabbitmq-server" yields:
Oct 01 20:16:53 f21-os-test systemd[1]: Starting RabbitMQ broker... Oct 01 20:16:53 f21-os-test systemd[1]: rabbitmq-server.service: Got notification message from PID 14545, but reception only permitted for main PID 14532 Oct 01 20:16:53 f21-os-test systemd[1]: rabbitmq-server.service: Got notification message from PID 14547, but reception only permitted for main PID 14532 Oct 01 20:16:53 f21-os-test systemd[1]: rabbitmq-server.service: Got notification message from PID 14571, but reception only permitted for main PID 14532 Oct 01 20:16:53 f21-os-test systemd[1]: rabbitmq-server.service: Got notification message from PID 14572, but reception only permitted for main PID 14532 Oct 01 20:16:54 f21-os-test rabbitmq-server[14532]: RabbitMQ 3.1.5. Copyright (C) 2007-2013 GoPivotal, Inc. Oct 01 20:16:54 f21-os-test rabbitmq-server[14532]: ## ## Licensed under the MPL. See http://www.rabbitmq.com/ Oct 01 20:16:54 f21-os-test rabbitmq-server[14532]: ## ## Oct 01 20:16:54 f21-os-test rabbitmq-server[14532]: ########## Logs: /var/log/rabbitmq/rabbit@f21-os-test.log Oct 01 20:16:54 f21-os-test rabbitmq-server[14532]: ###### ## /var/log/rabbitmq/rabbit@f21-os-test-sasl.log Oct 01 20:16:54 f21-os-test rabbitmq-server[14532]: ########## Oct 01 20:16:55 f21-os-test rabbitmq-server[14532]: Starting broker... completed with 0 plugins. Oct 01 20:18:23 f21-os-test systemd[1]: rabbitmq-server.service start operation timed out. Terminating. Oct 01 20:18:23 f21-os-test systemd[1]: Failed to start RabbitMQ broker. Oct 01 20:18:23 f21-os-test systemd[1]: Unit rabbitmq-server.service entered failed state.
/var/log/rabbitmq/hostname.log contains:
=INFO REPORT==== 1-Oct-2014::20:16:54 === Starting RabbitMQ 3.1.5 on Erlang 17 Copyright (C) 2007-2013 GoPivotal, Inc. Licensed under the MPL. See http://www.rabbitmq.com/
=INFO REPORT==== 1-Oct-2014::20:16:54 === node : rabbit@f21-os-test home dir : /var/lib/rabbitmq cookie hash : PZPVSneawENzOO4Ft5aeuA== log : /var/log/rabbitmq/rabbit@f21-os-test.log sasl log : /var/log/rabbitmq/rabbit@f21-os-test-sasl.log database dir : /var/lib/rabbitmq/mnesia/rabbit@f21-os-test
=INFO REPORT==== 1-Oct-2014::20:16:55 === Limiting to approx 924 file handles (829 sockets)
=INFO REPORT==== 1-Oct-2014::20:16:55 === Memory limit set to 1581MB of 3953MB total.
=INFO REPORT==== 1-Oct-2014::20:16:55 === Disk free limit set to 1000MB
=INFO REPORT==== 1-Oct-2014::20:16:55 === msg_store_transient: using rabbit_msg_store_ets_index to provide index
=INFO REPORT==== 1-Oct-2014::20:16:55 === msg_store_persistent: using rabbit_msg_store_ets_index to provide index
=WARNING REPORT==== 1-Oct-2014::20:16:55 === msg_store_persistent: rebuilding indices from scratch
=INFO REPORT==== 1-Oct-2014::20:16:55 === started TCP Listener on [::]:5672
=WARNING REPORT==== 1-Oct-2014::20:16:55 === The on_load function for module sd_notify returned {error, {load_failed, "Failed to load NIF library: '/usr/lib64/erlang/lib/sd_notify-0.1/priv/sd_notify_drv.so: undefined symbol: sd_notify'"}}
=INFO REPORT==== 1-Oct-2014::20:16:55 === Server startup complete; 0 plugins started.
https://bugzilla.redhat.com/show_bug.cgi?id=1148604
--- Comment #1 from John Eckersberg jeckersb@redhat.com --- I think possibly erlang-sd_notify needs rebuilt in rawhide following the most recent erlang rebase?
https://bugzilla.redhat.com/show_bug.cgi?id=1148604
John Eckersberg jeckersb@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Component|rabbitmq-server |erlang-sd_notify Assignee|lemenkov@gmail.com |jeckersb@redhat.com
--- Comment #2 from John Eckersberg jeckersb@redhat.com --- OK, what really is happening is that the sd_notify_drv.so is not linked against libsystem-daemon. This used to work previously because something else in the erlang runtime was linked against libsystemd-daemon, so the symbol was already mapped into the process and loading the sd_notify module would work.
However the newer erlang builds don't link with libsystemd-daemon necessarily, which is what happens here.
I'm updating erlang-sd_notify to explicitly carry that link-time dependency.
https://bugzilla.redhat.com/show_bug.cgi?id=1148604
--- Comment #3 from Peter Lemenkov lemenkov@gmail.com --- (In reply to John Eckersberg from comment #2)
OK, what really is happening is that the sd_notify_drv.so is not linked against libsystem-daemon. This used to work previously because something else in the erlang runtime was linked against libsystemd-daemon, so the symbol was already mapped into the process and loading the sd_notify module would work.
However the newer erlang builds don't link with libsystemd-daemon necessarily, which is what happens here.
I'm updating erlang-sd_notify to explicitly carry that link-time dependency.
John, thanks for digging into this. I added you as a co-maintainers. Looks like this change was related to a recent libsystemd-daemon.so -> libsystemd.so change (see this #1125105).
https://bugzilla.redhat.com/show_bug.cgi?id=1148604
--- Comment #4 from Peter Lemenkov lemenkov@gmail.com --- (In reply to John Eckersberg from comment #2)
OK, what really is happening is that the sd_notify_drv.so is not linked against libsystem-daemon. This used to work previously because something else in the erlang runtime was linked against libsystemd-daemon, so the symbol was already mapped into the process and loading the sd_notify module would work.
However the newer erlang builds don't link with libsystemd-daemon necessarily, which is what happens here.
I'm updating erlang-sd_notify to explicitly carry that link-time dependency.
Sadly but Ive made a mistake. I didn't even used -lsystemd while building:
https://github.com/lemenkov/erlang-sd_notify
In fact this was just a coincidence that my code is worked somehow (erlang already mapped some systemd functions as you found out). In order to fix this I believe that erlang-sd_notify requires rebar.config file with something like this:
https://github.com/basho/ebloom/blob/develop/rebar.config
This would tell rebar what libraries should this application be linked against. Also it's possible to setup some other variables here (CFLAGS, CXXFLAGS, etc).
https://bugzilla.redhat.com/show_bug.cgi?id=1148604
--- Comment #5 from John Eckersberg jeckersb@redhat.com --- The patch I pushed into git a moment ago just sets LDFLAGS=-lsystemd when invoking rebar in the spec.
https://bugzilla.redhat.com/show_bug.cgi?id=1148604
--- Comment #6 from Peter Lemenkov lemenkov@gmail.com --- (In reply to John Eckersberg from comment #5)
The patch I pushed into git a moment ago just sets LDFLAGS=-lsystemd when invoking rebar in the spec.
Looks good to me. Don't forget to merge in into f21.
https://bugzilla.redhat.com/show_bug.cgi?id=1148604
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |MODIFIED
https://bugzilla.redhat.com/show_bug.cgi?id=1148604
--- Comment #7 from Fedora Update System updates@fedoraproject.org --- erlang-sd_notify-0.1-4.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/erlang-sd_notify-0.1-4.fc21
https://bugzilla.redhat.com/show_bug.cgi?id=1148604
Dusty Mabe dustymabe@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dustymabe@redhat.com
--- Comment #8 from Dusty Mabe dustymabe@redhat.com ---
As a workaround you can use the following:
# If erlang-sd_notify-0.1-4 is in the repos then use that.. # If not install directly from koji # NOTE: the link is for x86_64 rpm
yum install -y erlang-sd_notify-0.1-4 || yum install http://kojipkgs.fedoraproject.org/packages/erlang-sd_notify/0.1/4.fc21/data/...
https://bugzilla.redhat.com/show_bug.cgi?id=1148604
--- Comment #9 from Dusty Mabe dustymabe@redhat.com --- Just a thought here. Should rabbitmq-server be updated to require erlang-sd_notify >= 0.1-4 ?
https://bugzilla.redhat.com/show_bug.cgi?id=1148604
--- Comment #10 from John Eckersberg jeckersb@redhat.com --- (In reply to Dusty Mabe from comment #9)
Just a thought here. Should rabbitmq-server be updated to require erlang-sd_notify >= 0.1-4 ?
I don't think so. If a user is going to update rabbitmq-server, they'll most likely get it by running "yum update", which would also pull in the updated erlang-sd_notify. Also, rabbitmq-server can function correctly even with erlang-sd_notify=0.1.3, as long as an older version of erlang is used.
https://bugzilla.redhat.com/show_bug.cgi?id=1148604
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|MODIFIED |ON_QA
--- Comment #11 from Fedora Update System updates@fedoraproject.org --- Package erlang-sd_notify-0.1-4.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing erlang-sd_notify-0.1-4.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-11943/erlang-sd_notify-0... then log in and leave karma (feedback).
https://bugzilla.redhat.com/show_bug.cgi?id=1148604
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |CLOSED Fixed In Version| |erlang-sd_notify-0.1-4.fc21 Resolution|--- |ERRATA Last Closed| |2014-11-01 12:55:10
--- Comment #12 from Fedora Update System updates@fedoraproject.org --- erlang-sd_notify-0.1-4.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
https://bugzilla.redhat.com/show_bug.cgi?id=1148604
Matthias Saou matthias@saou.eu changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |matthias@saou.eu
--- Comment #13 from Matthias Saou matthias@saou.eu --- Quick note in case anyone bumps into this and finds this report : On RHEL7 the "-lsystemd" doesn't work, that library isn't found. With "-lsystemd-daemon" the packages rebuild and work fine.
erlang@lists.fedoraproject.org
-
Red Hat Bugzilla