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 1429770 - ds-logpipe.py crashes for non-existing users
Summary: ds-logpipe.py crashes for non-existing users
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.3
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: mreynolds
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-07 04:13 UTC by Sankar Ramalingam
Modified: 2020-09-13 21:57 UTC (History)
3 users (show)

Fixed In Version: 389-ds-base-1.3.6.1-15.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 21:14:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 2216 0 None None None 2020-09-13 21:56:59 UTC
Red Hat Product Errata RHBA-2017:2086 0 normal SHIPPED_LIVE 389-ds-base bug fix and enhancement update 2017-08-01 18:37:38 UTC

Comment 5 mreynolds 2017-03-07 16:43:20 UTC 
Upstream ticket:
https://pagure.io/389-ds-base/issue/49157
Comment 8 Viktor Ashirov 2017-05-06 06:50:35 UTC 
Build tested:
389-ds-base-1.3.6.1-13.el7.x86_64

It still generates exception (and abrt crash report) when permission is denied.

ds-logpipe.py:315:<module>:Exception: Permission denied [13]

Traceback (most recent call last):
  File "/usr/bin/ds-logpipe.py", line 315, in <module>
    raise Exception("%s [%d]" % (e.strerror, e.errno))
Exception: Permission denied [13]
Comment 10 Viktor Ashirov 2017-05-20 04:02:43 UTC 
Build tested:
389-ds-base-1.3.6.1-14.el7.x86_64

ds-logpipe.py:321:<module>:AttributeError: 'module' object has no attribute 'ext'

Traceback (most recent call last):
  File "/usr/bin/ds-logpipe.py", line 321, in <module>
    sys.ext(1)
AttributeError: 'module' object has no attribute 'ext'


There is a typo on line 321, should be sys.exit(1).
Comment 12 Sankar Ramalingam 2017-05-24 08:53:50 UTC 
Executed namePipelog tests for 389-ds-base-1.3.6.1-15 build and observed that it prints the correct message;
"Failed to create log pipe - Permission denied [error 13]" for test NamedPipe_12. Also, there are no crashes from namedPipelog tests.
Hence, marking the bug as Verified.

Build tested:
[root@bkr-hv03-guest09 ~]# rpm -qa |grep 389-ds
389-ds-base-libs-1.3.6.1-15.el7.x86_64
389-ds-base-1.3.6.1-15.el7.x86_64
Comment 13 errata-xmlrpc 2017-08-01 21:14: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://access.redhat.com/errata/RHBA-2017:2086
Note You need to log in before you can comment on or make changes to this bug.