Closed theredcat closed 8 years ago
And i can confirm that the process is stuck in CPU user mode since the only SIG working is a SIGKILL (kill -9)
Your first issues seems to be similar/identical to https://github.com/christiangalsterer/execbeat/pull/1 and I try to look into it in the next days.
On the multiple socket items I need to check first.
@theredcat: I have committed some changes to master. HTTP connections are now reused. The looping problem I was not able reproduce. Can you maybe retry with latest version on master?
It works now! I'll let it run few days before putting it in prod ;-)
Running for 10 days, with 30 checks "@every 1m" and everythink is fine.
Sounds like a very thorough test ;-) Thanks for your support. The change is released in 1.0.1
Hello,
I have a infinite loop problem when running httpbeat. It occurs randomly, but faster (10-15sec) using logstash output. With file output it seem to run longer (3-4 min) but ultimatly start to loop. The CPU is then stuck at 100% User.
I've seen that on libbeat that may be related : https://github.com/elastic/beats/issues/878
Maybe you can update the lib version in dependencies ? I'm new to Go and I'm not sure how to do this.
I'm on debian Jessie, up to date, Go 1.5.1 x64
Here is my test config
A strace doesn't help at all, the main process is stuck on a system futex call and the third thread is in pure user mode so strace doesn't help here.
Here is the lsof output. I'm testing HTTPBeat monitoring my elasticsearch cluster (es:9200/_cluster/stats) so the es-03.my.tld are connections to ES by httpbeat for checks. I'm not using httpbeat ES output. I'm pretty surprised to see more that one HTTP connection to the es-03 server since there is only one check at a time. Maybe a non-closed socket here ?