Ignition Cached IPs

Ignition
1

Does Ignition cache IPs of DNS entries? I have the following example below where a tag endpoint is communicating with a scada endpoint and it appears to have an old IP address referenced that's being actively used by another service/app outside of Ignition. Why might I see this old IP in the logs?

In addition, if this is holding onto old IP information i.e. if a pod is restarted and grabs a new IP, would this pose problems for backup gateways, and any issues if a backup is restored if it holds that info?

Ignition Version: 8.1.35
App: Containerized Ignition
Runtime: Kubernetes

jvm 1 | 2025/01/14 17:18:13 | I [m.T.W.WebSocketConnection ] [17:18:12]: <- incoming local='paint-tag01' remote='paint-scada-0' method=shutdown: [2146868864] Shutting down connection 'paint-tag01' to http://xx.xx.xx.xx:8088/system: Remote is reconnecting gan-remote-connection-id=7a7f...2d-...b32-47........

2

No, but the JVM does, however it's only ~30 seconds by default.

3

@mgross does GAN do anything funny like resolve a hostname or IP and then use it to format some URL it hangs on to?

4

Yes, it grabs the other side's URL from the incoming connection parameters and assigns it internally. It uses this address to format various logs. The remote URL should reset to the new value as soon as the connection is re-established. Restoring a backup shouldn't cause problems because each gateway is also assigned a unique UUID via the data/.uuid file. This file remains unchanged even after a restoration.