Replay Process ends with: "Can not parse request"

[gottwald]

Replay Process ends with: "Can not parse request"

[buger]

Yes, you right. Its recent merge. Fixed.

[gottwald]

So it is normal, that some requests get lost by being not parseable, right?

[buger]

Nope, its definitly not normal. Need to debug why it happen.

[buger]

Actually its ok if some requests not parsed, due nature of RAW sockets, i can loose some packets, but it should be less then 5% of requests.

[gottwald]

The problem is bigger than I thought.
Can't get a single request parsed...
I got a lot of these messages: "malformed HTTP version"

[buger]

Interesting can you get some debugging info, and show actual request that can't be parsed?

[gottwald]

Actually I'm not sure if I'm allowed to. There's some confidential data in there.
But printing out the data variable as a string in the func ParseRequest(data []byte) shows that it sometimes kind of starts in the middle of a request.
Sometime in the middle of the URL, sometimes in the middle of the cookie information and so on.

[buger]

Strange, will be greate if you check that old 0.3.5 version works ok for you... It can be downloaded in "releases" section.

[gottwald]

Took the commit of 0.3.5 and patched it so that the parsing errors get visible like they are now. Same with that version.
So it's definitely not a new problem. It's just visible now.
And it's not all requests. Most of them work.
In the beginning it looked like that were all because no data got into elasticsearch, but that seems like a different problem since refactoring. Will test that too.

[slawosz]

@gottwald What are your replay options? You use one or more hosts to replay on?

[gottwald]

Single replay host without any rate limit