Closed herver closed 8 years ago
lomik
commented
8 years ago Hi, I need stderr output of crashed go-carbon process for debug.
I suspect there may be some kind of race there
Unlikely. More probability there is an error in the message parser
herver
commented
8 years ago I finally managed to capture stderr of the crashed go-carbon process, please find it attached to this comment. output.txt
lomik
commented
8 years ago 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)
lomik
commented
8 years ago 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 mymachineI 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.