Regular short getaddrinfo EAI_AGAIN outages

[jdaviescoates]

I recently enabled email notifications on my Uptime Kuma and I've noticed there are regular short outages. Something to do with getaddrinfo EAI_AGAIN

Any idea what's causing this and how to resolve it?

Apparently

EAI_AGAIN is a DNS lookup timed out error, means it is a network connectivity error or proxy related error.

According to https://stackoverflow.com/questions/40182121/whats-the-cause-of-the-error-getaddrinfo-eai-again

Oh, and here it says:

EAI_AGAIN means the DNS server replied that it cannot currently fulfill the request. (If you want the hairy details, the RCODE field in the response is set to 2, SERVFAIL.)

There is no single solution because it entirely depends on why the DNS server sends that back. Maybe it's overloaded, maybe the network is down, maybe it got the same reply from its upstream server.

In general, the best you can do is wait a while and try again. Hope that helps.

I wonder what the specific issue is in my case (perhaps just network issues with Netcup?)

[jdaviescoates]

@jdaviescoates said in Regular short getaddrinfo EAI_AGAIN outages:

perhaps just network issues with Netcup?

I've just created a load of monitors to watch apps I've got on some Hetzner Could VPS servers too. I wonder if I'll see the same issues on there or not...

[girish]

Do you have other domains by any chance? And does this happen only for the coop domain ? Could be a TLD issue that their authoritative servers are flaky.

[jdaviescoates]

@girish said in Regular short getaddrinfo EAI_AGAIN outages:

Do you have other domains by any chance?

Yes, lots.

@girish said in Regular short getaddrinfo EAI_AGAIN outages:

And does this happen only for the coop domain ?

Not sure yet, but shall keep an eye on it.

@girish said in Regular short getaddrinfo EAI_AGAIN outages:

Could be a TLD issue that their authoritative servers are flaky.

Sounds plausible.

[RoundHouse1924]

This is an Uptime Kuma quirk that I solved by upping "Retries" on each affected monitor to at least 2. Just one of my 25 monitors needed retries upping to 5 for a fix.

Hope this helps!

[jdaviescoates]

@RoundHouse1924 Thanks, although surely that could just mean that when it tried once it was broken but by the time it retried it was working again? Although I guess the time between retries is tiny?

[girish]

I went and checked our instances' logs. I found sporadic ENOTFOUND but very spaced out (like months apart).