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
Running 'C:\\opt\\telegraf\\telegraf.exe --config C:\\opt\\telegraf\\telegraf.conf --config-directory C:\\opt\\telegraf\\conf.d --test either within Powershell remoting or viia. SaltStack provides the following error: 2017/10/26 22:23:02 E! The service process could not connect to the service controller. Running other flags, eg. --version works.
Relevant telegraf.conf:
Number of win_perf_counters
System info:
Telegraf v1.4.1 (git: release-1.4 2de7aa2)
Windows
hi,
i'm seeing this issue on Windows Telegraf version 1.9.1.
"C:\Program Files\Telegraf\telegraf.exe --test" returns
"2018/12/17 00:32:39 E! The service process could not connect to the service controller."
while
"C:\Program Files\Telegraf\telegraf.exe --version"
works fine.
Can you kindly let me know if this will be fixed?
Thank you!
Bug report
Running
'C:\\opt\\telegraf\\telegraf.exe --config C:\\opt\\telegraf\\telegraf.conf --config-directory C:\\opt\\telegraf\\conf.d --test
either within Powershell remoting or viia. SaltStack provides the following error:2017/10/26 22:23:02 E! The service process could not connect to the service controller.
Running other flags, eg.--version
works.Relevant telegraf.conf:
Number of win_perf_counters
System info:
Telegraf v1.4.1 (git: release-1.4 2de7aa2)
Windows
Expected behavior:
Config is tested, printing to stdout.
Actual behavior:
Error:
Telegraf v1.4.1 (git: release-1.4 2de7aa23d7d3c3bcf639d417129ab7c17d83399b)
Use case: [Why is this important (helps with prioritizing requests)]
Auto-validation with config-management.
The text was updated successfully, but these errors were encountered: