You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I'm running this exporter as a container next to our kamailio container on AWS and it looks like the the timeout is not respected.
For example:
Results in the following log entry:
The connection is refused, because the kamailio container was still starting up at that time:
I'm using the following command syntax:
I'm not in any way proficient with Go, so no idea where it might be going wrong.
If I bootup a different container or EC2 instance with the binary the connection works without a timeout if the kamailio is booted completely.
The text was updated successfully, but these errors were encountered:
Hi,
I'm running this exporter as a container next to our kamailio container on AWS and it looks like the the timeout is not respected.
For example:
Results in the following log entry:
The connection is refused, because the kamailio container was still starting up at that time:
I'm using the following command syntax:
I'm not in any way proficient with Go, so no idea where it might be going wrong.
If I bootup a different container or EC2 instance with the binary the connection works without a timeout if the kamailio is booted completely.
The text was updated successfully, but these errors were encountered: