Update cron.update_mirrors doesn't work #9919

Closed
opened 2025-11-02 08:53:07 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @oDinZu on GitHub (Dec 2, 2022).

Description

In my app.ini I change from @daily 10m to @weekly 0 0 0 * * 0 and restart Gitea, but the cron schedule on the user interface doesn't update and stays at 10m time intervals. This creates bandwidth issues and hogs CPU resources.

I tested @weekly 0 0 0 * * 0,0 0 0 * * 0, @midnight, ... but everything I change doesn't update anything.

is [cron.update_mirrors] correct?
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Update mirrors
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
[cron.update_mirrors]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
SCHEDULE = 0 0 0 * * 0
;; Enable running Update mirrors task periodically.
;ENABLED = true
;; Run Update mirrors task when Gitea starts.
;RUN_AT_START = false
;; Notice if not success
;NOTICE_ON_SUCCESS = false
;; Limit the number of mirrors added to the queue to this number
;; (negative values mean no limit, 0 will result in no result in no mirrors being queued effectively disabling pull mirror updating.)
PULL_LIMIT=75
;; Limit the number of mirrors added to the queue to this number
;; (negative values mean no limit, 0 will result in no mirrors being queued effectively disabling push mirror updating)
PUSH_LIMIT=75

Gitea Version

1.16.6

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

I compiled it myself.

Database

None

Originally created by @oDinZu on GitHub (Dec 2, 2022). ### Description In my `app.ini` I change from `@daily 10m` to `@weekly 0 0 0 * * 0` and restart Gitea, but the cron schedule on the user interface doesn't update and stays at 10m time intervals. This creates bandwidth issues and hogs CPU resources. I tested `@weekly 0 0 0 * * 0`,`0 0 0 * * 0`, `@midnight`, ... but everything I change doesn't update anything. is `[cron.update_mirrors]` correct? ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; Update mirrors ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; [cron.update_mirrors] ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; SCHEDULE = 0 0 0 * * 0 ;; Enable running Update mirrors task periodically. ;ENABLED = true ;; Run Update mirrors task when Gitea starts. ;RUN_AT_START = false ;; Notice if not success ;NOTICE_ON_SUCCESS = false ;; Limit the number of mirrors added to the queue to this number ;; (negative values mean no limit, 0 will result in no result in no mirrors being queued effectively disabling pull mirror updating.) PULL_LIMIT=75 ;; Limit the number of mirrors added to the queue to this number ;; (negative values mean no limit, 0 will result in no mirrors being queued effectively disabling push mirror updating) PUSH_LIMIT=75 ### Gitea Version 1.16.6 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? I compiled it myself. ### Database None
GiteaMirror added the issue/needs-feedback label 2025-11-02 08:53:07 -06:00
Author
Owner

@zeripath commented on GitHub (Dec 3, 2022):

Gitea 1.16 is very old - upgrade to at least 1.17.

@zeripath commented on GitHub (Dec 3, 2022): Gitea 1.16 is very old - upgrade to at least 1.17.
Author
Owner

@lunny commented on GitHub (Dec 6, 2022):

Description

In my app.ini I change from @daily 10m to @weekly 0 0 0 * * 0 and restart Gitea, but the cron schedule on the user interface doesn't update and stays at 10m time intervals. This creates bandwidth issues and hogs CPU resources.

I tested @weekly 0 0 0 * * 0,0 0 0 * * 0, @midnight, ... but everything I change doesn't update anything.

is [cron.update_mirrors] correct? ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; Update mirrors ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; [cron.update_mirrors] ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; SCHEDULE = 0 0 0 * * 0 ;; Enable running Update mirrors task periodically. ;ENABLED = true ;; Run Update mirrors task when Gitea starts. ;RUN_AT_START = false ;; Notice if not success ;NOTICE_ON_SUCCESS = false ;; Limit the number of mirrors added to the queue to this number ;; (negative values mean no limit, 0 will result in no result in no mirrors being queued effectively disabling pull mirror updating.) PULL_LIMIT=75 ;; Limit the number of mirrors added to the queue to this number ;; (negative values mean no limit, 0 will result in no mirrors being queued effectively disabling push mirror updating) PUSH_LIMIT=75

Gitea Version

1.16

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

I compiled it myself.

Database

None

Please ensure Gitea read the correct app.ini (you changed).

@lunny commented on GitHub (Dec 6, 2022): > ### Description > In my `app.ini` I change from `@daily 10m` to `@weekly 0 0 0 * * 0` and restart Gitea, but the cron schedule on the user interface doesn't update and stays at 10m time intervals. This creates bandwidth issues and hogs CPU resources. > > I tested `@weekly 0 0 0 * * 0`,`0 0 0 * * 0`, `@midnight`, ... but everything I change doesn't update anything. > > is `[cron.update_mirrors]` correct? ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; Update mirrors ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; [cron.update_mirrors] ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; SCHEDULE = 0 0 0 * * 0 ;; Enable running Update mirrors task periodically. ;ENABLED = true ;; Run Update mirrors task when Gitea starts. ;RUN_AT_START = false ;; Notice if not success ;NOTICE_ON_SUCCESS = false ;; Limit the number of mirrors added to the queue to this number ;; (negative values mean no limit, 0 will result in no result in no mirrors being queued effectively disabling pull mirror updating.) PULL_LIMIT=75 ;; Limit the number of mirrors added to the queue to this number ;; (negative values mean no limit, 0 will result in no mirrors being queued effectively disabling push mirror updating) PUSH_LIMIT=75 > > ### Gitea Version > 1.16 > > ### Can you reproduce the bug on the Gitea demo site? > No > > ### Log Gist > _No response_ > > ### Screenshots > _No response_ > > ### Git Version > _No response_ > > ### Operating System > _No response_ > > ### How are you running Gitea? > I compiled it myself. > > ### Database > None Please ensure Gitea read the correct app.ini (you changed).
Author
Owner

@oDinZu commented on GitHub (Dec 10, 2022):

This was the issue @lunny; I found another config in /etc/gitea/app.ini.

Whoops, I should of looked at my Gitea configuration file first. I don't know why I didn't look at this to begin with.. 🥲

Thank you Lunny ❤️

@oDinZu commented on GitHub (Dec 10, 2022): This was the issue @lunny; I found another config in */etc/gitea/app.ini*. Whoops, I should of looked at my Gitea configuration file first. I don't know why I didn't look at this to begin with.. :smiling_face_with_tear: Thank you Lunny :heart:
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#9919