[Bug 1094143] New: Desktop centric polkit ejabberdctl policy file, prevents server use
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1094143
Bug ID: 1094143
Summary: Desktop centric polkit ejabberdctl policy file,
prevents server use
Product: Fedora
Version: 20
Component: ejabberd
Assignee: lemenkov(a)gmail.com
Reporter: stefw(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: 1094121
Description of problem:
The shipped polkit policy is completely desktop-centric and expects that the
admin user is logged in a local session (ie: a seat in logind parlance, with a
monitor and keyboard).
This prevents DBus API use when logged in via ssh (and using pkttyagent as your
polkit agent) or via Cockpit.
The <allow_any> tag in polkit policy applies to non-local sessions. It should
be set to something other than 'no' unless the action directly affects hardware
of the login seat.
Version-Release number of selected component (if applicable):
2.1.13-7.fc20
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1094121
[Bug 1094121] Tracker: Fix desktop centric polkit policy
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 8 months
[Bug 1077547] New: Riak service won't start
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1077547
Bug ID: 1077547
Summary: Riak service won't start
Product: Fedora
Version: 20
Component: riak
Severity: high
Assignee: lemenkov(a)gmail.com
Reporter: j.mark.brooks(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, lemenkov(a)gmail.com
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 10 months
[Bug 1036780] New: rabbitmq-server wrapper script drops arguments
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1036780
Bug ID: 1036780
Summary: rabbitmq-server wrapper script drops arguments
Product: Fedora
Version: rawhide
Component: rabbitmq-server
Assignee: hubert.plociniczak(a)gmail.com
Reporter: rhbugs(a)rbu.sh
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:
the wrapper script /usr/sbin/rabbitmqctl drops all arguments to the command in
certain cases, for example when the calling user is not root.
I am running a rabbitmq node as a local user (for development) as a regular
user, outside of /var. This works fine, however the Fedora-specific wrapper to
"rabbitctl" will obscure access to the rabbitctl script. It took me quite a
while to debug what was happening, until I found out the command is really a
wrapper whose sole purpose is munging arguments -- and it does it wrong.
Version-Release number of selected component (if applicable):
I am on 3.1.5-1.fc19 but I see the same bug in rawhide.
How reproducible:
Always.
Steps to Reproduce:
1. Be non-root / non-rabbitmq user
2. Run rabbitmqctl status
Actual results:
Error: could not recognise command
Usage:
rabbitmqctl [-n <node>] [-q] <command> [<command options>]
...
Expected results:
Status of node rabbit@localhost ...
[{pid,1234},...
Additional info:
The warning "Only root or rabbitmq should run" should really be "Only root or
rabbitmq must run", as currently it makes it impossible for anyone else.
However, this is not true, as any user *can* run rabbitmq.
Furthermore, users in the rabbitmq group should be able to run management
commands, given the correct parameters.
Lastly, the "rabbitmq-plugins" case looks fishy too, as it allows anyone to run
the rabbitmq-plugins command, and makes the first line obsolete.
--
You are receiving this mail because:
You are on the CC list for the bug.
7 years
[Bug 1152267] New: Support multiple instances of couchdb
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1152267
Bug ID: 1152267
Summary: Support multiple instances of couchdb
Product: Fedora
Version: rawhide
Component: couchdb
Assignee: lemenkov(a)gmail.com
Reporter: thomas(a)apestaart.org
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, lemenkov(a)gmail.com,
wtogami(a)gmail.com
Created attachment 946532
--> https://bugzilla.redhat.com/attachment.cgi?id=946532&action=edit
older style init file
Description of problem:
couchdb is often used as a supporting database for different software which
recommends using a different separate instance for various reasons. Examples I
know of are:
- hood.ie which uses different parameters for the config of couchdb
- feat, a clustering agent which uses python view servers which need to be
custom-configured
- desktopcouch, which uses per-user couch instances
- puppet can use it as an ENC
I'm adding an init file (for older Fedora and pre-7 RHEL), and a systemd
multiple instances file.
In my puppet modules for couchdb, I also add some selinux rules for these
differently named instances, which potentially might make sense to just put in
selinux-policy-targeted instead.
--
You are receiving this mail because:
You are on the CC list for the bug.
7 years, 6 months
[Bug 1028657] New: couchdb should also be usable under normal users
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1028657
Bug ID: 1028657
Summary: couchdb should also be usable under normal users
Product: Fedora
Version: rawhide
Component: couchdb
Assignee: lemenkov(a)gmail.com
Reporter: cickumqt(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, lemenkov(a)gmail.com
1. Running under normal user:
[rpmaker@fab fedpkg]$ couchdb
Apache CouchDB 1.3.1 (LogLevel=info) is starting.
Error opening log file /var/log/couchdb/couch.log: permission denied{"init
terminating in
do_boot",{{badmatch,{error,{bad_return,{{couch_app,start,[normal,["/etc/couchdb/default.ini","/etc/couchdb/local.ini"]]},{'EXIT',{{badmatch,{error,{shutdown,{failed_to_start_child,couch_primary_services,{shutdown,{failed_to_start_child,couch_log,{error,"permission
denied","/var/log/couchdb/couch.log"}}}}}}},[{couch_server_sup,start_server,1,[{file,"couch_server_sup.erl"},{line,98}]},{application_master,start_it_old,4,[{file,"application_master.erl"},{line,269}]}]}}}}}},[{couch,start,0,[{file,"couch.erl"},{line,18}]},{init,start_it,1,[]},{init,start_em,1,[]}]}}
2. Running under root:
[root@fab fedpkg]# couchdb
Apache CouchDB 1.3.1 (LogLevel=info) is starting.
Apache CouchDB has started. Time to relax.
[info] [<0.31.0>] Apache CouchDB has started on http://127.0.0.1:5984/
I don't know why this happened, but I think there might have some dirs/files
are operated by incorrect permissions setting.
--
You are receiving this mail because:
You are on the CC list for the bug.
7 years, 6 months