[Bug 1138213] New: Rabbitmq cluster remains partitioned after short network partition incident
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1138213
Bug ID: 1138213
Summary: Rabbitmq cluster remains partitioned after short
network partition incident
Product: Fedora
Version: 20
Component: rabbitmq-server
Assignee: lemenkov(a)gmail.com
Reporter: jprovazn(a)redhat.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:
In 3-node rabbitmq cluster after network partition happens and then when 3
nodes can communicate again, then cluster remains partitioned if
"pause_minority" policy is used.
This happens if network outage is short enough (~60secs), for longer outages
(>3 minutes) cluster was reconstructed properly. Very similar issue was
reported here:
http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2014-March/034639.html
This issue seems to be fixed in upstream already (not sure in which version
exactly, but 3.3.5 works fine).
Version-Release number of selected component (if applicable):
rabbitmq-server-3.1.5-9.fc20.noarch
Steps to Reproduce:
1. create 3-node cluster, use "pause_minority" no-quorum policy
2. stop networking on one of nodes and wait until the node is seen as shutdown
on other nodes
3. start networking on the node again
Actual results:
Cluster remains partitioned:
[root@overcloud-controller1-csugetg5pjql ~]# rabbitmqctl cluster_status
Cluster status of node 'rabbit@overcloud-controller1-csugetg5pjql' ...
[{nodes,
[{disc,
['rabbit@overcloud-controller0-o6yt2gtaxk6g',
'rabbit@overcloud-controller1-csugetg5pjql',
'rabbit@overcloud-controller2-z3tswnamdzhq']}]},
{running_nodes,
['rabbit@overcloud-controller0-o6yt2gtaxk6g',
'rabbit@overcloud-controller1-csugetg5pjql']},
{partitions,
[{'rabbit@overcloud-controller0-o6yt2gtaxk6g',
['rabbit@overcloud-controller2-z3tswnamdzhq']},
{'rabbit@overcloud-controller1-csugetg5pjql',
['rabbit@overcloud-controller2-z3tswnamdzhq']}]}]
...done.
Expected results:
no partitiones after the node is up again
Additional info:
only related message in log:
Mnesia('rabbit@overcloud-controller0-o6yt2gtaxk6g'): ** ERROR ** mnesia_event
got {inconsistent_database, running_partitioned_network,
'rabbit@overcloud-controller2-z3tswnamdzhq'}
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 10 months
[Bug 1098806] New: [abrt] couchdb: __pthread_mutex_lock(): couchjs killed by SIGSEGV
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1098806
Bug ID: 1098806
Summary: [abrt] couchdb: __pthread_mutex_lock(): couchjs killed
by SIGSEGV
Product: Fedora
Version: 20
Component: couchdb
Assignee: lemenkov(a)gmail.com
Reporter: fedorabugs(a)aylett.co.uk
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, lemenkov(a)gmail.com
Description of problem:
Running the built-in installation verification, after adding an SELinux rule to
work around #1098802.
After the crash, one of the Erlang processes seemed to get stuck in a restart
loop.
Version-Release number of selected component:
couchdb-1.5.0-1.fc20
Additional info:
reporter: libreport-2.2.2
backtrace_rating: 4
cmdline: /usr/bin/couchjs /usr/share/couchdb/server/main.js
crash_function: __pthread_mutex_lock
executable: /usr/lib64/erlang/lib/couch-1.5.0/priv/couchjs
kernel: 3.14.3-200.fc20.x86_64
runlevel: N 5
type: CCpp
uid: 984
Truncated backtrace:
Thread no. 1 (8 frames)
#0 __pthread_mutex_lock at ../nptl/pthread_mutex_lock.c:66
#1 PR_Lock at ../../../nspr/pr/src/pthreads/ptsynch.c:177
#2 AutoLockGC at jscntxt.h:2601
#3 finish at jsgc.cpp:2048
#4 js_FinishGC at jsgc.cpp:869
#5 JSRuntime::~JSRuntime at jsapi.cpp:696
#6 JS_Finish at jsapi.cpp:763
#7 JS_Init at jsapi.cpp:753
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 10 months
[Bug 1098802] New: SELinux alerts starting and running couchdb
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1098802
Bug ID: 1098802
Summary: SELinux alerts starting and running couchdb
Product: Fedora
Version: 20
Component: couchdb
Assignee: lemenkov(a)gmail.com
Reporter: fedorabugs(a)aylett.co.uk
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, lemenkov(a)gmail.com
Created attachment 896832
--> https://bugzilla.redhat.com/attachment.cgi?id=896832&action=edit
Output of `sudo grep type=AVC /var/log/audit/audit.log`
Description of problem:
After installing couchdb in F20, when starting the service you get SELinux
alerts. The web UI runs, but the internal self-test fails.
Version-Release number of selected component (if applicable):
Installed:
couchdb.x86_64 0:1.5.0-1.fc20
Dependency Installed:
erlang-asn1.x86_64 0:R16B-03.5.fc20
erlang-compiler.x86_64 0:R16B-03.5.fc20
erlang-crypto.x86_64 0:R16B-03.5.fc20
erlang-erts.x86_64 0:R16B-03.5.fc20
erlang-et.x86_64 0:R16B-03.5.fc20
erlang-gs.x86_64 0:R16B-03.5.fc20
erlang-hipe.x86_64 0:R16B-03.5.fc20
erlang-ibrowse.x86_64 0:2.2.0-8.fc20
erlang-inets.x86_64 0:R16B-03.5.fc20
erlang-kernel.x86_64 0:R16B-03.5.fc20
erlang-mnesia.x86_64 0:R16B-03.5.fc20
erlang-mochiweb.x86_64 0:2.4.2-3.fc20
erlang-oauth.x86_64 0:1.4.0-1.fc20
erlang-observer.x86_64 0:R16B-03.5.fc20
erlang-os_mon.x86_64 0:R16B-03.5.fc20
erlang-otp_mibs.x86_64 0:R16B-03.5.fc20
erlang-public_key.x86_64 0:R16B-03.5.fc20
erlang-runtime_tools.x86_64 0:R16B-03.5.fc20
erlang-sasl.x86_64 0:R16B-03.5.fc20
erlang-snappy.x86_64 0:1.0.3-0.5.git80db168.fc20
erlang-snmp.x86_64 0:R16B-03.5.fc20
erlang-ssl.x86_64 0:R16B-03.5.fc20
erlang-stdlib.x86_64 0:R16B-03.5.fc20
erlang-syntax_tools.x86_64 0:R16B-03.5.fc20
erlang-tools.x86_64 0:R16B-03.5.fc20
erlang-webtool.x86_64 0:R16B-03.5.fc20
erlang-wx.x86_64 0:R16B-03.5.fc20
erlang-xmerl.x86_64 0:R16B-03.5.fc20
lksctp-tools.x86_64 0:1.0.15-2.fc20
How reproducible:
sudo systemctl start couchdb
Browse to http://127.0.0.1:5984/_utils/verify_install.html and choose to verify
your installation.
Actual results:
Three alerts in the SELinux Alert Browser
Expected results:
All operations succeed.
Additional info:
Output of `sudo grep type=AVC /var/log/audit/audit.log` attached. That output
suggests there may be a conflict with my install of docker-io?
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 10 months
[Bug 1067367] New: [abrt] erlang-erts: wxEvtHandler::Disconnect(): beam.smp killed by SIGSEGV
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1067367
Bug ID: 1067367
Summary: [abrt] erlang-erts: wxEvtHandler::Disconnect():
beam.smp killed by SIGSEGV
Product: Fedora
Version: 20
Component: erlang
Assignee: lemenkov(a)gmail.com
Reporter: razorpeak(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, skottler(a)redhat.com
Version-Release number of selected component:
erlang-erts-R16B-03.1.fc20
Additional info:
reporter: libreport-2.1.12
backtrace_rating: 4
cmdline: /usr/lib64/erlang/erts-5.10.4/bin/beam.smp -- -root
/usr/lib64/erlang -progname erl -- -home /home/bikram -- -pa ebin -pa
../../deps/bullet/ebin ../../deps/cowboy/ebin ../../deps/dderloci/ebin
../../deps/erlimem/ebin ../../deps/erloci/ebin ../../deps/goldrush/ebin
../../deps/imem/ebin ../../deps/jsx/ebin ../../deps/lager/ebin
../../deps/mimetypes/ebin ../../deps/node_package/ebin ../../deps/proper/ebin
../../deps/ranch/ebin ../../deps/sqlparse/ebin -name
dderl(a)WKS01.k2informatics.ch -setcookie zdss4d2_6tP -s dderl -dderl port 8443
-imem tcp_port 8125 -imem erl_cluster_mgr '\'dderl(a)WKS01.k2informatics.ch\''
-imem mnesia_schema_name dderlstag
crash_function: wxEvtHandler::Disconnect
executable: /usr/lib64/erlang/erts-5.10.4/bin/beam.smp
kernel: 3.12.9-301.fc20.x86_64
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (10 frames)
#0 wxEvtHandler::Disconnect at src/common/event.cpp:1376
#1 WxeApp::wxe_dispatch at gen/wxe_funcs.cpp:122
#2 WxeApp::dispatch at wxe_impl.cpp:398
#3 WxeApp::dispatch_cmds at wxe_impl.cpp:351
#4 wxEvtHandler::ProcessEventIfMatches at src/common/event.cpp:1239
#5 wxEvtHandler::SearchDynamicEventTable at src/common/event.cpp:1421
#6 wxEvtHandler::ProcessEvent at src/common/event.cpp:1297
#7 wxAppBase::ProcessIdle at src/common/appcmn.cpp:449
#8 wxapp_idle_callback at src/gtk/app.cpp:213
#13 gtk_main at gtkmain.c:1257
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 10 months
[Bug 1064577] New: [abrt] erlang-erts: beam.smp killed by SIGSEGV
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1064577
Bug ID: 1064577
Summary: [abrt] erlang-erts: beam.smp killed by SIGSEGV
Product: Fedora
Version: 20
Component: erlang
Assignee: lemenkov(a)gmail.com
Reporter: redhat(a)astekk.se
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, lemenkov(a)gmail.com,
rhbugs(a)n-dimensional.de, skottler(a)redhat.com
Description of problem:
I used the debugger ( im() from eshell). and had a lot of processes breaking, w
auto attach on break enabled.
The gui got pretty unresponsive then, so I'm not entirely sure what I may have
done to it, to cause this.
Version-Release number of selected component:
erlang-erts-R16B-03.1.fc20
Additional info:
reporter: libreport-2.1.12
backtrace_rating: 3
cmdline: /usr/lib64/erlang/erts-5.10.4/bin/beam.smp -P 10000000 -K true
-- -root /usr/lib64/erlang -progname erl -- -home /home/kaos -- -pa
/home/kaos/src/zotonic/ebin /home/kaos/src/zotonic/deps/bear/ebin
/home/kaos/src/zotonic/deps/bert/ebin /home/kaos/src/zotonic/deps/dh_date/ebin
/home/kaos/src/zotonic/deps/edown/ebin /home/kaos/src/zotonic/deps/eiconv/ebin
/home/kaos/src/zotonic/deps/elog/ebin /home/kaos/src/zotonic/deps/emqtt/ebin
/home/kaos/src/zotonic/deps/folsom/ebin
/home/kaos/src/zotonic/deps/gen_smtp/ebin
/home/kaos/src/zotonic/deps/goldrush/ebin
/home/kaos/src/zotonic/deps/lager/ebin /home/kaos/src/zotonic/deps/meck/ebin
/home/kaos/src/zotonic/deps/mimetypes/ebin
/home/kaos/src/zotonic/deps/mochiweb/ebin
/home/kaos/src/zotonic/deps/parse_trans/ebin
/home/kaos/src/zotonic/deps/sendfile/ebin
/home/kaos/src/zotonic/deps/ua_classifier/ebin
/home/kaos/src/zotonic/deps/webzmachine/ebin
/home/kaos/src/zotonic/deps/z_stdlib/ebin
/home/kaos/src/zotonic/modules/mod_oauth/deps/erlang-oauth/ebin
/home/kaos/src/zotonic/priv/modules/*/deps/*/ebin
/home/kaos/src/zotonic/priv/sites/*/deps/*/ebin
/home/kaos/src/zotonic/priv/sites/*/modules/*/deps/*/ebin -sname
zotonic001@cypher -boot start_sasl -config
/home/kaos/src/zotonic/priv/erlang.config -sasl errlog_type error -s zotonic
executable: /usr/lib64/erlang/erts-5.10.4/bin/beam.smp
kernel: 3.12.9-301.fc20.x86_64
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (10 frames)
#0 ??
#1 WxeApp::wxe_dispatch at gen/wxe_funcs.cpp:8951
#2 WxeApp::dispatch at wxe_impl.cpp:398
#3 WxeApp::dispatch_cmds at wxe_impl.cpp:351
#4 wxEvtHandler::ProcessEventIfMatches at src/common/event.cpp:1239
#5 wxEvtHandler::SearchDynamicEventTable at src/common/event.cpp:1421
#6 wxEvtHandler::ProcessEvent at src/common/event.cpp:1297
#7 wxAppBase::ProcessIdle at src/common/appcmn.cpp:449
#8 wxapp_idle_callback at src/gtk/app.cpp:213
#13 gtk_main at gtkmain.c:1257
Potential duplicate: bug 1013431
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 10 months
[Bug 1153840] New: CVE-2014-8760 ejabberd: clients can unexpectedly connect without encryption [fedora-all]
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1153840
Bug ID: 1153840
Summary: CVE-2014-8760 ejabberd: clients can unexpectedly
connect without encryption [fedora-all]
Product: Fedora
Version: 20
Component: ejabberd
Keywords: Security, SecurityTracking
Severity: medium
Priority: medium
Assignee: lemenkov(a)gmail.com
Reporter: mmcallis(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
Blocks: 1153839 (CVE-2014-8760)
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time. If you need to fix the versions independent of each other,
you may clone this bug as appropriate.
[bug automatically created by: add-tracking-bugs]
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1153839
[Bug 1153839] CVE-2014-8760 ejabberd: clients can unexpectedly connect
without encryption
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 10 months
[Bug 1148604] New: rabbitmq-server does not start due to missing symbols
by Red Hat Bugzilla
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(a)gmail.com
Reporter: lars(a)redhat.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
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(a)f21-os-test.log
Oct 01 20:16:54 f21-os-test rabbitmq-server[14532]: ###### ##
/var/log/rabbitmq/rabbit(a)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(a)f21-os-test.log
sasl log : /var/log/rabbitmq/rabbit(a)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.
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 1 month
[Bug 1161922] New: Too many dependencies from Erlang
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1161922
Bug ID: 1161922
Summary: Too many dependencies from Erlang
Product: Fedora EPEL
Version: epel7
Component: erlang
Keywords: FutureFeature
Severity: high
Priority: high
Assignee: rjones(a)redhat.com
Reporter: lemenkov(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: antonbaklanov(a)gmail.com, atodorov(a)redhat.com,
awilliam(a)redhat.com, erlang(a)lists.fedoraproject.org,
extras-qa(a)fedoraproject.org, gemi(a)bluewin.ch,
hubert.plociniczak(a)gmail.com, jkaluza(a)redhat.com,
lemenkov(a)gmail.com, lhh(a)redhat.com, martin(a)laptop.org,
mcepl(a)redhat.com, misc(a)zarb.org, mmahut(a)redhat.com,
ohadlevy(a)redhat.com, rhbugs(a)n-dimensional.de,
rjones(a)redhat.com, s(a)shk.io, sbaker(a)redhat.com,
stick(a)gk2.sk, volker27(a)gmx.at
Depends On: 784693, 1095715, 1095717, 1095718, 1095721, 1095727,
1095699, 1095702, 1095703, 1095705, 1095708, 1095709,
1095710, 1095712
Blocks: 1086146
+++ This bug was initially created as a clone of Bug #784693 +++
Description of problem:
rabbitmq-server has Require: erlang >= R12B-3 which pulls in every possible
erlang package and it's dependencies including: gtk2, atk, tk, SDL and so on.
When using Amazon Linux AMI in Amazon EC2 it points by default to EPEL 6
repository. The side effect is that trying to install rabbitmq-server fails
with lots of missing dependencies. I tried to rebuild the packages myself but
there are way too many packages needed in order to build all necessary
dependencies.
I doubt that wxGTK and friends are all necessary for Rabbitmq. Can you please
fix the EPEL package so it lists only necessary dependencies and not the whole
world.
The Amazon forums thread is here:
https://forums.aws.amazon.com/message.jspa?messageID=282648
Version-Release number of selected component (if applicable):
rabbitmq-server-2.6.1-1.el6.noarch
How reproducible:
always
Steps to Reproduce:
1. yum install rabbitmq-server on Amazon Linux AMI
--- Additional comment from Peter Lemenkov on 2012-01-25 15:42:26 EST ---
I really really wish it could be fixed just removing several dependencies.
Unfortunately it isn't that easy.
The main problem is that although this X11 stuff indeed does not required for
RabbitMQ to run it does required for debugging and on-the-fly analysis. From
someone's point of view if (s)he fails to reproduce some debugging recipes from
internet (for example, starting appmon:start() or debugger:start()) then it's
time to blame packager for broken Erlang distribution and honestly I think it
would be true.
So from the one hand - several X11 libraries and broken dependency chain in
broken variant of RHEL but fully functional Erlang distribution, from the other
hand - Erlang with truncated essential functionality but happy casual
RabbitMQ/Ejabberd/CouchDB/Mochiweb users.
Honestly I really feel for you and will try to cut off a dependency chain but I
also don't want to break something. I plan to do something a bit more
complicated rather than just removing some dependencies - for example some kind
of "soft" dependencies using empty metapackages like erlang-debugger-x11 or
erlang-appmon-x11. Without them every attempt to run some GUI tools from the
console should end up with informative message about packages which must be
installed manually.
So bottom line is - I'd like this ticket to stay open for a while (until I or
someone else proposes something acceptable). But right now it looks like a bug
with Amazon infrastructure.
--- Additional comment from Alexander Todorov on 2012-01-26 04:42:30 EST ---
Hi Peter,
thanks for the quick response.
It's OK with me to split the dependencies in two and be able to handle console
users and GUI too. I hope it's not that hard to implement.
--- Additional comment from Alexander Todorov on 2012-01-26 08:31:51 EST ---
FYI I asked upstream about dependencies. This may be helpful:
http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2012-January/017687....
How about something like:
rabbitmq-server
rabbitmq-server-ssl
rabbitmq-server-hipe
... etc
Is it easy to break it down like this?
--- Additional comment from Peter Lemenkov on 2012-04-08 12:43:40 EDT ---
--- Additional comment from Peter Lemenkov on 2012-04-08 12:45:55 EDT ---
Changing component to erlang and reassigning to myself.
--- Additional comment from Pavol Rusnak on 2012-08-15 08:19:58 EDT ---
Same issue while installing ejabberd. I guess ejabberd should require just
particular erlang modules, not the whole erlang metapackage.
--- Additional comment from Peter Lemenkov on 2013-07-23 09:20:52 EDT ---
--- Additional comment from Peter Lemenkov on 2013-07-23 09:21:46 EDT ---
--- Additional comment from Adam Williamson (Red Hat) on 2013-09-18 00:11:48
EDT ---
--- Additional comment from Adam Williamson (Red Hat) on 2013-09-18 00:13:21
EDT ---
Yeah, I just hit this trying to install ejabberd too.
Seriously, I'm not installing *two* graphical toolkits on my headless server
just to get a jabber server going.
Debian has an 'erlang-nox' metapackage which depends on all of erlang except
the bits that require X:
http://packages.debian.org/sid/erlang-nox
and Debian's ejabberd package requires it. Perhaps you could do that?
--- Additional comment from Peter Lemenkov on 2014-04-02 12:13:41 EDT ---
--- Additional comment from Peter Lemenkov on 2014-04-02 12:15:23 EDT ---
Heads up. Due to numerous requests it was decided to fix this issue (enable
"headless" Erlang) as a Fedora 21 feature. I plan to backport it to the rest of
Erlang branches (including not yet released EL7).
--- Additional comment from Peter Lemenkov on 2014-04-02 12:17:57 EDT ---
See https://fedoraproject.org/wiki/Changes/BetterErlangSupport
--- Additional comment from Lon Hohberger on 2014-04-02 13:59:31 EDT ---
Nice write-up, Peter!
Would it make sense to note your idea where applications which can use the GUI
(but don't need it) throw an error when someone attempts to start them in GUI
mode instead of having GUI libraries as hard install requirements?
--- Additional comment from Lon Hohberger on 2014-04-04 14:10:19 EDT ---
Also, would it make sense to make erlang (source rpm) buildable without wx* in
the first place?
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=784693
[Bug 784693] Too many dependencies from Erlang
https://bugzilla.redhat.com/show_bug.cgi?id=1086146
[Bug 1086146] Better Erlang Support
https://bugzilla.redhat.com/show_bug.cgi?id=1095699
[Bug 1095699] Remove dependency on erlang-gs from erlang-appmon
https://bugzilla.redhat.com/show_bug.cgi?id=1095702
[Bug 1095702] Remove dependency on erlang-gs from erlang-debugger
https://bugzilla.redhat.com/show_bug.cgi?id=1095703
[Bug 1095703] Remove dependency on erlang-gs from erlang-dialyzer
https://bugzilla.redhat.com/show_bug.cgi?id=1095705
[Bug 1095705] Remove dependency on erlang-gs from erlang-et
https://bugzilla.redhat.com/show_bug.cgi?id=1095708
[Bug 1095708] Remove dependency on erlang-gs from erlang-observer
https://bugzilla.redhat.com/show_bug.cgi?id=1095709
[Bug 1095709] Remove dependency on erlang-gs from erlang-pman
https://bugzilla.redhat.com/show_bug.cgi?id=1095710
[Bug 1095710] Remove dependency on erlang-gs from erlang-toolbar
https://bugzilla.redhat.com/show_bug.cgi?id=1095712
[Bug 1095712] Remove dependency on erlang-gs from erlang-tv
https://bugzilla.redhat.com/show_bug.cgi?id=1095715
[Bug 1095715] Remove dependency on erlang-wx from erlang-debugger
https://bugzilla.redhat.com/show_bug.cgi?id=1095717
[Bug 1095717] Remove dependency on erlang-wx from erlang-dialyzer
https://bugzilla.redhat.com/show_bug.cgi?id=1095718
[Bug 1095718] Remove dependency on erlang-wx from erlang-et
https://bugzilla.redhat.com/show_bug.cgi?id=1095721
[Bug 1095721] Remove dependency on erlang-wx from erlang-observer
https://bugzilla.redhat.com/show_bug.cgi?id=1095727
[Bug 1095727] Remove dependency on erlang-wx from erlang-reltool
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 2 months
[Bug 1153842] New: CVE-2014-8760 ejabberd: clients can unexpectedly connect without encryption [epel-6]
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1153842
Bug ID: 1153842
Summary: CVE-2014-8760 ejabberd: clients can unexpectedly
connect without encryption [epel-6]
Product: Fedora EPEL
Version: el6
Component: ejabberd
Keywords: Security, SecurityTracking
Severity: medium
Priority: medium
Assignee: extras-orphan(a)fedoraproject.org
Reporter: mmcallis(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org,
extras-orphan(a)fedoraproject.org, jkaluza(a)redhat.com,
martin(a)laptop.org, mmahut(a)redhat.com
Blocks: 1153839 (CVE-2014-8760)
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora EPEL.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
epel-6 tracking bug for ejabberd: see blocks bug list for full details of the
security issue(s).
[bug automatically created by: add-tracking-bugs]
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1153839
[Bug 1153839] CVE-2014-8760 ejabberd: clients can unexpectedly connect
without encryption
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 3 months
[Bug 1154288] New: The package is missing
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1154288
Bug ID: 1154288
Summary: The package is missing
Product: Fedora EPEL
Version: epel7
Component: ejabberd
Assignee: extras-orphan(a)fedoraproject.org
Reporter: frank-buettner(a)gmx.net
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org,
extras-orphan(a)fedoraproject.org, jkaluza(a)redhat.com,
martin(a)laptop.org, mmahut(a)redhat.com
It still exits in EL6 but missing for EL7.
Erlang 16 is an part of EL7 so I think ejabberd 14.07 shut possible.
--
You are receiving this mail because:
You are on the CC list for the bug.
9 years, 3 months