You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Telegraf - version 0.13.1
Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-1 (2016-03-06) x86_64 GNU/Linux
Steps to reproduce:
systemctl start telegraf
Wait until telegraf has fully started (is listening for UDP traffic, is flushing data)
systemctl restart telegraf
Expected behavior:
Telegraf should release the UDP port for re-use before dying. When the next version starts, it should grab the UDP port and start listening for traffic.
Actual behavior:
The UDP port is unable to be grabbed by the new telegraf instance, causing it to die and restart repeatedly until systemd gives up trying to start it.
$ systemctl status telegraf
Aug 17 17:40:48 development-monitoring-influxdb-01234567 systemd[1]: Stopping The plugin-driven server agent for reporting metrics into InfluxDB [website]...
Aug 17 17:40:48 development-monitoring-influxdb-01234567 systemd[1]: Starting The plugin-driven server agent for reporting metrics into InfluxDB [website]...
Aug 17 17:40:48 development-monitoring-influxdb-01234567 systemd[1]: telegraf-website.service start request repeated too quickly, refusing to start.
Aug 17 17:40:48 development-monitoring-influxdb-01234567 systemd[1]: Failed to start The plugin-driven server agent for reporting metrics into InfluxDB [website].
Aug 17 17:40:48 development-monitoring-influxdb-01234567 systemd[1]: Unit telegraf-website.service entered failed state.
On top of this, there is sometimes STILL a telegraf process running, even though systemd says the process has failed to start. It is somehow detached from systemd, but the logs and netstat say that everything is running fine.
Bug report
Relevant telegraf.conf:
System info:
Telegraf - version 0.13.1
Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-1 (2016-03-06) x86_64 GNU/Linux
Steps to reproduce:
systemctl start telegraf
systemctl restart telegraf
Expected behavior:
Telegraf should release the UDP port for re-use before dying. When the next version starts, it should grab the UDP port and start listening for traffic.
Actual behavior:
The UDP port is unable to be grabbed by the new telegraf instance, causing it to die and restart repeatedly until systemd gives up trying to start it.
Additional Info:
On top of this, there is sometimes STILL a telegraf process running, even though systemd says the process has failed to start. It is somehow detached from systemd, but the logs and
netstat
say that everything is running fine.The text was updated successfully, but these errors were encountered: