Skip to content
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

Sometimes monitors get bogged down #1621

Closed
2 tasks done
Nuklon opened this issue May 6, 2022 · 5 comments
Closed
2 tasks done

Sometimes monitors get bogged down #1621

Nuklon opened this issue May 6, 2022 · 5 comments
Labels
bug Something isn't working

Comments

@Nuklon
Copy link

Nuklon commented May 6, 2022

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

  • I checked and didn't find similar issue

🛡️ Security Policy

Description

I have two HTTPs monitors for the same site, exactly the same parameters except one is checking every 30 seconds, and the other every minute.

This just happened for the 1 minute site:
image

The 30 second site is all good:
image

It also happens the other way (i.e., 30s gets bogged down whereas 1m shows no faults).

👟 Reproduction steps

Add two sites, dockerized, one with 1m and one with 30s.

👀 Expected behavior

This shouldn't happen.

😓 Actual Behavior

Occassional bogged down monitors

🐻 Uptime-Kuma Version

1.15.1 (also happened with previous versions)

💻 Operating System and Arch

Docker

🌐 Browser

Firefox 100

🐋 Docker Version

Latest docker-win.

🟩 NodeJS Version

No response

📝 Relevant log output

No response

@Nuklon Nuklon added the bug Something isn't working label May 6, 2022
@Saibamen
Copy link
Contributor

Saibamen commented May 8, 2022

FYI @chakflying

@chakflying
Copy link
Collaborator

chakflying commented May 10, 2022

Tested a bit but cannot reproduce. I suspect it has something to do with how the DNS gets limited queries, which #1598 should fix.

@Nuklon
Copy link
Author

Nuklon commented May 10, 2022

Tested a bit but cannot reproduce. I suspect it has something to do with how the DNS gets limited queries, which #1598 should fix.

I have three separate sites with this issue (all have 30s and 1m monitors). One site uses Cloudflare DNS and other two Gandi.

The console print in docker isn't that useful, probably.

uptime-kuma-uptime-kuma-1  | 2022-05-10T09:03:20.912Z [MONITOR] WARN: Monitor #8 'site.name - 30s': Pending: timeout of 48000ms exceeded | Max retries: 2 | Retry: 1 | Retry Interval: 30 seconds | Type: http

@Nuklon
Copy link
Author

Nuklon commented May 11, 2022

I've double checked by also adding a monitor of IP address and it has the same problem, so it's not DNS related.

@Nuklon
Copy link
Author

Nuklon commented Nov 30, 2022

Seems to be fixed by latest Windows update, so closing.

@Nuklon Nuklon closed this as completed Nov 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants