starred/uptime-kuma

Fork 0

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

Maintenance not working #2150

New issue

Open

opened 2026-02-28 02:44:40 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-28 02:44:40 -05:00

Owner

Originally created by @hanyuwei70 on GitHub (Apr 29, 2023).

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

I checked and didn't find similar issue

🛡️ Security Policy

I agree to have read this project Security Policy

Description

I have set up one maintenance using these settings.

but when maintenance window should work, it still send me alerts.

This issue happened after I updated from 1.21.0 to 1.21.2 (not very sure)

👟 Reproduction steps

Described above

👀 Expected behavior

Not raise any alerts

😓 Actual Behavior

Raise alters even in maintenance window.

🐻 Uptime-Kuma Version

1.21.2

💻 Operating System and Arch

Arch Linux

🌐 Browser

Edge

🐋 Docker Version

23.0.1

🟩 NodeJS Version

No response

📝 Relevant log output

2023-04-29T03:00:00+08:00 [MAINTENANCE] INFO: Maintenance id: 1 is under maintenance now
2023-04-29T03:01:53+08:00 [MONITOR] WARN: Monitor #4 '<redacted>': Pending: connect ETIMEDOUT 172.67.145.23:443 | Max retries: 3 | Retry: 1 | Retry Interval: 300 seconds | Type: http
Worker for job "clear-old-data" online undefined
2023-04-29T03:14:01+08:00 [PLUGIN] WARN: Warning: In order to enable plugin feature, you need to use the default data directory: ./data/
2023-04-29T03:14:01+08:00 [DB] INFO: Data Dir: data/
2023-04-29T03:14:02+08:00 [DB] INFO: SQLite config:
[ { journal_mode: 'wal' } ]
[ { cache_size: -12000 } ]
2023-04-29T03:14:02+08:00 [DB] INFO: SQLite Version: 3.41.1
{
  name: 'clear-old-data',
  message: 'Data deletion has been disabled as period is less than 1. Period is 0 days.'
}
{ name: 'clear-old-data', message: 'done' }
2023-04-29T03:26:04+08:00 [MONITOR] WARN: Monitor #14 '<redacted>': Pending: Request failed with status code 502 | Max retries: 3 | Retry: 1 | Retry Interval: 60 seconds | Type: http
2023-04-29T03:27:04+08:00 [MONITOR] WARN: Monitor #14 '<redacted>': Pending: Request failed with status code 502 | Max retries: 3 | Retry: 2 | Retry Interval: 60 seconds | Type: http
2023-04-29T03:28:05+08:00 [MONITOR] WARN: Monitor #14 '<redacted>': Pending: Request failed with status code 502 | Max retries: 3 | Retry: 3 | Retry Interval: 60 seconds | Type: http
2023-04-29T03:29:13+08:00 [MONITOR] WARN: Monitor #4 '<redacted>': Pending: connect ETIMEDOUT 104.21.79.107:443 | Max retries: 3 | Retry: 1 | Retry Interval: 300 seconds | Type: http
2023-04-29T03:29:14+08:00 [MONITOR] WARN: Monitor #14 '<redacted>': Failing: Request failed with status code 502 | Interval: 60 seconds | Type: http | Down Count: 0 | Resend Interval: 0
2023-04-29T03:30:15+08:00 [MONITOR] WARN: Monitor #14 '<redacted>': Failing: Request failed with status code 502 | Interval: 60 seconds | Type: http | Down Count: 0 | Resend Interval: 0
2023-04-29T03:31:16+08:00 [MONITOR] WARN: Monitor #14 '<redacted>': Failing: Request failed with status code 502 | Interval: 60 seconds | Type: http | Down Count: 0 | Resend Interval: 0
2023-04-29T03:32:16+08:00 [MONITOR] WARN: Monitor #14 '<redacted>': Failing: Request failed with status code 502 | Interval: 60 seconds | Type: http | Down Count: 0 | Resend Interval: 0

Originally created by @hanyuwei70 on GitHub (Apr 29, 2023). ### ⚠️ Please verify that this bug 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) ### Description I have set up one maintenance using these settings. ![image](https://user-images.githubusercontent.com/5236679/235297270-78b3aa65-757a-42d6-845e-852fca8d04ed.png) but when maintenance window should work, it still send me alerts. ![image](https://user-images.githubusercontent.com/5236679/235297315-a6d73f47-c92d-42e6-a8d3-7995c6e6edc7.png) ![image](https://user-images.githubusercontent.com/5236679/235297590-8f14379d-8d11-417d-8251-dc18d944d791.png) This issue happened after I updated from 1.21.0 to 1.21.2 (not very sure) ### 👟 Reproduction steps Described above ### 👀 Expected behavior Not raise any alerts ### 😓 Actual Behavior Raise alters even in maintenance window. ### 🐻 Uptime-Kuma Version 1.21.2 ### 💻 Operating System and Arch Arch Linux ### 🌐 Browser Edge ### 🐋 Docker Version 23.0.1 ### 🟩 NodeJS Version _No response_ ### 📝 Relevant log output ```shell 2023-04-29T03:00:00+08:00 [MAINTENANCE] INFO: Maintenance id: 1 is under maintenance now 2023-04-29T03:01:53+08:00 [MONITOR] WARN: Monitor #4 '<redacted>': Pending: connect ETIMEDOUT 172.67.145.23:443 | Max retries: 3 | Retry: 1 | Retry Interval: 300 seconds | Type: http Worker for job "clear-old-data" online undefined 2023-04-29T03:14:01+08:00 [PLUGIN] WARN: Warning: In order to enable plugin feature, you need to use the default data directory: ./data/ 2023-04-29T03:14:01+08:00 [DB] INFO: Data Dir: data/ 2023-04-29T03:14:02+08:00 [DB] INFO: SQLite config: [ { journal_mode: 'wal' } ] [ { cache_size: -12000 } ] 2023-04-29T03:14:02+08:00 [DB] INFO: SQLite Version: 3.41.1 { name: 'clear-old-data', message: 'Data deletion has been disabled as period is less than 1. Period is 0 days.' } { name: 'clear-old-data', message: 'done' } 2023-04-29T03:26:04+08:00 [MONITOR] WARN: Monitor #14 '<redacted>': Pending: Request failed with status code 502 | Max retries: 3 | Retry: 1 | Retry Interval: 60 seconds | Type: http 2023-04-29T03:27:04+08:00 [MONITOR] WARN: Monitor #14 '<redacted>': Pending: Request failed with status code 502 | Max retries: 3 | Retry: 2 | Retry Interval: 60 seconds | Type: http 2023-04-29T03:28:05+08:00 [MONITOR] WARN: Monitor #14 '<redacted>': Pending: Request failed with status code 502 | Max retries: 3 | Retry: 3 | Retry Interval: 60 seconds | Type: http 2023-04-29T03:29:13+08:00 [MONITOR] WARN: Monitor #4 '<redacted>': Pending: connect ETIMEDOUT 104.21.79.107:443 | Max retries: 3 | Retry: 1 | Retry Interval: 300 seconds | Type: http 2023-04-29T03:29:14+08:00 [MONITOR] WARN: Monitor #14 '<redacted>': Failing: Request failed with status code 502 | Interval: 60 seconds | Type: http | Down Count: 0 | Resend Interval: 0 2023-04-29T03:30:15+08:00 [MONITOR] WARN: Monitor #14 '<redacted>': Failing: Request failed with status code 502 | Interval: 60 seconds | Type: http | Down Count: 0 | Resend Interval: 0 2023-04-29T03:31:16+08:00 [MONITOR] WARN: Monitor #14 '<redacted>': Failing: Request failed with status code 502 | Interval: 60 seconds | Type: http | Down Count: 0 | Resend Interval: 0 2023-04-29T03:32:16+08:00 [MONITOR] WARN: Monitor #14 '<redacted>': Failing: Request failed with status code 502 | Interval: 60 seconds | Type: http | Down Count: 0 | Resend Interval: 0 ```

deekerman added the

bug

A:maintenance

labels

2026-02-28 02:44:40 -05:00

deekerman commented

2026-02-28 02:44:43 -05:00

Author

Owner

@Tralapo commented on GitHub (Apr 30, 2023):

I had the same issue, no matter what I tried or which recurring type I used.

As soon as I left the "Effected Date Range" empty (which is now Optional) it worked again. Seems like a bug somewhere in there.

@Tralapo commented on GitHub (Apr 30, 2023): I had the same issue, no matter what I tried or which recurring type I used. As soon as I left the "Effected Date Range" empty (which is now Optional) it worked again. Seems like a bug somewhere in there.

deekerman commented

2026-02-28 02:44:46 -05:00

Author

Owner

@hanyuwei70 commented on GitHub (May 2, 2023):

I had the same issue, no matter what I tried or which recurring type I used.

As soon as I left the "Effected Date Range" empty (which is now Optional) it worked again. Seems like a bug somewhere in there.

Works for me! Thanks.

@hanyuwei70 commented on GitHub (May 2, 2023): > I had the same issue, no matter what I tried or which recurring type I used. > > As soon as I left the "Effected Date Range" empty (which is now Optional) it worked again. Seems like a bug somewhere in there. Works for me! Thanks.

deekerman commented

2026-02-28 02:44:46 -05:00

Author

Owner

@gdtms247 commented on GitHub (May 10, 2023):

I have the exact same issue for last few weeks, removed "Effected Date Range" and scheduled maintenance is now successfully running. Thanks!

@gdtms247 commented on GitHub (May 10, 2023): I have the exact same issue for last few weeks, removed "Effected Date Range" and scheduled maintenance is now successfully running. Thanks!

deekerman commented

2026-02-28 02:44:46 -05:00

Author

Owner

@x86dev commented on GitHub (May 10, 2023):

Same here, can confirm that this workaround fixed it for me, thanks!

@x86dev commented on GitHub (May 10, 2023): Same here, can confirm that this workaround fixed it for me, thanks!

deekerman commented

2026-02-28 02:44:46 -05:00

Author

Owner

@DANW999 commented on GitHub (Nov 11, 2023):

I can confirm that also worked for me. I was pulling my hair out trying to figure out why the maintenance mode was not kicking in at scheduled time.

@DANW999 commented on GitHub (Nov 11, 2023): I can confirm that also worked for me. I was pulling my hair out trying to figure out why the maintenance mode was not kicking in at scheduled time.