-
Notifications
You must be signed in to change notification settings - Fork 125
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
go-carbon crashes when doing deep scan #30
Comments
Hi, I need stderr output of crashed go-carbon process for debug.
Unlikely. More probability there is an error in the message parser |
I finally managed to capture stderr of the crashed go-carbon process, please find it attached to this comment. |
Thanks! The reason is really in a bad message (very big size in header of pickle message). In the near future I will correct it (with limiting max pickle message size) |
Fixed in 0.7-beta4 https://github.com/lomik/go-carbon/releases/tag/v0.7-beta4 Please, reopen issue if this problem persists |
I had go-carbon crash already once or twice in the last weeks, I didn't pay really attention and updated to the latest version (0.7-beta1) and it still occurs.
These are the "bad lines" found in the logs prior to the crash, as you can see this comes from regular security scans that run inside my company's network and are generated by something like
nmap -sV --version-all -p XXXX mymachine
I was able to reproduce this once, but not again after that. I suspect there may be some kind of race there, as go-carbon is running with the following configuration options and receiving ~ 200k metrics.
The text was updated successfully, but these errors were encountered: