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
Real-time parsing works as not intended v.1.9.1 #2630
Comments
Does this occur when you execute it directly on the machine, without using Docker? |
Standalone goaccess working as intended (with minimum workload). Got some updates: In my initial question i didnt mention one important detail - my access log rotating every 1 hour.
The 1st hour after goaccess started im getting an accurate stats. At the moment the second hour ticks and the access.log has been rotated (access.log inode value is still the same) - then the deviations started to appears.
On the Time Distribution pane
this stats are fine
this stats received in the first 20 mins of a hour and they are NOT correct |
Are you running this using
|
in my docker container im running goaccess like this (as stated in my docker-compose file):
so the log goes directly to goaccess without piping |
does it function properly outside of Docker when passing the log directly? |
Yep, standalone goaccess (outside Docker env) working as intended (with minimum workload). |
Got it. I'm just trying to pinpoint the problem as precisely as possible. So, it seems the issue arises when running via Docker or when piping data in using tail -F, right? If you remove --persist and --restore, does the issue still occur with the real-time counters? Also, are you experiencing the same issues with terminal output? Any additional details would be appreciated so I can attempt to reproduce this on my end. Thanks! |
The issue arises when running via Docker. I can provide you with the docker-compose file im using. Thank you so much for your time. |
Update Time Distribution Pane: Hours from different days overlap each other: |
@H1r0Sh1mA, just to clarify, are you encountering two separate issues? One regarding the real-time problem with Docker and the other regarding the accuracy of the stats numbers? If so, I suggest opening a new issue for the stats so we can address them separately. Regarding the discrepancy with the cum/max/avg time served, it seems like there might be an issue with your log format. Could you share the actual lines from your access log? That would help us investigate further. Thanks |
the log format arguments:
escaping trails (like:
Didnt have a chance yet to test
I am experiencing all these issues in docker environment with real-time parsing mode. To avoid confusion i will open issues one by one separately. |
no updates so far? |
Some questions here...
|
GoAccess ver 1.9.1
Env: docker container
Command:
Problem:
During the real-time parsing goaccess re-parsing the entire log file every time a new record is added, causing it to count all the requests and stats again, including those that were already counted in previous parsing iteration.
Describing in more details:
we have 1 record in access log (total 1 line) -> report returns 1 total/valid request (all stats seems fine)
adding 1 record to access log (total 2 lines) -> report returns 3 total/valid/ requests (goaccess read the log file from the beginning and adding the 1st and the 2d records to the previous iteration)
adding 1 record to access log (total 3 lines) -> report returns 6 total/valid requests (goaccess read the log file from the beginning again and adding all the 3 records to previous iteration)
etc.....
The one shot (no real-time monitoring) execution works as intended.
The text was updated successfully, but these errors were encountered: