Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash when collaborator pushes/pulls to a private repo #7018

Closed
2 of 7 tasks
tcpluess opened this issue May 22, 2019 · 6 comments
Closed
2 of 7 tasks

Crash when collaborator pushes/pulls to a private repo #7018

tcpluess opened this issue May 22, 2019 · 6 comments

Comments

@tcpluess
Copy link

tcpluess commented May 22, 2019

Description

My colleague has created a private repository as follows:

Screenshot_2019-05-22_17-18-37

And I am added as collaborator to that repo:

Screenshot_2019-05-22_17-20-14

It worked fine to clone the repo and push to it, as one can see:

Screenshot_2019-05-22_17-21-25

However, since he made the last commit, gitea silently crashes when I try to push again some changes or pull from the repo. I set the log level to Debug, but this doesn't give much more info.

I checked the journalctl as well (see gist) and also dmesg (see gist as well).

@tcpluess tcpluess changed the title Crash when collaborator pushes to a private repo Crash when collaborator pushes/pulls to a private repo May 22, 2019
@zeripath
Copy link
Contributor

Looks like it ran out of memory.

@zeripath
Copy link
Contributor

Hmm so it looks like you're pushing over http. Can you check http log and the hook logs.

It might be worth checking if pushing over SSH works.

@zeripath
Copy link
Contributor

I don't suppose you can reproduce on try?

@mrsdizzie
Copy link
Member

mrsdizzie commented May 22, 2019

how big is the repo you are trying to push/pull?

And/or perhaps maybe more relevant here, what is reported on the server for git count-objects -vH

@lunny
Copy link
Member

lunny commented May 23, 2019

Have you enabled code search?

@tcpluess
Copy link
Author

I perhaps found the problem. My Gitea instance was running in a LXC container with Debian 9. It seems like there is a compatibility issue with systemd running inside a container. Here are some explanations why, even though this is for Docker, it seems also to apply for LXC.
I created a new container using Alpine Linux, and with that, Gitea works just fine on the very same repo.

So I close the issue for now as it seems it has nothing to do with Gitea.

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants