Looks like that one is probably due to bug 1253896.
When 'EOF in transport thread' shows up, 'Dropping user packet because connection is dead' doesn't, so 'Dropping user packet because connection is dead' might be the best to write an e-r query against right now.
Alternatively maybe we could check on "timeout=self.timeout, pkey=self.pkey", that shows up 26 times in the last 7 days, all fails:
I do see these in the console log though:
"Dropping user packet because connection is dead"
That's had 15 hits in the last 7 days:
http:// logstash. openstack. org/#eyJzZWFyY2 giOiJtZXNzYWdlO lwiRHJvcHBpbmcg dXNlciBwYWNrZXQ gYmVjYXVzZSBjb2 5uZWN0aW9uIGlzI GRlYWRcIiBBTkQg ZmlsZW5hbWU6XCJ jb25zb2xlLmh0bW xcIiIsImZpZWxkc yI6W10sIm9mZnNl dCI6MCwidGltZWZ yYW1lIjoiNjA0OD AwIiwiZ3JhcGhtb 2RlIjoiY291bnQi LCJ0aW1lIjp7InV zZXJfaW50ZXJ2YW wiOjB9LCJzdGFtc CI6MTM4Njg4NDM0 ODA1NH0=
Also seeing this:
"EOF in transport thread"
150 hits in the last 7 days on that, 100% fail rates for the builds that shows up in:
http:// logstash. openstack. org/#eyJzZWFyY2 giOiJtZXNzYWdlO lwiRU9GIGluIHRy YW5zcG9ydCB0aHJ lYWRcIiBBTkQgZm lsZW5hbWU6XCJjb 25zb2xlLmh0bWxc IiIsImZpZWxkcyI 6W10sIm9mZnNldC I6MCwidGltZWZyY W1lIjoiNjA0ODAw IiwiZ3JhcGhtb2R lIjoiY291bnQiLC J0aW1lIjp7InVzZ XJfaW50ZXJ2YWwi OjB9LCJzdGFtcCI 6MTM4Njg4NTAxNz A4NX0=
Looks like that one is probably due to bug 1253896.
When 'EOF in transport thread' shows up, 'Dropping user packet because connection is dead' doesn't, so 'Dropping user packet because connection is dead' might be the best to write an e-r query against right now.
Alternatively maybe we could check on "timeout= self.timeout, pkey=self.pkey", that shows up 26 times in the last 7 days, all fails:
http:// logstash. openstack. org/#eyJzZWFyY2 giOiJtZXNzYWdlO lwidGltZW91dD1z ZWxmLnRpbWVvdXQ sIHBrZXk9c2VsZi 5wa2V5XCIgQU5EI GZpbGVuYW1lOlwi Y29uc29sZS5odG1 sXCIiLCJmaWVsZH MiOltdLCJvZmZzZ XQiOjAsInRpbWVm cmFtZSI6IjYwNDg wMCIsImdyYXBobW 9kZSI6ImNvdW50I iwidGltZSI6eyJ1 c2VyX2ludGVydmF sIjowfSwic3RhbX AiOjEzODY4ODUyO TQwNTl9