Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1357607

Summary: Update pcp-pmda-ds389log defaults to use dirsrv user instead of nobody
Product: Red Hat Enterprise Linux 7 Reporter: Viktor Ashirov <vashirov>
Component: pcpAssignee: Nathan Scott <nathans>
Status: CLOSED ERRATA QA Contact: Miloš Prchlík <mprchlik>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: brolley, fche, lberk, lmiksik, mbenitez, mgoodwin, mprchlik, myllynen, nathans
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pcp-3.11.3-4.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 04:24:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Viktor Ashirov 2016-07-18 15:46:06 UTC
Description of problem:
Since RHEL7.3 default user for 389-ds is dirsrv instead of nobody.
It would be nice to update defaults for pcp-pmda-ds389log to reflect this change.

/var/lib/pcp/pmdas/ds389log/pmdads389log.pl:28
our $ds_user = 'nobody'; # empty - use root

Version-Release number of selected component (if applicable):
pcp-pmda-ds389log-3.11.3-2.el7.x86_64

Comment 2 Nathan Scott 2016-07-18 20:53:55 UTC
Simple change - does this make sense to you, Marko?  (does log reading require this permission now?)  Thanks.

Comment 3 Marko Myllynen 2016-07-19 09:14:41 UTC
(In reply to Nathan Scott from comment #2)
> Simple change - does this make sense to you, Marko?  (does log reading
> require this permission now?)  Thanks.

The logs are not world-readable so either root or the log-owning user must be used here. I checked latest Fedora and it also uses dirsrv. So I think it'd be a reasonable change (if dirsrv doesn't work everywhere then it's not much different than nobody not working everywhere). Thanks.

Comment 4 Nathan Scott 2016-07-19 21:42:45 UTC
Thanks Marko, I'll get that change pushed through.

Comment 6 Fedora Update System 2016-08-16 01:55:21 UTC
pcp-3.11.4-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-b76275250f

Comment 7 Fedora Update System 2016-08-16 05:16:23 UTC
pcp-3.11.4-1.el5 has been pushed to the Fedora EPEL 5 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-a51156083f

Comment 8 Fedora Update System 2016-08-16 05:56:36 UTC
pcp-3.11.4-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-415f0c78ed

Comment 9 Miloš Prchlík 2016-08-20 15:34:17 UTC
It looks like the patch was not applied to pcp-3.11.3-3.el7:

[root@ibm-x3650m4-01-vm-13 pmdas]# rpm -q pcp-pmda-ds389log
pcp-pmda-ds389log-3.11.3-3.el7.x86_64
[root@ibm-x3650m4-01-vm-13 pmdas]# pwd
/var/lib/pcp/pmdas
[root@ibm-x3650m4-01-vm-13 pmdas]# grep -r 'ds_user =' ds389log/pmdads389log.pl 
our $ds_user = 'nobody'; # empty - use root
[root@ibm-x3650m4-01-vm-13 pmdas]# 

Upstream patch 1f0ee8705d108b628e59746e851f51fd1599190c says:

-our $ds_user = 'nobody'; # empty - use root
+our $ds_user = 'dirsrv'; # empty - use root

Comment 11 Miloš Prchlík 2016-08-31 12:47:15 UTC
Verified with build pcp-3.11.3-4.el7.

Comment 12 Fedora Update System 2016-09-05 19:48:36 UTC
pcp-3.11.4-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.

Comment 13 Fedora Update System 2016-09-05 22:53:13 UTC
pcp-3.11.4-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.

Comment 14 Fedora Update System 2016-09-06 02:19:40 UTC
pcp-3.11.4-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.

Comment 16 errata-xmlrpc 2016-11-04 04:24:10 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2344.html