github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-15 20:09:18 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Gitea unable to start #1742

New Issue
Closed
opened 2025-11-02 04:11:52 -06:00 by GiteaMirror · 14 comments
GiteaMirror commented 2025-11-02 04:11:52 -06:00
Owner
Copy Link

Originally created by @drsect0r on GitHub (Apr 30, 2018).

  • Gitea version: Docker 907f7f0a49e0
  • Git version:
  • Operating system: Debian 8
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

Gitea appears to be stuck in a loop and is unable to start, displaying the messages below. Only thing related I could find is commit cb87f29b76.

WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping
2018/04/30 09:57:31 [T] AppPath: /app/gitea/gitea
2018/04/30 09:57:31 [T] AppWorkPath: /app/gitea
2018/04/30 09:57:31 [T] Custom path: /data/gitea
2018/04/30 09:57:31 [T] Log path: /data/gitea/log
WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping
2018/04/30 09:57:32 [T] AppPath: /app/gitea/gitea
2018/04/30 09:57:32 [T] AppWorkPath: /app/gitea
2018/04/30 09:57:32 [T] Custom path: /data/gitea
2018/04/30 09:57:32 [T] Log path: /data/gitea/log
WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping
2018/04/30 09:57:33 [T] AppPath: /app/gitea/gitea
2018/04/30 09:57:33 [T] AppWorkPath: /app/gitea
2018/04/30 09:57:33 [T] Custom path: /data/gitea
2018/04/30 09:57:33 [T] Log path: /data/gitea/log
WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping
2018/04/30 09:57:34 [T] AppPath: /app/gitea/gitea
2018/04/30 09:57:34 [T] AppWorkPath: /app/gitea
2018/04/30 09:57:34 [T] Custom path: /data/gitea
2018/04/30 09:57:34 [T] Log path: /data/gitea/log
Originally created by @drsect0r on GitHub (Apr 30, 2018). - Gitea version: Docker 907f7f0a49e0 - Git version: - Operating system: Debian 8 - 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: ## Description Gitea appears to be stuck in a loop and is unable to start, displaying the messages below. Only thing related I could find is commit https://github.com/go-gitea/gitea/commit/cb87f29b76f661d9c726579067c9c64db55fd970. ``` WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping 2018/04/30 09:57:31 [T] AppPath: /app/gitea/gitea 2018/04/30 09:57:31 [T] AppWorkPath: /app/gitea 2018/04/30 09:57:31 [T] Custom path: /data/gitea 2018/04/30 09:57:31 [T] Log path: /data/gitea/log WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping 2018/04/30 09:57:32 [T] AppPath: /app/gitea/gitea 2018/04/30 09:57:32 [T] AppWorkPath: /app/gitea 2018/04/30 09:57:32 [T] Custom path: /data/gitea 2018/04/30 09:57:32 [T] Log path: /data/gitea/log WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping 2018/04/30 09:57:33 [T] AppPath: /app/gitea/gitea 2018/04/30 09:57:33 [T] AppWorkPath: /app/gitea 2018/04/30 09:57:33 [T] Custom path: /data/gitea 2018/04/30 09:57:33 [T] Log path: /data/gitea/log WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping 2018/04/30 09:57:34 [T] AppPath: /app/gitea/gitea 2018/04/30 09:57:34 [T] AppWorkPath: /app/gitea 2018/04/30 09:57:34 [T] Custom path: /data/gitea 2018/04/30 09:57:34 [T] Log path: /data/gitea/log ```
GiteaMirror added the type/question label 2025-11-02 04:11:52 -06:00
GiteaMirror commented 2025-11-02 04:11:53 -06:00
Author
Owner
Copy Link

@daviian commented on GitHub (Apr 30, 2018):

There's already a discussion about that warning: https://github.com/gliderlabs/docker-alpine/issues/30

Guess we should implemented the workaround mentioned here https://github.com/gliderlabs/docker-alpine/issues/30#issuecomment-372020089

@daviian commented on GitHub (Apr 30, 2018): There's already a discussion about that warning: https://github.com/gliderlabs/docker-alpine/issues/30 Guess we should implemented the workaround mentioned here https://github.com/gliderlabs/docker-alpine/issues/30#issuecomment-372020089
GiteaMirror commented 2025-11-02 04:11:53 -06:00
Author
Owner
Copy Link

@drsect0r commented on GitHub (Apr 30, 2018):

I also don't think this is the cause of Gitea not starting. (just found out about https://github.com/go-gitea/gitea/issues/3859)

@drsect0r commented on GitHub (Apr 30, 2018): I also don't think this is the cause of Gitea not starting. (just found out about https://github.com/go-gitea/gitea/issues/3859)
GiteaMirror commented 2025-11-02 04:11:53 -06:00
Author
Owner
Copy Link

@pojntfx commented on GitHub (May 10, 2018):

I have the same problem using the latest gitea docker image. Any workarounds? Tried gliderlabs/docker-alpine#30 (entered the commands into the running container from the OpenShift web console; should I do this differently?) but that did not work, still the same error. I'm using postgresql as my database.

@pojntfx commented on GitHub (May 10, 2018): I have the same problem using the latest gitea docker image. Any workarounds? Tried gliderlabs/docker-alpine#30 (entered the commands into the running container from the OpenShift web console; should I do this differently?) but that did not work, still the same error. I'm using postgresql as my database.
GiteaMirror commented 2025-11-02 04:11:53 -06:00
Author
Owner
Copy Link

@NoMoreNicksLeft commented on GitHub (Jun 20, 2018):

I have this same problem. The linked alpine issue fix does not work for me. This loops forever.

@NoMoreNicksLeft commented on GitHub (Jun 20, 2018): I have this same problem. The linked alpine issue fix does not work for me. This loops forever.
GiteaMirror commented 2025-11-02 04:11:53 -06:00
Author
Owner
Copy Link

@ivarlovlie commented on GitHub (Jun 20, 2018):

probably unrelated, but this loop/error only occurs when i set START_SSH_SERVER to true

@ivarlovlie commented on GitHub (Jun 20, 2018): probably unrelated, but this loop/error only occurs when i set `START_SSH_SERVER` to `true`
GiteaMirror commented 2025-11-02 04:11:54 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Jun 20, 2018):

That's because gitea can not bind on 22 port probably

@lafriks commented on GitHub (Jun 20, 2018): That's because gitea can not bind on 22 port probably
GiteaMirror commented 2025-11-02 04:11:54 -06:00
Author
Owner
Copy Link

@UtechtDustin commented on GitHub (Jun 20, 2018):

@lafriks
I also get the same output (without the warning)

2018/06/20 19:06:35 [T] AppPath: /opt/gitea/gitea
2018/06/20 19:06:35 [T] AppWorkPath: /opt/gitea
2018/06/20 19:06:35 [T] Custom path: /opt/gitea/custom
2018/06/20 19:06:35 [T] Log path: /opt/log

Gittea dont start and i got also no errors (also not in the log file).

@UtechtDustin commented on GitHub (Jun 20, 2018): @lafriks I also get the same output (without the warning) ``` 2018/06/20 19:06:35 [T] AppPath: /opt/gitea/gitea 2018/06/20 19:06:35 [T] AppWorkPath: /opt/gitea 2018/06/20 19:06:35 [T] Custom path: /opt/gitea/custom 2018/06/20 19:06:35 [T] Log path: /opt/log ``` Gittea dont start and i got also no errors (also not in the log file).
GiteaMirror commented 2025-11-02 04:11:54 -06:00
Author
Owner
Copy Link

@ptrcnull commented on GitHub (Nov 17, 2018):

Still happens for me on the latest Docker image.

  • Gitea version: Docker fa6ca546d614
  • Database: SQLite

EDIT: nvm, fixed it. for anyone reading: check your disk space

@ptrcnull commented on GitHub (Nov 17, 2018): Still happens for me on the latest Docker image. - Gitea version: Docker fa6ca546d614 - Database: SQLite EDIT: nvm, fixed it. for anyone reading: check your disk space
GiteaMirror commented 2025-11-02 04:11:54 -06:00
Author
Owner
Copy Link

@daknuett commented on GitHub (Dec 19, 2018):

I have the same problem. I am on version 60505c2ef496475a7f90f0ea577a8cf1f3d2b53dfa7d0c9aca342e7b620d309a with SQLite database.

Gitea seems to ignore my gitea/conf/app.ini:

Dec 19 13:26:15 syslogd started: BusyBox v1.28.4
Dec 19 13:26:15 sshd[15]: Server listening on :: port 22.
Dec 19 13:26:15 sshd[15]: Server listening on 0.0.0.0 port 22.
2018/12/19 13:26:15 [T] AppPath: /app/gitea/gitea
2018/12/19 13:26:15 [T] AppWorkPath: /app/gitea
2018/12/19 13:26:15 [T] Custom path: /data/gitea
2018/12/19 13:26:15 [T] Log path: /data/gitea/log
2018/12/19 13:26:16 [T] AppPath: /app/gitea/gitea
2018/12/19 13:26:16 [T] AppWorkPath: /app/gitea
2018/12/19 13:26:16 [T] Custom path: /data/gitea
2018/12/19 13:26:16 [T] Log path: /data/gitea/log
2018/12/19 13:26:16 [I] Gitea vb65e37e built with: bindata, sqlite, sqlite_unlock_notify
2018/12/19 13:26:17 [T] AppPath: /app/gitea/gitea
2018/12/19 13:26:17 [T] AppWorkPath: /app/gitea
2018/12/19 13:26:17 [T] Custom path: /data/gitea
2018/12/19 13:26:17 [T] Log path: /data/gitea/log
2018/12/19 13:26:18 [T] AppPath: /app/gitea/gitea
2018/12/19 13:26:18 [T] AppWorkPath: /app/gitea
2018/12/19 13:26:18 [T] Custom path: /data/gitea
2018/12/19 13:26:18 [T] Log path: /data/gitea/log
2018/12/19 13:26:19 [T] AppPath: /app/gitea/gitea
2018/12/19 13:26:19 [T] AppWorkPath: /app/gitea
2018/12/19 13:26:19 [T] Custom path: /data/gitea
2018/12/19 13:26:19 [T] Log path: /data/gitea/log
2018/12/19 13:26:20 [T] AppPath: /app/gitea/gitea
2018/12/19 13:26:20 [T] AppWorkPath: /app/gitea
2018/12/19 13:26:20 [T] Custom path: /data/gitea
2018/12/19 13:26:20 [T] Log path: /data/gitea/log
[repeats]

Although I have in my app.ini:

DISABLE_SSH      = false
SSH_PORT         = 10022

All was working fine unti it recently just stopped working.

@daknuett commented on GitHub (Dec 19, 2018): I have the same problem. I am on version 60505c2ef496475a7f90f0ea577a8cf1f3d2b53dfa7d0c9aca342e7b620d309a with SQLite database. Gitea seems to ignore my `gitea/conf/app.ini`: ``` Dec 19 13:26:15 syslogd started: BusyBox v1.28.4 Dec 19 13:26:15 sshd[15]: Server listening on :: port 22. Dec 19 13:26:15 sshd[15]: Server listening on 0.0.0.0 port 22. 2018/12/19 13:26:15 [T] AppPath: /app/gitea/gitea 2018/12/19 13:26:15 [T] AppWorkPath: /app/gitea 2018/12/19 13:26:15 [T] Custom path: /data/gitea 2018/12/19 13:26:15 [T] Log path: /data/gitea/log 2018/12/19 13:26:16 [T] AppPath: /app/gitea/gitea 2018/12/19 13:26:16 [T] AppWorkPath: /app/gitea 2018/12/19 13:26:16 [T] Custom path: /data/gitea 2018/12/19 13:26:16 [T] Log path: /data/gitea/log 2018/12/19 13:26:16 [I] Gitea vb65e37e built with: bindata, sqlite, sqlite_unlock_notify 2018/12/19 13:26:17 [T] AppPath: /app/gitea/gitea 2018/12/19 13:26:17 [T] AppWorkPath: /app/gitea 2018/12/19 13:26:17 [T] Custom path: /data/gitea 2018/12/19 13:26:17 [T] Log path: /data/gitea/log 2018/12/19 13:26:18 [T] AppPath: /app/gitea/gitea 2018/12/19 13:26:18 [T] AppWorkPath: /app/gitea 2018/12/19 13:26:18 [T] Custom path: /data/gitea 2018/12/19 13:26:18 [T] Log path: /data/gitea/log 2018/12/19 13:26:19 [T] AppPath: /app/gitea/gitea 2018/12/19 13:26:19 [T] AppWorkPath: /app/gitea 2018/12/19 13:26:19 [T] Custom path: /data/gitea 2018/12/19 13:26:19 [T] Log path: /data/gitea/log 2018/12/19 13:26:20 [T] AppPath: /app/gitea/gitea 2018/12/19 13:26:20 [T] AppWorkPath: /app/gitea 2018/12/19 13:26:20 [T] Custom path: /data/gitea 2018/12/19 13:26:20 [T] Log path: /data/gitea/log [repeats] ``` Although I have in my app.ini: ``` DISABLE_SSH = false SSH_PORT = 10022 ``` All was working fine unti it recently just stopped working.
GiteaMirror commented 2025-11-02 04:11:55 -06:00
Author
Owner
Copy Link

@danst0 commented on GitHub (Jan 18, 2019):

Same here. Latest Docker image. app.ini is ignored.

@danst0 commented on GitHub (Jan 18, 2019): Same here. Latest Docker image. app.ini is ignored.
GiteaMirror commented 2025-11-02 04:11:55 -06:00
Author
Owner
Copy Link

@Marco77577 commented on GitHub (Apr 18, 2019):

And also here. Is there no solution?

@Marco77577 commented on GitHub (Apr 18, 2019): And also here. Is there no solution?
GiteaMirror commented 2025-11-02 04:11:55 -06:00
Author
Owner
Copy Link

@daknuett commented on GitHub (Apr 18, 2019):

Well the last time I had to wait for the next image and it started working again.

A possible workaround is to explicitly tag the version that works, instead of using latest.

@daknuett commented on GitHub (Apr 18, 2019): Well the last time I had to wait for the next image and it started working again. A possible workaround is to explicitly tag the version that works, instead of using `latest`.
GiteaMirror commented 2025-11-02 04:11:55 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Apr 18, 2019):

Hmm they should always work! If they're not working you need to open an issue.

@zeripath commented on GitHub (Apr 18, 2019): Hmm they should always work! If they're not working you need to open an issue.
GiteaMirror commented 2025-11-02 04:11:56 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Apr 18, 2019):

I will lock this conversation so that any new issue can be resolved in open tickets.

@techknowlogick commented on GitHub (Apr 18, 2019): I will lock this conversation so that any new issue can be resolved in open tickets.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#1742
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?