-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Using [[inputs.sqlserver]] causes segfault after updating telegraf to v. 1.2.0 #2317
Comments
how do you know it's related to the sqlserver plugin? does it happen immediately or after some time? |
A1. If [inputs.sqlserver] is commented out, telegraf.service starts and runs OK. A2. It happens immediately as you can see in the log: |
I can confirm that i am encountering this issue as well on two SQL SERVER instances. Problem on Windows 2012 server, Telegraf version 1.2.0. |
I confirm too, i running telegraf and influxDB on Debian 8. for information with this: https://github.com/zensqlmonitor/influxdb-sqlserver i have no error. |
Bug report
After updating TICK from prev. v. to v.1.2.0 telegraf.service exited with error, please see log in "Additional info" below.
Relevant part of telegraf.conf:
# Read metrics from Microsoft SQL Server
[[inputs.sqlserver]]
interval = "60s"
servers = [
"Server=wks2382;Port=1433;User Id=telegraf;Password=somePassw;app name=telegraf;log=1;",
]
Other content in the config is unchanged.
System info:
Linux osboxes 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
telegraf version 1.2.0, influxdb v. 1.2.0.
Steps to reproduce:
Expected behavior:
Actual behavior:
Additional info:
The text was updated successfully, but these errors were encountered: