[Bug 1393649] New: ejabberd'
s unit file should not launch ejabberdctl with /usr/bin/bash
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1393649
Bug ID: 1393649
Summary: ejabberd's unit file should not launch ejabberdctl
with /usr/bin/bash
Product: Fedora
Version: rawhide
Component: ejabberd
Severity: medium
Assignee: lemenkov(a)gmail.com
Reporter: randy(a)electronsweatshop.com
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, jeremy(a)jcline.org,
lemenkov(a)gmail.com, martin(a)laptop.org,
randy(a)electronsweatshop.com
Depends On: 1393643
External Bug ID: Github processone/ejabberd/issues/1375
Description of problem:
Currently, ejabberdctl is launched by systemd with /usr/bin/bash instead of
being launched directly. This causes the process to run in the initrc_t context
which is very permissive. Instead, systemd should launch ejabberdctl directly.
However, there are two blockers to getting this change done and working, as we
get these AVC denials with this change in place:
type=AVC msg=audit(1478751171.862:648): avc: denied { write } for pid=2989
comm="async_2" name="ejabberd.pem" dev="dm-1" ino=44546
scontext=system_u:system_r:rabbitmq_t:s0
tcontext=unconfined_u:object_r:etc_t:s0 tclass=file permissive=0
type=AVC msg=audit(1478751171.863:649): avc: denied { write } for pid=2989
comm="async_2" name="ejabberd.pem" dev="dm-1" ino=44546
scontext=system_u:system_r:rabbitmq_t:s0
tcontext=unconfined_u:object_r:etc_t:s0 tclass=file permissive=0
type=AVC msg=audit(1478751171.865:650): avc: denied { name_bind } for
pid=2986 comm="beam" src=5349 scontext=system_u:system_r:rabbitmq_t:s0
tcontext=system_u:object_r:unreserved_port_t:s0 tclass=tcp_socket permissive=0
I've filed a bug upstream to request that they stop trying to open the certfile
in write mode[0], and I've filed a bug against selinux-policy to request that
ejabberd be allowed to use tcp port 5349[1]. Once both of those bugs are fixed,
we can proceed with dropping /usr/bin/bash presuming that we don't then hit
further AVC denials (which could happen).
Version-Release number of selected component (if applicable):
ejabberd-16.08-2.fc25.x86_64
Additional info:
[0] https://github.com/processone/ejabberd/issues/1375
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1393643
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1393643
[Bug 1393643] ejabberd is not allowed to open tcp port 5349
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 7 months
[Bug 1341252] New: ejabberd does not log to journald
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1341252
Bug ID: 1341252
Summary: ejabberd does not log to journald
Product: Fedora
Version: rawhide
Component: ejabberd
Assignee: lemenkov(a)gmail.com
Reporter: jeremy(a)jcline.org
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, jeremy(a)jcline.org,
lemenkov(a)gmail.com, martin(a)laptop.org,
rbarlow(a)redhat.com
Created attachment 1163265
--> https://bugzilla.redhat.com/attachment.cgi?id=1163265&action=edit
Patch to ejabberd.service
Description of problem:
It'd be great if ejabberd logged to journald rather than /var/log/ejabberd/.
This can be achieved with a few small changes to the systemd unit file. I've
attached my proposed systemd unit file.
Version-Release number of selected component (if applicable):
All currently released versions.
Steps to Reproduce:
1. systemctl start ejabberd.service
2. journalctl -u ejabberd
3. :(
Actual results:
Logs are placed in /var/log/ejabberd
Expected results:
Logging is handled by journald
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 9 months
[Bug 1379050] New: wings fails to run
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1379050
Bug ID: 1379050
Summary: wings fails to run
Product: Fedora
Version: 24
Component: wings
Severity: medium
Assignee: lemenkov(a)gmail.com
Reporter: revdepign(a)yahoo.co.jp
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, lemenkov(a)gmail.com
Description of problem:
wings fails to run.
Version-Release number of selected component (if applicable):
wings-2.0.4-1.fc24.x86_64
How reproducible:
Press "Wings 3D" icon to start the application in Gnome.
Steps to Reproduce:
1. Press "Wings 3D" icon to start the application in Gnome.
Actual results:
No windows are appear and any responses are noticeable.
Expected results:
Wings is functional.
Additional info:
With terminal I got following:
$ wings
=ERROR REPORT==== 24-Sep-2016::20:01:41 ===
WX ERROR: SMP emulator required (start with erl -smp)
=ERROR REPORT==== 24-Sep-2016::20:01:41 ===
Error in process <0.31.0> with exit value:
{not_smp,[{wxe_server,start,1,[{file,"wxe_server.erl"},{line,65}]},
{wx,new,1,[{file,"wx.erl"},{line,115}]},
{wings_theme,native_theme,0,[{file,"wings_theme.erl"},{line,89}]},
{wings_pref,defaults,0,[{file,"wings_pref.erl"},{line,380}]},
{wings_pref,init,0,[{file,"wings_pref.erl"},{line,38}]},
{wings,init,1,[{file,"wings.erl"},{line,96}]}]}
=ERROR REPORT==== 24-Sep-2016::20:01:41 ===
Error in process <0.30.0> with exit value:
{{noproc,{wx_object,call,[progress_bar,cancel]}},
[{wx_object,call,2,[{file,"wx_object.erl"},{line,272}]},
{wings_u,crash_log,3,[{file,"wings_u.erl"},{line,101}]},
{wings,halt_loop,1,[{file,"wings.erl"},{line,69}]}]}
And when I added "-smp" option, I got following:
$ wings -smp
=ERROR REPORT==== 24-Sep-2016::20:02:40 ===
WX ERROR: wxWidgets Assert failure: ./src/gtk/window.cpp(2966): "(m_widget !=
__null)" in DoGetClientSize() : invalid window
=ERROR REPORT==== 24-Sep-2016::20:02:40 ===
WX ERROR: wxWidgets Assert failure: ./src/gtk/window.cpp(2966): "(m_widget !=
__null)" in DoGetClientSize() : invalid window
=ERROR REPORT==== 24-Sep-2016::20:02:40 ===
WX ERROR: wxWidgets Assert failure: ./src/gtk/window.cpp(2957): "(m_widget !=
__null)" in DoSetClientSize() : invalid window
=ERROR REPORT==== 24-Sep-2016::20:02:40 ===
WX ERROR: wxWidgets Assert failure: ./src/gtk/window.cpp(3457): "m_widget !=
__null" in SetFocus() : invalid window
=ERROR REPORT==== 24-Sep-2016::20:02:40 ===
WX ERROR: wxWidgets Assert failure: ./src/gtk/window.cpp(2834): "m_widget" in
DoSetSize() : invalid window
=ERROR REPORT==== 24-Sep-2016::20:02:40 ===
Error in process <0.31.0> with exit value:
{{error,no_gl_context,5075},
[{gl,rec,0,[{file,"gen/gl.erl"},{line,298}]},
{wings_gl,init_extensions,0,[{file,"wings_gl.erl"},{line,55}]},
{wings_init,init,0,[{file,"wings_init.erl"},{line,84}]},
{wings,init,1,[{file,"wings.erl"},{line,102}]}]}
=ERROR REPORT==== 24-Sep-2016::20:02:40 ===
Error in process <0.30.0> with exit value:
{{noproc,{wx_object,call,[progress_bar,cancel]}},
[{wx_object,call,2,[{file,"wx_object.erl"},{line,272}]},
{wings_u,crash_log,3,[{file,"wings_u.erl"},{line,101}]},
{wings,halt_loop,1,[{file,"wings.erl"},{line,69}]}]}
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years
[Bug 1403384] New: -smp flag is required to let wings start
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1403384
Bug ID: 1403384
Summary: -smp flag is required to let wings start
Product: Fedora
Version: 25
Component: wings
Assignee: lemenkov(a)gmail.com
Reporter: germano.massullo(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, lemenkov(a)gmail.com
Description of problem:
Running
$ wings
result in wings hanging after messages
================
=ERROR REPORT==== 9-Dec-2016::22:55:11 ===
WX ERROR: SMP emulator required (start with erl -smp)
=ERROR REPORT==== 9-Dec-2016::22:55:11 ===
Error in process <0.32.0> with exit value:
{not_smp,[{wxe_server,start,1,[{file,"wxe_server.erl"},{line,65}]},
{wx,new,1,[{file,"wx.erl"},{line,115}]},
{wings_theme,native_theme,0,[{file,"wings_theme.erl"},{line,89}]},
{wings_pref,defaults,0,[{file,"wings_pref.erl"},{line,380}]},
{wings_pref,init,0,[{file,"wings_pref.erl"},{line,38}]},
{wings,init,1,[{file,"wings.erl"},{line,96}]}]}
=ERROR REPORT==== 9-Dec-2016::22:55:11 ===
Error in process <0.31.0> with exit value:
{{noproc,{wx_object,call,[progress_bar,cancel]}},
[{wx_object,call,2,[{file,"wx_object.erl"},{line,272}]},
{wings_u,crash_log,3,[{file,"wings_u.erl"},{line,101}]},
{wings,halt_loop,1,[{file,"wings.erl"},{line,69}]}]}
================
the only way to let wings start is to use the -smp flag
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years