-
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_listener] 1000 Nodes will get EOF[failed to start monitoring items: EOF] #14568
Comments
Hi, Looking at the upstream gopcua library it seems other users have reported similar issues: gopcua/opcua#531 Does connecting to a single node with security settings work? That would rule out any misconfiguring there. |
Hi powersj Connecting to a single node with security settings works fine. Thanks |
I have put up #14595 which enables the opcua client debug logger. can you please download an artifact from that PR and run with it? Please provide the collected logs. Thanks edit: You will need to set two things to get the additional messages: 1 - debug in the agent via |
@powersj Thanks |
Nothing there stands out to me, but I'm not an OPCUA expert. Please create a discussion with the gopcua upstream project and ask there. |
Hello! I am closing this issue due to inactivity. I hope you were able to resolve your problem, if not please try posting this question in our Community Slack or Community Forums or provide additional details in this issue and reqeust that it be re-opened. Thank you! |
Relevant telegraf.conf
Logs from Telegraf
System info
Telegraf 1.29.0 ,docker 24.0.2, IGS OPCUA
Docker
No response
Steps to reproduce
...
Expected behavior
start monitoring items success
Actual behavior
failed to start monitoring items: EOF
Additional info
Telegraf Logs
When I cancel the use of security settings, I can configure 20000 NodeID.
The text was updated successfully, but these errors were encountered: