-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
logconv.pl does not correctly show "Peak Concurrent Connections" after log format changes in 389ds v2.1 #5640
Comments
Description: Some of the "closed" m,essages inteh access log are now a mixed case, and logconv should be able to process it. relates: 389ds#5640 Reviewed by: jchapman & tbordaz (Thanks!!)
Description: Some of the "closed" m,essages inteh access log are now a mixed case, and logconv should be able to process it. relates: #5640 Reviewed by: jchapman & tbordaz (Thanks!!)
Description: Some of the "closed" m,essages inteh access log are now a mixed case, and logconv should be able to process it. relates: #5640 Reviewed by: jchapman & tbordaz (Thanks!!)
Description: Some of the "closed" m,essages inteh access log are now a mixed case, and logconv should be able to process it. relates: #5640 Reviewed by: jchapman & tbordaz (Thanks!!)
Description: Some of the "closed" m,essages inteh access log are now a mixed case, and logconv should be able to process it. relates: #5640 Reviewed by: jchapman & tbordaz (Thanks!!)
Description: Some of the "closed" m,essages inteh access log are now a mixed case, and logconv should be able to process it. relates: #5640 Reviewed by: jchapman & tbordaz (Thanks!!)
This commit resolves the problem only partially (probably only cleanly closed connections are counted as closed). As i said in the first message, the commit 26a1e0c has replaced the log file keyword "closed" by "Disconnect". The values of "Peak Concurrent Connections" on our production servers are about 600-800, while the new logconv.pl still displays about 3000-4000. Here are the changes that take into account the replacement of the keyword in addition to case sensitivity of the word "closed":
|
Sorry @aivanov389 I'll get this fixed right away... |
Description: Some of the "closed" messages have been replaced by "disconnect" The tool needs to handles these changes relates: 389ds#5640 Reviewed by: spichugi(Thanks!)
Description: Some of the "closed" messages have been replaced by "disconnect" The tool needs to handles these changes relates: #5640 Reviewed by: spichugi(Thanks!)
Description: Some of the "closed" messages have been replaced by "disconnect" The tool needs to handles these changes relates: #5640 Reviewed by: spichugi(Thanks!)
Description: Some of the "closed" messages have been replaced by "disconnect" The tool needs to handles these changes relates: #5640 Reviewed by: spichugi(Thanks!)
Description: Some of the "closed" messages have been replaced by "disconnect" The tool needs to handles these changes relates: #5640 Reviewed by: spichugi(Thanks!)
Description: Some of the "closed" messages have been replaced by "disconnect" The tool needs to handles these changes relates: #5640 Reviewed by: spichugi(Thanks!)
Issue Description
logconv.pl does not correctly show "Peak Concurrent Connections" after log format changes in #5029 . It does not detect correctly the "Disconnect - Cleanly Closed Connection - U1" string used now in logs instead of "closed error - U1".
Steps to Reproduce
Steps to reproduce the behavior:
Expected results
The number of "Peak Concurrent Connections" should be minimal for a low-activity server. logconv.pl insteads shows a huge number since it considers all the opened connections in access log as concurrent. The reason is the incorrect way to detect when they are closed.
How to Fix
One of the possibilities is to make the "connection closed" event detection case-insensitive.
There may be other side effects since in #5029 the word "closed" was replaced by "Disconnect"
The text was updated successfully, but these errors were encountered: