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.

Description of problem:

It seem like the first connection is always conn=1, not conn=0 as expected in the /usr/bin/logconv.pl tool at line 1151:

if (m/ conn=0 fd=/){$restarts++}

so the tool misses the restarts in the report:
----------- Access Log Output ------------

Restarts:                     0


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

RHDS 8.2 and

        389-Directory/1.2.9.13 B2011.281.321
        ca1.example.com:389 (/etc/dirsrv/slapd-ca1)

[19/Oct/2011:18:59:14 -0400] conn=1 fd=64 slot=64 connection from ::1 to ::1


How reproducible:
always

Steps to Reproduce:
1. grep conn=0 /var/log/dirsrv/access*
2. grep -A 4 389-D /var/log/dirsrv/slapd-ca1/access*
3. logconv.pl -V ./access > ./access.logconv.pl.txt

  
Actual results:
----------- Access Log Output ------------

Restarts:                     0


Expected results:


Additional info:

Upstream ticket:
https://fedorahosted.org/389/ticket/177

marking as screened because it has been cloned upstream

Test coverage :: logconv.sh (logconv01)

[jrusnack@dstet 6.0]$ grep "conn=0" /var/log/dirsrv/slapd-dstet/access
[jrusnack@dstet 6.0]$ echo $?
1

[jrusnack@dstet 6.0]$ rpm -qa | grep 389
389-ds-base-1.2.11.15-2.el6.x86_64

Verified.

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.

http://rhn.redhat.com/errata/RHSA-2013-0503.html