Debian Server Telegraf Docker Container fails to connect to OPCUA while Ubuntu Machine connects #15325
Labels
bug
unexpected problem or unintended behavior
Comments
If you are able to successfully connect from one server, but not another then this points at something in networking getting in the way not Telegraf. Telegraf is produed as a static binary, so the binaries and libraries themselves are exactly the same. My suggestion is to set If you get additional data, such that you resolve the issue, you should post this here so others can learn from it or we can determine if the docs need updating. |
|
I tried to add the tracing, but it does not work. The working ping and accessible port makes me believe that the networking is alright, but maybe it isnt... |
telegraf-tiger
bot
removed
the
waiting for response
This is not the same version you said you were using in your report That option is only available in newer versions. |
|
Thank you for the quick answer, i will investigate further. |
telegraf-tiger
bot
removed
the
waiting for response
|
Sorry for the wait, was finally able to get to it. the client trace shows the origin of the EOF i guess meanwhile locally it works even with 1.30.2 the important lines to me are: meanwhile locally it works: |
telegraf-tiger
bot
removed
the
waiting for response
locally vs in docker
is that a hint? |
Also reproducible with the opcua_listener plugin |
|
I got it to work! causes the telegraf instance to reconnect. I while i am happy gopcua exists, it doesnt seem stable to me. |
Thanks for following up and sharing what the root cause was.
The listener only listens so in general it ignores the Telegraf interval. There is the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Relevant telegraf.conf
Logs from Telegraf
System info
Telegraf 1.30.2, Debian GNU/Linux 12 (bookworm), Docker version 25.0.3, build 4debf41
Docker
No response
Steps to reproduce
1.Start the docker-compose on the Debian Server
2.Check the logs
3.See that it cant connect to the opcua server
Expected behavior
On my local Pc (Ubuntu 22.04.4 LTS, Docker version 25.0.3, build 4debf41, Telegraf 1.30.2) this config works as expected.
It fails once but succeeds then.
This should also happen on the Debian Server.
Actual behavior
The Telegraf Docker Container on the Debian server fails to connect.
Additional info
The OPCUA server can be pinged from the Debian server.
ping 192.168.82.220
PING 192.168.82.220 (192.168.82.220) 56(84) bytes of data.
64 bytes from 192.168.82.220: icmp_seq=1 ttl=255 time=0.418 ms
64 bytes from 192.168.82.220: icmp_seq=2 ttl=255 time=0.406 ms
nc -zv 192.168.82.220 4840
192.168.82.220: inverse host lookup failed: Unknown host
(UNKNOWN) [192.168.82.220] 4840 (?) open
The text was updated successfully, but these errors were encountered: