[Bug 1033305] New: rabbitmq-plugins is not in the default $PATH
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1033305
Bug ID: 1033305
Summary: rabbitmq-plugins is not in the default $PATH
Product: Fedora
Version: 19
Component: rabbitmq-server
Severity: low
Assignee: hubert.plociniczak(a)gmail.com
Reporter: johnhford(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org,
hubert.plociniczak(a)gmail.com, lemenkov(a)gmail.com
Description of problem:
This program is used to, for instance, enable the http management console. In
the homebrew distribution, it's available in the default path.
In fedora it's:
$ rpm -ql rabbitmq-server | grep bin/rabbitmq-plugins
/usr/lib/rabbitmq/bin/rabbitmq-plugins
/usr/lib/rabbitmq/lib/rabbitmq_server-3.1.5/sbin/rabbitmq-plugins
In the official distribution, it's in the default path:
$ curl -LO
http://www.rabbitmq.com/releases/rabbitmq-server/v3.2.1/rabbitmq-server-3...
$ rpm -qpl rabbitmq-server-3.2.1-1.noarch.rpm | grep bin/rabbitmq-plugin
warning: rabbitmq-server-3.2.1-1.noarch.rpm: Header V4 DSA/SHA1 Signature, key
ID 056e8e56: NOKEY
/usr/lib/rabbitmq/bin/rabbitmq-plugins
/usr/lib/rabbitmq/lib/rabbitmq_server-3.2.1/sbin/rabbitmq-plugins
/usr/sbin/rabbitmq-plugins
How reproducible:
100%
Steps to Reproduce:
1. install rabbitmq-server
2. try to run "sudo rabbitmq-plugins enable rabbitmq_management"
Actual results:
Program not found in $PATH.
Expected results:
Program found in $PATH and can be run
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 6 months
[Bug 1059028] New: rabbitmq restarts fail randomly
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1059028
Bug ID: 1059028
Summary: rabbitmq restarts fail randomly
Product: Fedora
Version: 20
Component: rabbitmq-server
Assignee: hubert.plociniczak(a)gmail.com
Reporter: imcleod(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org,
hubert.plociniczak(a)gmail.com, lemenkov(a)gmail.com,
skottler(a)redhat.com
Description of problem:
I originally encountered this issue when installing OpenStack via devstack but
have since been able to reproduce it by simply executing commands inside of a
fresh F20 install.
Version-Release number of selected component (if applicable):
rabbitmq-server-3.1.5-1.fc20.noarch
How reproducible:
Occurs regularly but not 100% of the time
Steps to Reproduce:
/sbin/service rabbitmq-server stop
/sbin/service rabbitmq-server start
rabbitmqctl change_password guest newpassword
Actual results:
About half the time, on a freshly installed F20, this will fail, claiming the
node cannot be contacted. A typical error message:
[root@cob-dell5 ~]# rabbitmqctl change_password guest ozrootpw
Changing password for user "guest" ...
Error: unable to connect to node 'rabbit@cob-dell5': nodedown
DIAGNOSTICS
===========
nodes in question: ['rabbit@cob-dell5']
hosts, their running nodes and ports:
- cob-dell5: [{rabbitmqctl2648,48609}]
current node details:
- node name: 'rabbitmqctl2648@cob-dell5'
- home dir: /var/lib/rabbitmq
- cookie hash: 8DNoVu56TqDYWypW7YXDJw==
Expected results:
Changing password for user "guest" ...
...done.
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 7 months
[Bug 1036359] New: ejabberd logs not reopened after rotation
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1036359
Bug ID: 1036359
Summary: ejabberd logs not reopened after rotation
Product: Fedora
Version: 20
Component: ejabberd
Assignee: lemenkov(a)gmail.com
Reporter: redhat(a)subs.maneos.org
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, jkaluza(a)redhat.com,
lemenkov(a)gmail.com, martin(a)laptop.org
Description of problem:
Version-Release number of selected component (if applicable):
ejabberd-2.1.13-7.fc20.x86_64
How reproducible:
Steps to Reproduce:
1. Make sure ejabberd is running and logrotate is enabled.
2. Wait until logrotate runs.
3. Check contents of /var/log/ejabberd/ejabberd.log.
Actual results:
0 size file that never gets updated.
Expected results:
File containing log entries for events as they occur.
Additional info:
/etc/logrotate.d/ejabberd is trying to run /usr/sbin/ejabberdctl, but
ejabberdctl is installed in /usr/bin now.
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 8 months
[Bug 1023017] New: Restore ECC support in Erlang's crypto library
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1023017
Bug ID: 1023017
Summary: Restore ECC support in Erlang's crypto library
Product: Fedora
Version: rawhide
Component: erlang
Severity: high
Assignee: lemenkov(a)gmail.com
Reporter: lemenkov(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, lemenkov(a)gmail.com,
rhbugs(a)n-dimensional.de
Right now ECC is disabled explicitly since it looks like Erlang's crypto
library assumes that it's either available fully or not. We've just enabled few
ECC curves so this confuses erlang-crypto and leads to a startup issue like
this:
=ERROR REPORT==== 24-Oct-2013::16:30:48 ===
Unable to load crypto library. Failed with error:
"load_failed, Failed to load NIF library:
'/usr/lib64/erlang/lib/crypto-3.1/priv/lib/crypto.so: undefined symbol:
EC_GROUP_new_curve_GF2m'"
OpenSSL might not be installed on this system.
We should patch crypto module to provide available ECC bits instead of
disabling it completely.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=COwcnn7Cu3&a=cc_unsubscribe
9 years, 8 months
[Bug 1038314] New: Cyclic dependencies: erlang and erlang-examples
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1038314
Bug ID: 1038314
Summary: Cyclic dependencies: erlang and erlang-examples
Product: Fedora
Version: 19
Component: erlang
Assignee: lemenkov(a)gmail.com
Reporter: jakub.jedelsky(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, lemenkov(a)gmail.com,
rhbugs(a)n-dimensional.de
Description of problem:
It is impossible to remove erlang package with /usr/bin/rpm command with
erlang-examples and vice versa. There are cyclic dependencies among these two
packages.
Version-Release number of selected component (if applicable):
erlang-R16B-02.3.fc19.x86_64
How reproducible:
always
Steps to Reproduce:
1. try to remove erlang
$ /usr/bin/rpm -e erlang
returns:
error: Failed dependencies:
erlang(x86-64) = R16B-02.3.fc19 is needed by (installed)
erlang-examples-R16B-02.3.fc19.x86_64
2. try to remove erlang-examples
$ /usr/bin/rpm -e erlang-examples
returns:
error: Failed dependencies:
erlang-examples(x86-64) = R16B-02.3.fc19 is needed by (installed)
erlang-R16B-02.3.fc19.x86_64
3. try to remove erlang
...
Actual results:
can't remove erlang without erlang-examples and vice versa
Expected results:
One of packages is possible to remove without any dependencies.
Additional info:
It's because of puppet, which removes packages through rpm command. There is no
problem with removing through yum.
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 8 months
[Bug 1056027] New: tsung-recorder script on x86_64 uses wrong path to Erlang
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1056027
Bug ID: 1056027
Summary: tsung-recorder script on x86_64 uses wrong path to
Erlang
Product: Fedora EPEL
Version: el6
Component: tsung
Severity: medium
Assignee: cickumqt(a)gmail.com
Reporter: ts(a)bee.kz
QA Contact: extras-qa(a)fedoraproject.org
CC: cickumqt(a)gmail.com, erlang(a)lists.fedoraproject.org,
lemenkov(a)gmail.com
Description of problem:
tsung-recorder script on x86_64 uses wrong path to Erlang
Version-Release number of selected component (if applicable):
1.5.0-3.el6
How reproducible:
Steps to Reproduce:
$ yum install tsung
$ cat /usr/bin/tsung-recorder | grep ^INSTALL_DIR
Actual results:
INSTALL_DIR=/usr/lib/erlang/
Expected results:
INSTALL_DIR=/usr/lib64/erlang/
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 9 months
[Bug 1059913] New: Race condition creating .erlang.cookie
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1059913
Bug ID: 1059913
Summary: Race condition creating .erlang.cookie
Product: Fedora
Version: 20
Component: rabbitmq-server
Assignee: hubert.plociniczak(a)gmail.com
Reporter: jeckersb(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org,
hubert.plociniczak(a)gmail.com, lemenkov(a)gmail.com,
skottler(a)redhat.com
Description of problem:
There is a race condition when starting rabbitmq-server for the first time.
When the erlang runtime starts, it tries to read its cookie file (for rabbitmq,
/var/lib/rabbitmq/.erlang.cookie) and if it doesn't already exist, it generates
a new random cookie and creates the file.
The following two lines from the rabbitmq-service.service unit file are
involved:
ExecStart=/usr/lib/rabbitmq/bin/rabbitmq-server
ExecStartPost=/usr/lib/rabbitmq/bin/rabbitmqctl wait /var/run/rabbitmq/pid
The rabbitmq-server command returns before the service is up. Therefor it is
required to exec the additional rabbitmqctl wait in order to make sure the
service starts all the way. However both of these are erlang programs, and
they share the cookie startup code described previously.
There is variance on the order of events and the eventual error. But generally
what happens is:
- ExecStart (rabbitmq-server) is run and exits. The erlang runtime is now
booting in the background.
- ExecStartPost (rabbitmqctl) is run.
- rabbitmq-server determines the cookie file is not present, and generates a
new cookie.
- rabbitmqctl determines the cookie file is not present, and generates a new
cookie.
- rabbitmq-server writes the new cookie to disk and sets the file to read-only
- rabbitmqctl tries to open the cookie file read/write in order to write its
cookie, but errors with EACCESS because the file already exists and is read
only.
- The erlang runtime for rabbitmqctl crashes and the command returns with a
non-successful exit code.
- The entire service unit is marked as failed, and all of the processes are
killed by systemd.
Version-Release number of selected component (if applicable):
rabbitmq-server-3.1.5-1.fc20.noarch
erlang-R16B-03.1.fc20.x86_64
How reproducible:
There is some variability since it's a race. I've provided my reproducer below
that works 100% of the time for me, inside a F20 VM. In theory this behavior
should still exist if starting the service from the cli instead of rebooting,
but I can't reproduce it that way.
Steps to Reproduce:
1. install rabbitmq-server
2. systemctl enable rabbitmq-server.service
3. reboot
Actual results:
Service fails to start, see attachment of journalctl output for error
Expected results:
Service starts cleanly
Additional info:
This is really an erlang bug, but the workaround for rabbit is simple (I'll
post a patch in a followup). I'll run down the erlang bit separately but it
will take longer, so it makes sense to apply the workaround here until erlang
is fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 11 months
Bootstrapping erlang-rebar for EPEL7
by Sam Kottler
Greetings,
It's currently not possible to do a complete bootstrap of the erlang stack for EPEL7 because of a circular dependency in erlang-rebar. Right now there's a patch (rebar-0003-Remove-bundled-getopt.patch) applied to erlang-rebar which removes getopt from the upstream tarball. Unfortunately, rebar requires getopt to properly build and getopt subsequently requires rebar to build. Is it acceptable to remove the unbundling patch for the initial bootstrap (controlled via a variable I'll add to the spec) to get erlang-rebar built and then build erlang-getopt with the unbundled package?
-Sam
10 years, 2 months