Restoring remote connection

[marcoc610]

I am running the exporter on a dedicated system that connects to a remote IBM i and the collection works.

When the i system was restarted, the collection stopped and did not start again.

During the restart, the exporter logs
"ERROR!! ABORTING COLLECTION!! Cause: Communication link failure. (Connection was dropped unexpectedly.)"

After the i was up again, the exporter logs
"ERROR!! ABORTING COLLECTION!! Cause: The connection does not exist."

The workaround, that I found, is to look for that messages in the logs (every 5 minuutes or so) and restart the exporter.
Is there any way to let the exporter try to restore the connection, if it is lost?

[ThePrez]

That's definitely a reasonable enhancement request! We will queue it up

[DDULDDUCK]

That's definitely a reasonable enhancement request! We will queue it up

I'm also experiencing this Communication link failure issue. In our environment, this happens reliably every night, and we've traced the cause to our scheduled database backup on our IBM i (AS400) system.

During the backup process, connections are temporarily locked or dropped. The main problem is that the exporter doesn't seem to recover the connection automatically after the database becomes available again, requiring a manual restart.

Has there been any progress on a solution for this? A feature like a validationQuery to test and re-establish stale connections would be a perfect fix. Is there any known workaround for this currently?

Thanks for your great work on this tool.