https://bugzilla.redhat.com/show_bug.cgi?id=1240487
Bug ID: 1240487
Summary: erl segfault on fedora-23-i686 (autoconf testsuite)
Product: Fedora
Version: rawhide
Component: erlang
Assignee: lemenkov(a)gmail.com
Reporter: praiskup(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, lemenkov(a)gmail.com,
rhbugs(a)n-dimensional.de, s(a)shk.io
We observe autoconf FTBFS on rawhide (testsuite failures). One of the
testsuite failures is related to Erlang & autoconf, but it appears only on
i686. I tried to cut related testcase out into segfault-i686.tar.gz
reproducer:
$ tar -xf segfault-i686.tar.gz
$ cd segfault-i686
$ make && make run
erlc -b beam my_testsuite.erl
cd lib && ./compile
erl -pa ./lib -s my_testsuite test
Erlang/OTP 17 [erts-6.3] [source] [smp:4:4] [async-threads:10] [hipe]
[kernel-poll:false]
Eshell V6.3 (abort with ^G)
1> All 3 tests passed.
Makefile:6: recipe for target 'run' failed
make: *** [run] Segmentation fault (core dumped)
The segfault ^^ breaks autoconf testsuite, but I'm not able to diagnose
properly. Any help appreciated, let me know if you need some other info.
FTBFS:
https://kojipkgs.fedoraproject.org//work/tasks/7404/10217404/build.log
Pavel
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1027729
Bug ID: 1027729
Summary: erlang-folsom-0.8.0 is available
Product: Fedora
Version: rawhide
Component: erlang-folsom
Keywords: FutureFeature, Triaged
Assignee: lemenkov(a)gmail.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, lemenkov(a)gmail.com
Latest upstream release: 0.8.0
Current version/release in Fedora Rawhide: 0.7.4-2.fc20
URL: https://github.com/boundary/folsom/tags
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1179216
Bug ID: 1179216
Summary: Utilize system-wide crypto-policies
Product: Fedora
Version: 21
Component: ejabberd
Assignee: lemenkov(a)gmail.com
Reporter: nmavrogi(a)redhat.com
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
Please convert to use the system's crypto policy for SSL and TLS:
https://fedoraproject.org/wiki/Packaging:CryptoPolicies
If this program is compiled against gnutls, change the default priority string
to be "@SYSTEM" or to use gnutls_set_default_priority().
If this program is compiled against openssl, and there is no default cipher
list specified, you don't need to modify it. Otherwise replace the default
cipher list with "PROFILE=SYSTEM".
In both cases please verify that the application uses the system's crypto
policies.
If the package is already using the system-wide crypto policies, or it does not
use SSL or TLS, no action is required, the bug can simply be closed.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1204119
Bug ID: 1204119
Summary: ejabberd-15.03 is available
Product: Fedora
Version: rawhide
Component: ejabberd
Keywords: FutureFeature, Triaged
Assignee: lemenkov(a)gmail.com
Reporter: upstream-release-monitoring(a)fedoraproject.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
Latest upstream release: 15.03
Current version/release in rawhide: 14.07-6.fc22
URL: https://github.com/processone/ejabberd
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1302368
Bug ID: 1302368
Summary: rabbitmq-server service timeout on stop
Product: Fedora
Version: 23
Component: rabbitmq-server
Severity: low
Assignee: lemenkov(a)gmail.com
Reporter: christopherjabrams(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org,
hubert.plociniczak(a)gmail.com, jeckersb(a)redhat.com,
lemenkov(a)gmail.com, rjones(a)redhat.com, s(a)shk.io
Description of problem:
The rabbitmq-server service times out when calling stop.
Version-Release number of selected component (if applicable):
rabbitmq-server-3.5.7-1.fc23.noarch
How reproducible:
Always
Steps to Reproduce:
1. sudo systemctl start rabbitmq-server
2. sudo systemctl stop rabbitmq-server
Actual results:
Stop times out after 90 seconds. From the systemd journal:
Jan 27 15:47:14 localhost.localdomain systemd[1]: Stopping RabbitMQ broker...
-- Subject: Unit rabbitmq-server.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit rabbitmq-server.service has begun shutting down.
Jan 27 15:47:14 localhost.localdomain systemd[1]: Cannot find unit for notify
message of PID 10985.
Jan 27 15:47:14 localhost.localdomain systemd[1]: Cannot find unit for notify
message of PID 10986.
Jan 27 15:47:14 localhost.localdomain systemd[1]: Cannot find unit for notify
message of PID 10987.
Jan 27 15:47:14 localhost.localdomain rabbitmqctl[10874]: Stopping and halting
node rabbit@localhost ...
Jan 27 15:48:44 localhost.localdomain systemd[1]: rabbitmq-server.service:
State 'stop-final-sigterm' timed out. Killing.
Jan 27 15:48:44 localhost.localdomain systemd[1]: Stopped RabbitMQ broker.
-- Subject: Unit rabbitmq-server.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit rabbitmq-server.service has finished shutting down.
Jan 27 15:48:44 localhost.localdomain systemd[1]: rabbitmq-server.service: Unit
entered failed state.
Jan 27 15:48:44 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=rabbitmq-server comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=failed'
Jan 27 15:48:44 localhost.localdomain systemd[1]: rabbitmq-server.service:
Failed with result 'timeout'.
Expected results:
The service stops without timing out.
Additional info:
If I call 'sudo rabbitmqctl stop', RabbitMQ stops promptly. A subsequent call
to 'sudo systemctl stop rabbitmq-server' then returns quickly.
--
You are receiving this mail because:
You are on the CC list for the bug.