Skip to content

Broken repo - don't understand why and how to fix #34424

Closed
@davidfrickert

Description

@davidfrickert

Description

"The Git data underlying this repository cannot be read. Contact the administrator of this instance or delete this repository."

Have this happen to two repos so far on the last few months. Solved first by deleting the repo and re-pushing the code, but really would be better if this doesn't happen

I can still pull/push to the repo from git tools, but anything involving gitea UI or actions is completely broken on these repos.

(Note: the actual repo name has been replaced with in the snippets below)
The repo seems fine:

/data/git/gitea-repositories/davidfrickert/<REPONAME>.git $ git show-ref --tags
bd3da0bb27177a3b191bb84521eef59692b210b6 refs/tags/0.1.0
33989d17e4d94ac386af6f1a1fdeef14b5231ba0 refs/tags/0.1.1
/data/git/gitea-repositories/davidfrickert/<REPONAME>.git $ /usr/bin/git -c protocol.version=2 -c credential.helper= rev-parse
/data/git/gitea-repositories/davidfrickert/<REPONAME>.git $ echo $?
0

I have this in the app.ini:

[log]
MODE = console
LEVEL = Debug ; please set the level to debug when we are debugging a problem
STACKTRACE_LEVEL = error
COLORIZE = false ; this can be true if you can strip out the ansi coloring

I don't really get anything interesting in the logs when trying to access the repo via gitea (a bit more shown in the gist but probably not useful):

2025/05/10 14:58:19 .../context_response.go:70:HTML() [D] Template: repo/empty

Funnily enough, I am able to clone the repo with no issues (sorry for some PT language):
Pushing new commits / pulling etc also works.

git clone https://git.djf.lol/davidfrickert/<REPONAME>.git
Clonando para '<REPONAME>'...
remote: Enumerating objects: 37, done.
remote: Counting objects: 100% (37/37), done.
remote: Compressing objects: 100% (33/33), done.
remote: Total 37 (delta 10), reused 0 (delta 0), pack-reused 0 (from 0)
A receber objetos: 100% (37/37), 13.67 KiB | 13.67 MiB/s, concluído.
A resolver deltas: 100% (10/10), concluído.

Gitea Version

1.23.7

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

https://gist.github.com/davidfrickert/753cd38cfc1462f92b1863f3b8241c24

Screenshots

Image

Git Version

git --version -> git version 2.47.2

Operating System

Fedora 41 Server

How are you running Gitea?

Helm chart on Kubernetes (3 gitea instances, 3 redis instances)
Using the official docker image from gitea v1.23.7

Database

PostgreSQL

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions