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

Gitea 1.12.4 always restart and see 502 Bad Gateway #5986

New Issue
Closed
opened 2025-11-02 06:42:00 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 06:42:00 -06:00
Owner
Copy Link

Originally created by @fansat on GitHub (Sep 11, 2020).

  • Gitea version (or commit ref):
  • Git version:1.12.4
  • Operating system:linux
  • 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/09/11 02:15:02 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT * FROM team INNER JOIN team_user ON team_user.team_id = team.id INNER JOIN team_repo ON team_repo.team_id = team.id WHERE (team.org_id = ?) AND (team_user.uid=?) AND (team_repo.repo_id=?) [3 5 124] - 364.565964ms
2020/09/11 02:15:02 ...er/issues/indexer.go:228:func3() [F] Issue Indexer Initialization timed-out after: 30s
2020/09/11 02:16:21 ...dules/setting/log.go:279:newLogService() [I] Gitea Log Mode: File(File:info)
2020/09/11 02:16:21 ...les/setting/cache.go:70:newCacheService() [I] Cache Service Enabled
2020/09/11 02:16:21 ...les/setting/cache.go:81:newCacheService() [I] Last Commit Cache Service Enabled
2020/09/11 02:16:21 ...s/setting/session.go:63:newSessionService() [I] Session Service Enabled
2020/09/11 02:16:21 routers/init.go:63:initDBEngine() [I] Beginning ORM engine initialization.
2020/09/11 02:16:21 routers/init.go:70:initDBEngine() [I] ORM engine initialization attempt #1/10...
2020/09/11 02:16:21 ...rm/session_schema.go:25:Ping() [I] PING DATABASE mysql

Description

gitea often restart and see 502 Bad Gateway. see in log: er/issues/indexer.go:228:func3() [F] Issue Indexer Initialization timed-out after: 30s

[indexer]
REPO_INDEXER_ENABLED = false

Add this config, it did not work also.

Screenshots

Originally created by @fansat on GitHub (Sep 11, 2020). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): - Git version:1.12.4 - Operating system:linux - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [ ] Not relevant - Log gist: 2020/09/11 02:15:02 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT * FROM `team` INNER JOIN `team_user` ON team_user.team_id = team.id INNER JOIN `team_repo` ON team_repo.team_id = team.id WHERE (team.org_id = ?) AND (team_user.uid=?) AND (team_repo.repo_id=?) [3 5 124] - 364.565964ms 2020/09/11 02:15:02 ...er/issues/indexer.go:228:func3() [F] Issue Indexer Initialization timed-out after: 30s 2020/09/11 02:16:21 ...dules/setting/log.go:279:newLogService() [I] Gitea Log Mode: File(File:info) 2020/09/11 02:16:21 ...les/setting/cache.go:70:newCacheService() [I] Cache Service Enabled 2020/09/11 02:16:21 ...les/setting/cache.go:81:newCacheService() [I] Last Commit Cache Service Enabled 2020/09/11 02:16:21 ...s/setting/session.go:63:newSessionService() [I] Session Service Enabled 2020/09/11 02:16:21 routers/init.go:63:initDBEngine() [I] Beginning ORM engine initialization. 2020/09/11 02:16:21 routers/init.go:70:initDBEngine() [I] ORM engine initialization attempt #1/10... 2020/09/11 02:16:21 ...rm/session_schema.go:25:Ping() [I] PING DATABASE mysql ## Description gitea often restart and see 502 Bad Gateway. see in log: er/issues/indexer.go:228:func3() [F] Issue Indexer Initialization timed-out after: 30s [indexer] REPO_INDEXER_ENABLED = false Add this config, it did not work also. ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror commented 2025-11-02 06:42:00 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Sep 11, 2020):

It is said Issue Indexer Initialization timed-out after: 30s but not repository indexer.

@lunny commented on GitHub (Sep 11, 2020): It is said `Issue Indexer Initialization timed-out after: 30s` but not repository indexer.
GiteaMirror commented 2025-11-02 06:42:01 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Sep 11, 2020):

Just to be clearer ISSUE indexer not repository.

It's likely that the data in data/indexers/issues.* is corrupt and you should just delete them.

@zeripath commented on GitHub (Sep 11, 2020): Just to be clearer **ISSUE** indexer not repository. It's likely that the data in data/indexers/issues.* is corrupt and you should just delete them.
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
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#5986
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?