Bug 757836
| Summary: | logconv.pl restarts count on conn=0 instead of conn=1 | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Marc Sauton <msauton> | |
| Component: | 389-ds-base | Assignee: | Rich Megginson <rmeggins> | |
| Status: | CLOSED ERRATA | QA Contact: | Sankar Ramalingam <sramling> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | low | |||
| Version: | 6.3 | CC: | jgalipea, jrusnack, mreynolds, nkinder, rmeggins | |
| Target Milestone: | rc | |||
| Target Release: | 6.4 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | 389-ds-base-1.2.11.12-1.el6 | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: Previously, the logconv.pl script used a connection number equal to 0 as a restart point.
Consequence: logconv.pl reported inaccurate restart counts
Fix: 389 DS uses conn=1 as the restart point
Result: accurate restart stats
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 781495 (view as bug list) | Environment: | ||
| Last Closed: | 2013-02-21 08:16:50 UTC | Type: | --- | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 743970, 781495 | |||
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 |
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: