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

Random 500 errors #11606

Closed
2 of 7 tasks
sshaikh opened this issue May 24, 2020 · 3 comments
Closed
2 of 7 tasks

Random 500 errors #11606

sshaikh opened this issue May 24, 2020 · 3 comments

Comments

@sshaikh
Copy link

sshaikh commented May 24, 2020

  • Gitea version (or commit ref): 1.12.0
  • Git version: 2.20.1
  • Operating system: Debian
  • 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:

2020/05/24 15:43:18 ...sitory/repository.go:23:CreateRepository() [E] Rollback deleteRepository: repository does not exist [id: 31, uid: 2, owner_name: , name: ]
2020/05/24 15:43:18 routers/repo/repo.go:175:handleCreateError() [E] CreatePost: initRepository: createDelegateHooks: Unable to set /appdata/repositories/atal/omv-config.git/hooks/pre-receive executable. Error stat /appdata/repositories/atal/omv-config.git/hooks/pre-receive.d/gitea: interrupted system call

https://gist.github.com/sshaikh/4bfd4219e4dcdfa2a8c96893c5c02c56

Description

We get 500 errors on the webUI at what appears to be random points. Sometimes when viewing a repo - but then F5 would fix it. A lot more often when creating repos, but eventually things go through. Also at various points in the usage.

Git pulls and pushes seem to work all the time.

I can't see what causes the error from the logs.

Environment

I'm running Gitea in an LXC container, and my repos are on a bind mount (which in turn is an autofs CIFS mount on the LXC host). I do not think there is an access issue as the file system appears to be available at all times (and the creating repo consistently fails until it works).

@alexander-zierhut
Copy link

+1
Had a 500 error when trying to enable 2FA.

@stale
Copy link

stale bot commented Jul 25, 2020

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale stale bot added the issue/stale label Jul 25, 2020
@stale
Copy link

stale bot commented Aug 9, 2020

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

@stale stale bot closed this as completed Aug 9, 2020
@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.
Projects
None yet
Development

No branches or pull requests

2 participants