-
-
Notifications
You must be signed in to change notification settings - Fork 49
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
Endless wait loop between threads resulting in go-dnscollector (0.45+) to hang #729
Comments
Thank you for reporting this issue. Could you please provide more details, such as:
|
Many thanks for the quick reply.
(this is the configuration file upgraded for 0.46b) The issue appeared with 0.45.0. In other words, 0.44.0 is the last working version for us. Thanks again! |
Thank for sharing config, Can you share your frstm file ? it will be more easy to reproduce in my side. |
I found the regression, the dnstap packet process is never started... with the ingestor. |
wow, that was quick! Good work @dmachard! I cannot easily share the dnstap file, which is coming from our production systems. Thanks again! |
fix pushed in master branch and release v0.46.0-beta2 |
This is just to confirm that the issue has been fixed successfully starting 0.46.0-beta2. Thank you! |
When upgrading from 0.41 to 0.45/0.46b, go-dnscollector is now hanging when processing files.
The flow works well for tiny fstrm files, but as soon as the file reaches a certain size apparently, this creates a condition between the different threads causing an endless wait loop.
If we take the first 50 000 lines of the file below (dnstap-2024-06-03-19:56:54.fstrm), the file is successfully processed and then deleted.
If we take the first 100 000 lines of the very same file (for a total of 30MB), go-dnscollector will hang whilst processing the file, and never complete this work or subsequently delete it:
Running
strace
at this point will show this loop (note the "Connection timed out"):Trying to exit the go-dnscollector at this point with CTRL+C is also hanging, requiring a full
kill -9
of the process:Just replacing the go-dnscollector 0.45/0.46b binary with version 0.41 "solves" this issue and the fstrm file is processed instantly and then successfully deleted.
The text was updated successfully, but these errors were encountered: