-
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
OPCUA Plugin crashes Telegraf (again) #13834
Comments
Hi,
As the error message states, you have not provided the client with anything to do. There is no nodes or groups to montior. That said, we should catch this during the |
Thank you, the crash is quite bad for production but atleast your hint for the missing config fixed my issue. For future reference; although its not explicitly written in the example config many lines of the config are necessary
|
Many? |
Provides a check to a user's config to ensure that they have provided a group and or root node to collect data from. fixes: influxdata#13834
Excuse my generalization, telegraf is an impressive feat with extreme amounts of options. I was referring to the missing error catching around the whole opcua plugin, as mentioned in other issues, as well as the exit on error ( discussed #11313 (comment) and here #10694 (comment) ) . I will correct this. Although the fact that Telegraf crashes the plugin meets an error persists, i would agree to close this issue now. |
Relevant telegraf.conf
Logs from Telegraf
System info
Telegraf 1.27.4, Docker version 20.10.17, build 100c701
Docker
influxdata/influxdata-docker#703
Steps to reproduce
Start my docker compose.
Expected behavior
Collections of metrics from the opcua server
Actual behavior
Error in plugin: registering nodes failed: There was nothing to do because the client passed a list of operations with no elements. StatusBadNothingToDo (0x800F0000)
Telegraf crashes
Additional info
Same fault, but because of un and replugging of the network connection here:
#13260
Similar fault, solved by downgrading (doesnt work):
#10140
The text was updated successfully, but these errors were encountered: