Gitea wont start , Status Code 2 on Systemd on Centos 7 #3072

New Issue

GiteaMirror · 2025-11-02T04:59:48-06:00

GiteaMirror commented

2025-11-02 04:59:48 -06:00

Originally created by @dukesx on GitHub (Mar 19, 2019).

Gitea version (or commit ref): 1.7.4
Git version: 2.19
Operating system: Centos 7
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- [ x ] Not relevant
Log gist: it doesnt log anything , it wont start at all , systemd is saying status code 2

Description

So , i have a server with cPanel with Centos 7. I tried installing via the docs but however i work , systemd just does not start Gitea at all.

Sometimes it says Code 2 or Code 203 , i have tried running "git" user and "root" , both have their own errors.

I did add relevant permissions to /etc/gitea and /var/lib/gitea as well. I also chmod +x to gitea binary. No solution. Please Help !

Update: Now the Service , switches state after each second , one second it is up and on the other second it is down ..... See the screenshots

...

Screenshots

Originally created by @dukesx on GitHub (Mar 19, 2019).   - Gitea version (or commit ref): 1.7.4 - Git version: 2.19 - Operating system: Centos 7 - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [ x ] Not relevant - Log gist: it doesnt log anything , it wont start at all , systemd is saying status code 2 ## Description So , i have a server with cPanel with Centos 7. I tried installing via the docs but however i work , systemd just does not start Gitea at all. Sometimes it says Code 2 or Code 203 , i have tried running "git" user and "root" , both have their own errors. I did add relevant permissions to `/etc/gitea` and `/var/lib/gitea` as well. I also `chmod +x` to gitea binary. No solution. Please Help ! **Update**: Now the Service , switches state after each second , one second it is up and on the other second it is down ..... See the screenshots ... ## Screenshots ![ajeeb](https://user-images.githubusercontent.com/5988991/54627059-57ca4600-4a94-11e9-8495-470298f6c338.png)

GiteaMirror added the issue/stale issue/needs-feedback labels 2025-11-02 04:59:48 -06:00

GiteaMirror closed this issue

2025-11-02 04:59:48 -06:00

GiteaMirror commented

2025-11-02 04:59:49 -06:00

@jolheiser commented on GitHub (Mar 19, 2019):

Is there anything in your gitea.log?

@jolheiser commented on GitHub (Mar 19, 2019): Is there anything in your `gitea.log`?

GiteaMirror commented

2025-11-02 04:59:49 -06:00

@stale[bot] commented on GitHub (May 30, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (May 30, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 04:59:49 -06:00

@stale[bot] commented on GitHub (Jun 13, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Jun 13, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror referenced this issue

2025-11-02 12:18:08 -06:00

[PR #3072] [MERGED] Sort repos in issues dashboard sidebar #16747

Sign in to join this conversation.