[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, 8 months
[Bug 1083637] New: Trim dependencies in rabbitmq-server
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1083637
Bug ID: 1083637
Summary: Trim dependencies in rabbitmq-server
Product: Fedora EPEL
Version: epel7
Component: rabbitmq-server
Assignee: hubert.plociniczak(a)gmail.com
Reporter: lhh(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org,
hubert.plociniczak(a)gmail.com, josh(a)fornwall.com,
rjones(a)redhat.com, skottler(a)redhat.com
Description of problem:
The rabbitmq-server package pulls in 59 dependencies on a system with X
previously installed. (It also pulls in wxGTK and wxGTK-gl, which is
rabbitmq-server needs the following erlang packages to run:
Requires: erlang-inets
Requires: erlang-mnesia
Requires: erlang-erts
Requires: erlang-asn1
Requires: erlang-snmp
Requires: erlang-xmerl
Requires: erlang-stdlib
Requires: erlang-public_key
Requires: erlang-otp_mibs
Requires: erlang-ssl
Requires: erlang-kernel
Requires: erlang-sasl
Requires: erlang-crypto
Requires: erlang-os_mon
Requires: erlang-runtime_tools
There are some internal Requires: lines in erlang which pull in more, but if
you delete them with 'rpm -e --nodeps', rabbitmq-server still operates.
Without changing the internal requirements of the erlang package, using the
above 'Requires' lines cuts the number of dependencies pulled in from ~59 to
~29. It still includes wxGTK / wxGTK-gl, so not perfect, but better.
(It is also possible to build Erlang without wx* support, but it is less
beneficial to do so as doing so breaks things like the debugger - I'll explore
that separately.)
Version-Release number of selected component (if applicable): 3.1.5-3.el7
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 9 months
[Bug 1107767] New: The "rebar eunit -v" command exhibits errors in some tests.
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1107767
Bug ID: 1107767
Summary: The "rebar eunit -v" command exhibits errors in some
tests.
Product: Fedora
Version: rawhide
Component: erlang-eleveldb
Assignee: lemenkov(a)gmail.com
Reporter: efintzel(a)linux.vnet.ibm.com
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, lemenkov(a)gmail.com
Created attachment 907296
--> https://bugzilla.redhat.com/attachment.cgi?id=907296&action=edit
Patch used for the spec file
Description of problem:
The "rebar eunit -v" command exhibits errors in some tests.
Version-Release number of selected component (if applicable):
erlang-eleveldb-1.3.2-2.fc21.src.rpm
How reproducible:
Mock build with make check active.
Actual results:
cacheleak: cacheleak_test_ (module 'cacheleak')...enif_send: env==NULL on
non-SMP VM/var/tmp/rpm-tmp.LY07JU: line 31: 31546 Aborted rebar
eunit -v
error: Bad exit status from /var/tmp/rpm-tmp.LY07JU (%check)
module 'cleanup'
cleanup: assumption_test...enif_send: env==NULL on non-SMP
VM/var/tmp/rpm-tmp.PQdkaz: line 31: 6614 Aborted rebar eunit
-v
error: Bad exit status from /var/tmp/rpm-tmp.PQdkaz (%check)
Additional info:
Removed the cacheleak test for fc21, as it is already done for fc17 and fc18.
The cleanup test was also removed for fc21.
Then build was ran again with success.
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 9 months
[Bug 1080382] New: tsung erlang lib directory is wrong on lib64
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1080382
Bug ID: 1080382
Summary: tsung erlang lib directory is wrong on lib64
Product: Fedora
Version: rawhide
Component: tsung
Assignee: cickumqt(a)gmail.com
Reporter: kwizart(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: cickumqt(a)gmail.com, erlang(a)lists.fedoraproject.org,
lemenkov(a)gmail.com
Description of problem:
The tsung erlang lib directory is wrong on lib64 when running the following
command:
tsung-recorder -p webdav start
Version-Release number of selected component (if applicable):
tsung-1.5.0-3.fc20.x86_64
How reproducible:
always with tsung-recorder
Steps to Reproduce:
1. tsung-recorder -p webdav start
2.
3.
Actual results:
Creating local Tsung directory /home/kwizart/.tsung
Creating Tsung log directory /home/kwizart/.tsung/log
Starting Tsung recorder on port 8090
$ {"init terminating in do_boot",{'cannot get
bootfile','/usr/lib/erlang//lib/tsung_recorder-1.5.0/priv/tsung_recorder.boot'}}
Expected results:
don't know yet...
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 9 months
[Bug 1106357] New: tsung: please upgrade to 1.5.1
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1106357
Bug ID: 1106357
Summary: tsung: please upgrade to 1.5.1
Product: Fedora EPEL
Version: el6
Component: tsung
Severity: high
Assignee: i(a)cicku.me
Reporter: larry(a)l2g.to
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, i(a)cicku.me,
lemenkov(a)gmail.com
Tsung 1.5.1 was released on April 9. It addresses bugs in 1.5.0 that prevent
load-testing of HTTPS servers.
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 9 months
[Bug 1103524] New: Change rabbitmq-server systemd service to Type=notify
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1103524
Bug ID: 1103524
Summary: Change rabbitmq-server systemd service to Type=notify
Product: Fedora
Version: rawhide
Component: rabbitmq-server
Assignee: hubert.plociniczak(a)gmail.com
Reporter: lemenkov(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: apevec(a)redhat.com, erlang(a)lists.fedoraproject.org,
hubert.plociniczak(a)gmail.com, jeckersb(a)redhat.com,
lemenkov(a)gmail.com, rjones(a)redhat.com,
rohara(a)redhat.com, s(a)shk.io, skottler(a)redhat.com
Depends On: 1059913
+++ This bug was initially created as a clone of Bug #1059913 +++
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.
--- Additional comment from John Eckersberg on 2014-01-30 18:06:26 EST ---
--- Additional comment from John Eckersberg on 2014-01-31 09:33:31 EST ---
This patch updates the systemd service to run `rabbitmqctl status` before
starting the rabbitmq-server process. This ensures the erlang cookie is
created before starting the service.
--- Additional comment from Richard W.M. Jones on 2014-04-01 13:58:41 EDT ---
I performed the steps given in the bug description and the patch
works for me in a Rawhide VM.
The patch also looks reasonable to me and low risk, so I'm going to
backport it to Fedora 20.
--- Additional comment from Fedora Update System on 2014-04-01 14:51:47 EDT ---
rabbitmq-server-3.1.5-5.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/rabbitmq-server-3.1.5-5.fc20
--- Additional comment from Fedora Update System on 2014-04-03 00:08:25 EDT ---
Package rabbitmq-server-3.1.5-5.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing rabbitmq-server-3.1.5-5.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-4722/rabbitmq-server-...
then log in and leave karma (feedback).
--- Additional comment from Sam Kottler on 2014-04-03 09:07:54 EDT ---
I'll merge rawhide into EPEL7 when I'm at a machine with my certs on it.
--- Additional comment from Alan Pevec on 2014-04-08 13:02:47 EDT ---
Instead of messing with ExecStartPost, it would be more reliable to switch
systemd service to Type=notify just need someone familiar with rabbitmq to tell
us where to put sd_notify to send notification when service is ready.
--- Additional comment from Fedora Update System on 2014-04-14 18:47:32 EDT ---
rabbitmq-server-3.1.5-5.fc20 has been pushed to the Fedora 20 stable
repository. If problems still persist, please make note of it in this bug
report.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1059913
[Bug 1059913] Race condition creating .erlang.cookie
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 10 months