starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

periodic getaddrinfo EAI_AGAIN #3964

New issue

Closed

opened 2026-02-28 03:46:35 -05:00 by deekerman · 12 comments

deekerman commented

2026-02-28 03:46:35 -05:00

Owner

Originally created by @PikuZheng on GitHub (Feb 11, 2025).

⚠️ Please verify that this question has NOT been raised before.

I checked and didn't find similar issue

🛡️ Security Policy

I agree to have read this project Security Policy

📝 Describe your problem

periodic getaddrinfo EAI_AGAIN with https test (http works fine)

I checked similar issue and confirm it‘s not related to dns or network connection (monitored the dns server - it was always available)

also tried enable or disabled NSCD

📝 Error Message(s) or Log

2025-02-11T09:16:21Z [MONITOR] WARN: Monitor #3 '163(国内网站)': Pending: getaddrinfo EAI_AGAIN www.163.com | Max retries: 1 | Retry: 1 | Retry Interval: 60 seconds | Type: http

🐻 Uptime-Kuma Version

1.23.16

💻 Operating System and Arch

Alpine

🌐 Browser

Chrome 132.0

🖥️ Deployment Environment

Runtime: offical docker image
Database: sqlite
Filesystem used to store the database on: ext4
number of monitors: 7

Originally created by @PikuZheng on GitHub (Feb 11, 2025). ### ⚠️ Please verify that this question has NOT been raised before. - [x] I checked and didn't find similar issue ### 🛡️ Security Policy - [x] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### 📝 Describe your problem periodic getaddrinfo EAI_AGAIN with https test (http works fine) I checked similar issue and confirm it‘s not related to dns or network connection (monitored the dns server - it was always available) ![Image](https://github.com/user-attachments/assets/024c9b91-b018-4c30-8af0-15ed1c402558) also tried enable or disabled NSCD ### 📝 Error Message(s) or Log 2025-02-11T09:16:21Z [MONITOR] WARN: Monitor #3 '163(国内网站)': Pending: getaddrinfo EAI_AGAIN www.163.com | Max retries: 1 | Retry: 1 | Retry Interval: 60 seconds | Type: http ### 🐻 Uptime-Kuma Version 1.23.16 ### 💻 Operating System and Arch Alpine ### 🌐 Browser Chrome 132.0 ### 🖥️ Deployment Environment - Runtime: offical docker image - Database: sqlite - Filesystem used to store the database on: ext4 - number of monitors: 7

deekerman

2026-02-28 03:46:35 -05:00

closed this issue
added the
Stale

help
labels

deekerman commented

2026-02-28 03:46:41 -05:00

Author

Owner

@ganga2166 commented on GitHub (Feb 14, 2025):

@PikuZheng has this issue been resolved?

@ganga2166 commented on GitHub (Feb 14, 2025): @PikuZheng has this issue been resolved?

deekerman commented

2026-02-28 03:46:41 -05:00

Author

Owner

@PikuZheng commented on GitHub (Feb 14, 2025):

Negative ☹️

@PikuZheng commented on GitHub (Feb 14, 2025): Negative ☹️

deekerman commented

2026-02-28 03:46:41 -05:00

Author

Owner

@Coltonomore commented on GitHub (Feb 27, 2025):

I am receiving the same error.

@Coltonomore commented on GitHub (Feb 27, 2025): I am receiving the same error.

deekerman commented

2026-02-28 03:46:41 -05:00

Author

Owner

@igorrl1 commented on GitHub (Mar 7, 2025):

I have the same issue. suddenly the container can't resolve dns queries anymore. The workaround is to set a custom dns on docker.
None of my other containers seem to be affected.

@igorrl1 commented on GitHub (Mar 7, 2025): I have the same issue. suddenly the container can't resolve dns queries anymore. The workaround is to set a custom dns on docker. None of my other containers seem to be affected.

deekerman commented

2026-02-28 03:46:41 -05:00

Author

Owner

@jbehrmusic commented on GitHub (Mar 30, 2025):

having the same issue. uptime kuma won't allow me to setup a webhook for discord

@jbehrmusic commented on GitHub (Mar 30, 2025): having the same issue. uptime kuma won't allow me to setup a webhook for discord

deekerman commented

2026-02-28 03:46:41 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Apr 17, 2025):

Regular debugging step is to enable dns caching in the settings for this issue.
We by default don't cache and some dns servers don't like this => getaddrinfo EAI_AGAIN

If you still get issues with caching enabled, your DNS' TTL-Config might be wrong.

@CommanderStorm commented on GitHub (Apr 17, 2025): Regular debugging step is to enable dns caching in the settings for this issue. We by default don't cache and some dns servers don't like this => `getaddrinfo EAI_AGAIN` If you still get issues with caching enabled, your DNS' TTL-Config might be wrong.

deekerman commented

2026-02-28 03:46:41 -05:00

Author

Owner

@PikuZheng commented on GitHub (Apr 19, 2025):

Tried turning cache on and off, there was improvement but not much. On the other hand, the ttl was 600.
After observing it for a while, I suspect it has something to do with the CPU performance. I would like to know the number of cpu cores (currently 2) and frequency it requires.

@PikuZheng commented on GitHub (Apr 19, 2025): Tried turning cache on and off, there was improvement but not much. On the other hand, the ttl was 600. After observing it for a while, I suspect it has something to do with the CPU performance. I would like to know the number of cpu cores (currently 2) and frequency it requires.

deekerman commented

2026-02-28 03:46:41 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Apr 19, 2025):

We will under the current architecture only use one core.

@CommanderStorm commented on GitHub (Apr 19, 2025): We will under the current architecture only use one core.

deekerman commented

2026-02-28 03:46:41 -05:00

Author

Owner

@huyz commented on GitHub (Jun 2, 2025):

After trying the different built-in caching options, I settled on installing a Technitium DNS caching server and that resolved my frequent EAI_AGAIN errors.

@huyz commented on GitHub (Jun 2, 2025): After trying the different built-in caching options, I settled on installing a Technitium DNS caching server and that resolved my frequent EAI_AGAIN errors. Btw, related issue: https://github.com/louislam/uptime-kuma/issues/3123

deekerman commented

2026-02-28 03:46:41 -05:00

Author

Owner

@PikuZheng commented on GitHub (Jun 2, 2025):

thanks @huyz and I have local dns server with cache and HA but the issue. and other local computers has never seen a dns problem.

@PikuZheng commented on GitHub (Jun 2, 2025): thanks @huyz and I have local dns server with cache and HA but the issue. and other local computers has never seen a dns problem.

deekerman commented

2026-02-28 03:46:41 -05:00

Author

Owner

@github-actions[bot] commented on GitHub (Aug 1, 2025):

We are clearing up our old help-issues and your issue has been open for 60 days with no activity.
If no comment is made and the stale label is not removed, this issue will be closed in 7 days.

@github-actions[bot] commented on GitHub (Aug 1, 2025): We are clearing up our old `help`-issues and your issue has been open for 60 days with no activity. If no comment is made and the stale label is not removed, this issue will be closed in 7 days.

deekerman commented

2026-02-28 03:46:41 -05:00

Author

Owner

@PikuZheng commented on GitHub (Aug 1, 2025):

I believe that beta2 has alleviated this problem. It may also be that the performance is better after I migrated to MySQL.

@PikuZheng commented on GitHub (Aug 1, 2025): I believe that beta2 has alleviated this problem. It may also be that the performance is better after I migrated to MySQL.