Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 1013900

Summary:	logconv: some stats do not work across server restarts
Product:	Red Hat Enterprise Linux 7	Reporter:	Nathan Kinder <nkinder>
Component:	389-ds-base	Assignee:	Rich Megginson <rmeggins>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Sankar Ramalingam <sramling>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	jgalipea, nkinder, rmeggins, srkrishn
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	389-ds-base-1.3.1.6-6.el7	Doc Type:	Bug Fix
Doc Text:	Cause: logconv.pl did not handle server restarts very well. When the server restarts, the connection counter is reset. Any data associated with the old connection number is lost. Consequence: Some statistics are not calculated correctly or at all if logconv.pl detects a server restart. Fix: Index statistics by a tuple of (restartnum,connid,opid) where restartnum is the Nth restart, connid is the connection ID during that start period, and opid is the ID of the operation on that connection. Result: All statistics are calculated correctly no matter how many server restarts are detected by logconv.pl	Story Points:	---
Clone Of:	1013165	Environment:
Last Closed:	2014-06-13 12:02:04 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:	1013165
Bug Blocks:

Description Nathan Kinder 2013-10-01 02:25:06 UTC

+++ This bug was initially created as a clone of Bug #1013165 +++

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47533

logconv keeps most stats in hashes keyed on connid,opid.  These are not unique - the server resets conn=1 upon restart.  logconv needs to keep unique stats across restarts.

Comment 2 srkrishn@redhat.com 2014-01-31 12:44:59 UTC

hi,
i verified the bug and the updated logconv.pl script performs properly even if the server restarts.i cannot mark it as verified,hence Sankar will handle it.

Comment 3 Sankar Ramalingam 2014-02-01 02:19:07 UTC

Based on the notes from Sriram and automated test execution, marking the bug as Verified.

Build tested - 389-ds-base-1.3.1.6-15

Automated tests in ./logfile/logconv.sh
Test - logconv01

Comment 4 Ludek Smid 2014-06-13 12:02:04 UTC

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.