Telegraf ping plugin issue

Amit_Kumar_Singh · May 13, 2019, 11:16am

We are using latest version of ping plugin and we use about 1000 ip to ping once in every 5 min, but when we see the logs we see alot of logs like below.
> 2019-05-13T10:45:28Z E! [inputs.ping]: Error in plugin: host 10.20.6.127: signal: killed

2019-05-13T10:45:28Z E! [inputs.ping]: Error in plugin: host 10.20.6.13: signal: killed
2019-05-13T10:45:28Z E! [inputs.ping]: Error in plugin: host 10.20.6.14: signal: killed
2019-05-13T10:45:28Z E! [inputs.ping]: Error in plugin: host 10.20.6.15: signal: killed
2019-05-13T10:45:28Z E! [inputs.ping]: Error in plugin: host 10.20.6.83: signal: killed
2019-05-13T10:45:28Z E! [inputs.ping]: Error in plugin: host 10.20.6.10: signal: killed
2019-05-13T10:45:28Z E! [inputs.ping]: Error in plugin: host 10.20.6.11: signal: killed
2019-05-13T10:45:30Z E! [inputs.ping]: Error in plugin: host 10.1.7.46: signal: killed

It is not related to file limit as i have set it to 65000. OS is RHEL7

MarcV · May 13, 2019, 12:54pm

Hi Amit_Kumar_Singh ,

this seems related to a bug …

github.com/influxdata/telegraf

input.ping randomly killed with large number of urls

opened 07:19AM - 26 Feb 19 UTC

closed 09:13PM - 12 Sep 19 UTC

eimamagi

bug

### Relevant telegraf.conf: We are monitoring around 1000 URLs: **cat /etc/t…elegraf/telegraf.d/ping.conf** [[inputs.ping]] urls = ["host1"] ping_interval = 60.0 ... [[inputs.ping]] urls = ["host1000"] ping_interval = 60.0 We have increased number of opened files as recommended here https://github.com/influxdata/telegraf/issues/5459. ### System info: **cat /etc/redhat-release** CentOS Linux release 7.5.1804 (Core) **uname -a** Linux mon 3.10.0-862.11.6.el7.x86_64 #1 SMP Tue Aug 14 21:49:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux **rpm -q telegraf** telegraf-1.9.2-1.x86_64 ### Steps to reproduce: 1. systemctl start telegraf 2. we find errors in syslog for random hosts which are working fine: Feb 26 07:59:36 mon telegraf: 2019-02-26T06:59:36Z E! [inputs.ping]: Error in plugin: host host9: signal: killed Feb 26 07:59:36 mon telegraf: 2019-02-26T06:59:36Z E! [inputs.ping]: Error in plugin: host host900: signal: killed ### Expected behavior: Ping plugin documentation doesn't have any limits defined so we expected that pinging 1000 or so addresses from one host shouldn't be a problem. ### Actual behavior: Pings for random hosts which are working fine are killed and return result code <> 0. ### Additional info: [Include gist of relevant config, logs, etc.]

best regards ,

Topic		Replies	Views
Telegraf inputs.ping Telegraf	4	1813	February 22, 2018
Inputs.ping method= native Telegraf telegraf	1	834	September 9, 2021
[inputs.ping] Error in plugin: , exit status 3221225794: X.X.X.X	4	619	May 19, 2021
Ping telegraf plugin possible issue telegraf	18	4832	August 15, 2017
TELEGRAF ping plugin - best practices Telegraf telegraf	0	47	September 4, 2024

Telegraf ping plugin issue

Related topics