Gitea Maintenance Question #729

New Issue

GiteaMirror · 2025-11-02T03:34:19-06:00

GiteaMirror commented

2025-11-02 03:34:19 -06:00

Originally created by @davydov-vyacheslav on GitHub (May 21, 2017).

Hi,

I have a question about maintenance part of gitea.

As admin / owner of gitea instance I'd like:

during upgrading get information about status of migration . If migration is not completed yet, the server returns 503 error per each request . It is a bit confused because I don't know, whether migration fails / service is not up during any reasons or just migration is still in progress
My database locates at different host, and each time when for some reasons database connection lists, I'm receiving 503 error per each request. Again, when I have access only for UI part (from mobile device) it is hard to get insight the reason of this behavior.

Is it possible to get some king of maintenance page to get status of each page connection and e.g. for database connection get ability to try to restore connection? Is it possible there get server.log content to identify possible reasons of 503 error myself without direct access to host?

P.S.
In my environment it is installed as daemon / service (Raspberry PI).

Thanks in advance,
Slava

Originally created by @davydov-vyacheslav on GitHub (May 21, 2017). Hi, I have a question about maintenance part of gitea. As admin / owner of gitea instance I'd like: - during upgrading get information about status of migration . If migration is not completed yet, the server returns 503 error per each request . It is a bit confused because I don't know, whether migration fails / service is not up during any reasons or just migration is still in progress - My database locates at different host, and each time when for some reasons database connection lists, I'm receiving 503 error per each request. Again, when I have access only for UI part (from mobile device) it is hard to get insight the reason of this behavior. Is it possible to get some king of maintenance page to get status of each page connection and e.g. for database connection get ability to try to restore connection? Is it possible there get server.log content to identify possible reasons of 503 error myself without direct access to host? P.S. In my environment it is installed as daemon / service (Raspberry PI). Thanks in advance, Slava

GiteaMirror added the type/question label 2025-11-02 03:34:19 -06:00

GiteaMirror closed this issue

2025-11-02 03:34:19 -06:00

GiteaMirror commented

2025-11-02 03:34:20 -06:00

@lunny commented on GitHub (May 22, 2017):

I think 503 is returned from your reverse proxy since Gitea upgrade failed (i.e. nginx).

@lunny commented on GitHub (May 22, 2017): I think 503 is returned from your reverse proxy since Gitea upgrade failed (i.e. nginx).

GiteaMirror commented

2025-11-02 03:34:20 -06:00

@davydov-vyacheslav commented on GitHub (May 22, 2017):

The main problem (from my point of view) is that 503 error returns not because of failed migration but because migration is still in progress , and the situation is ambiguous to determine the actual root of 503 error

@davydov-vyacheslav commented on GitHub (May 22, 2017): The main problem (from my point of view) is that 503 error returns not because of failed migration but because migration is still in progress , and the situation is ambiguous to determine the actual root of 503 error

GiteaMirror commented

2025-11-02 03:34:20 -06:00

@lunny commented on GitHub (May 22, 2017):

Yes. The Gitea web service will be started after migration completed.

@lunny commented on GitHub (May 22, 2017): Yes. The Gitea web service will be started after migration completed.

GiteaMirror commented

2025-11-02 03:34:20 -06:00

@davydov-vyacheslav commented on GitHub (May 22, 2017):

Is there a way to make some kind diagnostic page to determine the reason of site being down (actually up, but with errors or migration in progress) ?

@davydov-vyacheslav commented on GitHub (May 22, 2017): Is there a way to make some kind diagnostic page to determine the reason of site being down (actually up, but with errors or migration in progress) ?

GiteaMirror commented

2025-11-02 03:34:20 -06:00

@kolaente commented on GitHub (May 28, 2017):

If you're using a reverse proxy, you could set up a 503-Errorpage with that

@kolaente commented on GitHub (May 28, 2017): If you're using a reverse proxy, you could set up a 503-Errorpage with that

GiteaMirror referenced this issue

2025-11-02 11:49:07 -06:00

[PR #731] [MERGED] fix logfile name #15547

Sign in to join this conversation.