-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorect message "getaddrinfo ENOTFOUND" on 4xx sites #4765
Comments
What is a DNS header?
Most commonly, this issue is caused by you using a DNS resolver which does not like the level of DNS requests it is getting.
Longhorn is not ext4. Warning Filesystem support for POSIX file locks is required to avoid SQLite database corruption. Be aware of possible file locking problems such as those commonly encountered with NFS. Please map the |
You stripped to much, to get right response with 2xx code I needed to configure DNS zone in core dns service in kubernetes as well as some auth headers for that site. First step should allow to resolve ip correctly and get 4xx response, second changes that into 2xx code.
It's ReadWriteOnce, in attached pod stat returns overlayfs for data directory, |
I think you overlooked the section on |
Is this error for DNS only or also for 404? |
The About the other issue you are having: What is true is that we will not consider |
📑 I have found these related issues/pull requests
I found many issues regarding faulty dns, but not something like this,
🛡️ Security Policy
Description
I needed to add monitor for site that required both dns and auth headers,
First status I got was:
Offline | 2024-05-15 11:02:03 | getaddrinfo ENOTFOUND test.xyz
That indicates DNS problem and I changed several things to get it to work, still there was same error
I logged into console and checked several things, node was able to resolve site now perfectly, so I was sure that this is not an issue now.
Then I modified monitor to accept 4xx codes as OK so it logged:
Online | 2024-05-15 14:42:10 | 404 - Resource Not Found
At this point I was sure that requests were ok, but missing auth headers, I removed 4xx codes as ok and got this message:
Offline | 2024-05-15 14:42:23 | Request failed with status code 404
While both - DNS and 4xx code is problem I think that system should report last message as it is so it describes real problem.
👟 Reproduction steps
Probably only online/offline changes are reflected in messages, so returning 404 and shortly after that 401 will log only first one.
👀 Expected behavior
It should display latest response indicating problem, here it should give me 4xx code when dns was working so I don't debug this area.
😓 Actual Behavior
First message classified as error is logged
🐻 Uptime-Kuma Version
latest from helm chart - 1.23.11
💻 Operating System and Arch
kubernetes
🌐 Browser
all
🖥️ Deployment Environment
📝 Relevant log output
The text was updated successfully, but these errors were encountered: