#177 logconv.pl restarts count on conn=0 instead of conn=1
Closed: wontfix None Opened 10 years ago by rmeggins.

https://bugzilla.redhat.com/show_bug.cgi?id=757836

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:

batch move to 1.2.10.rc1

Pushed to master:

[mareynol@mareynol src]$ git push
Counting objects: 11, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (6/6), 672 bytes, done.
Total 6 (delta 4), reused 0 (delta 0)
To ssh://mreynolds@git.fedorahosted.org/git/389/ds.git
184a57a..ed87077 master -> master

Added initial screened field value.

Metadata Update from @mreynolds:
- Issue assigned to mreynolds
- Issue set to the milestone: 1.2.10.a7

5 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/177

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

2 years ago

Login to comment on this ticket.

Metadata