Bug 1474100 - Use of uninitialized value in string ne at /usr/bin/logconv.pl
Use of uninitialized value in string ne at /usr/bin/logconv.pl
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base (Show other bugs)
Unspecified Unspecified
low Severity low
: rc
: ---
Assigned To: mreynolds
Viktor Ashirov
Depends On:
  Show dependency treegraph
Reported: 2017-07-23 17:19 EDT by Viktor Ashirov
Modified: 2018-04-10 10:19 EDT (History)
3 users (show)

See Also:
Fixed In Version: 389-ds-base-
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2018-04-10 10:18:12 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0811 None None None 2018-04-10 10:19 EDT

  None (edit)
Description Viktor Ashirov 2017-07-23 17:19:54 EDT
Description of problem:
The following snippet from access log produces error before outputting log stats:

[23/Jul/2017:22:04:38.941421026 +0200] conn=26261 fd=121 slot=121 connection from to
[23/Jul/2017:22:04:38.941527375 +0200] conn=26261 op=0 BIND dn="cn=Directory Manager" method=128 version=3
[23/Jul/2017:22:04:38.941603992 +0200] conn=26261 op=0 RESULT err=0 tag=97 nentries=0 etime=0 dn="cn=directory manager"
[23/Jul/2017:22:04:38.941695466 +0200] conn=26261 op=1 UNBIND
[23/Jul/2017:22:04:38.941709197 +0200] conn=26261 op=1 fd=121 closed - U1

Use of uninitialized value in string ne at /usr/bin/logconv.pl line 2565, <$LOGFH> line 4

Version-Release number of selected component (if applicable):

Additional info:
Regression was introduced in a fix for https://bugzilla.redhat.com/show_bug.cgi?id=1111400, upstream: https://pagure.io/389-ds-base/issue/48681
Comment 5 Viktor Ashirov 2017-11-06 08:47:38 EST
Build tested:

No errors in the output, marking as VERIFIED.
Comment 8 errata-xmlrpc 2018-04-10 10:18:12 EDT
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.


Note You need to log in before you can comment on or make changes to this bug.