-
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
[inputs.opcua] Error in plugin: Get Data Failed: Status not OK: Bad (0x80000000) #8871
Comments
Have you solved your problem please? |
No. And nobody has helped to solve it. |
I can reproduce this behavior with the following configuration using the
The good node is skipped, while we would expect to see it in the output. The problem arises from returning the error instead of just logging the error. I'll reference this issue in a commit with an example solution in the near future. |
In commit R290@c931908 I've added the standard telegraf logger and replaced the return error by a I can open a pull request if this is an acceptable solution. |
Relevant telegraf.conf:
N/A
System info:
Windows Server 2012 R2 - Telegraf 1.17
Docker
N/A
Steps to reproduce:
Expected behavior:
Point with Good quality should be read and stored in InfluxDB. Point with Bad quality, not.
Actual behavior:
[inputs.opcua] Error in plugin: Get Data Failed: Status not OK: Bad (0x80000000)
Error in log file.
None of configured points is stored in influxDB, at least, point with Good quality should be stored.
Additional info:
[inputs.opcua] Error in plugin: Get Data Failed: Status not OK: Bad (0x80000000)
The text was updated successfully, but these errors were encountered: