Skip to content
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

Logresolvemerge.pl can misorder log lines #232

Open
nielsb opened this issue Apr 17, 2023 · 0 comments
Open

Logresolvemerge.pl can misorder log lines #232

nielsb opened this issue Apr 17, 2023 · 0 comments

Comments

@nielsb
Copy link

nielsb commented Apr 17, 2023

logresolvemerge is very helpful in detecting different time formats without help. Unfortunately it also can be confused by log contents. The following has hit us a couple of times the last month or so, causing logresolvemerge to pick the wrong time information

The following log line

138.201.23.68 - - [28/Mar/2023:02:08:55 +0200] "GET / HTTP/1.1" 200 197475 "https://www.uni-erfurt.de/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_0; rv:1.9.3.20) Gecko/3764-11-07 02:32:07 Firefox/3.8"

makes logresolvemerge select the time as "3764-11-07 02:32:07" causing the rest of this file to be retained until all other files have been emptied, and then to be dropped by awstats because of wrong order.

I have fixed the problem for us by flipping the two first time match lines, because we only handle Apache common log, but the proper solution will require copying part of the LogFormat logic from awstats.pl to logresolvemerge.pl

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant