github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Unable to create internal queue for push_update Error (Docker Swarm) #7340

New Issue
Closed
opened 2025-11-02 07:23:24 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-02 07:23:24 -06:00
Owner
Copy Link

Originally created by @TheSilkky on GitHub (May 15, 2021).

  • Gitea version (or commit ref): 1.15.0+dev-303-gb6b8b194c
  • Git version: 2.30.2
  • Operating system: docker-swarm mode (Docker version 20.10.6)
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
  • Log gist: 
    2021/05/15 08:09:49 ...ueue_disk_channel.go:144:Run() [F] Unable to create internal queue for push_update Error: Unable to create queue level for push_update with cfg queue.LevelQueueConfiguration{ByteFIFOQueueConfiguration:queue.ByteFIFOQueueConfiguration{WorkerPoolConfiguration:queue.WorkerPoolConfiguration{QueueLength:20, BatchLength:20, BlockTimeout:1000000000, BoostTimeout:300000000000, BoostWorkers:1, MaxWorkers:5}, Workers:0, Name:"push_update-level"}, DataDir:"/data/gitea/queues/push_update", ConnectionString:"", QueueName:""} by max attempts: error: resource temporarily unavailable

Full server logs
app.ini

Description

docker-compose
Gitea is accessible from the web-ui and everything appears to work fine, but regularly a "bad gateway" error appears, after looking in the logs you can see Unable to create internal queue for push_update Error: Unable to create queue level for push_update with cfg and shortly after Received signal 15; terminating. The container crashes.

Extra details:

  • Postgres is running on only 1 node. The others communicate with it over an overlay network.
  • I'm using GlusterFS to store the persistent Gitea data.

Screenshots

Cluster diagram

Originally created by @TheSilkky on GitHub (May 15, 2021). <!-- 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. Make sure it's not mentioned in the FAQ (https://docs.gitea.io/en-us/faq) 5. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.15.0+dev-303-gb6b8b194c - Git version: 2.30.2 - Operating system: docker-swarm mode (Docker version 20.10.6) <!-- Please include information on whether you built gitea yourself, used one of our downloads or are using some other package --> <!-- Please also tell us how you are running gitea, e.g. if it is being run from docker, a command-line, systemd etc. ---> <!-- If you are using a package or systemd tell us what distribution you are using --> - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - Log gist: ``` 2021/05/15 08:09:49 ...ueue_disk_channel.go:144:Run() [F] Unable to create internal queue for push_update Error: Unable to create queue level for push_update with cfg queue.LevelQueueConfiguration{ByteFIFOQueueConfiguration:queue.ByteFIFOQueueConfiguration{WorkerPoolConfiguration:queue.WorkerPoolConfiguration{QueueLength:20, BatchLength:20, BlockTimeout:1000000000, BoostTimeout:300000000000, BoostWorkers:1, MaxWorkers:5}, Workers:0, Name:"push_update-level"}, DataDir:"/data/gitea/queues/push_update", ConnectionString:"", QueueName:""} by max attempts: error: resource temporarily unavailable ``` [Full server logs](https://bin.snopyta.org/?792d861770a7deda#CvT9C5sM98BnzTRtJR8DAfsQgZBSEtw5UPdYMUxTw6qr) [app.ini](https://bin.snopyta.org/?e27dc2b9e3a047e1#2S6Xvt1wK9PvhNAtMq73kAM2WtYTfTSuBFBijE6mP5eC) <!-- It really is important to provide pertinent logs --> <!-- Please read https://docs.gitea.io/en-us/logging-configuration/#debugging-problems --> <!-- In addition, if your problem relates to git commands set `RUN_MODE=dev` at the top of app.ini --> ## Description <!-- If using a proxy or a CDN (e.g. CloudFlare) in front of gitea, please disable the proxy/CDN fully and connect to gitea directly to confirm the issue still persists without those services. --> [docker-compose](https://bin.snopyta.org/?ab5e575306c3f2f8#FaceKvrqX37m9Y5KRK7dsSHgRkFdKr5oBnYnYQr6PiS7) Gitea is accessible from the web-ui and everything appears to work fine, but regularly a "bad gateway" error appears, after looking in the logs you can see ```Unable to create internal queue for push_update Error: Unable to create queue level for push_update with cfg``` and shortly after ```Received signal 15; terminating```. The container crashes. Extra details: - Postgres is running on only 1 node. The others communicate with it over an overlay network. - I'm using GlusterFS to store the persistent Gitea data. ## Screenshots ![Cluster diagram](https://i.postimg.cc/HkHkKrZ8/cluster.png) <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the type/question label 2025-11-02 07:23:24 -06:00
GiteaMirror commented 2025-11-02 07:23:26 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (May 15, 2021):

 resource temporarily unavailable

implies that the directory /data/gitea/queues/push_update cannot be accessed.

@zeripath commented on GitHub (May 15, 2021): ``` resource temporarily unavailable ``` implies that the directory `/data/gitea/queues/push_update` cannot be accessed.
GiteaMirror commented 2025-11-02 07:23:26 -06:00
Author
Owner
Copy Link

@TheSilkky commented on GitHub (May 15, 2021):

 resource temporarily unavailable

implies that the directory /data/gitea/queues/push_update cannot be accessed.

Might be a permissions problems with the mounted data directory. Ill have a look when I have time, thanks

@TheSilkky commented on GitHub (May 15, 2021): > ``` > resource temporarily unavailable > ``` > > implies that the directory `/data/gitea/queues/push_update` cannot be accessed. Might be a permissions problems with the mounted data directory. Ill have a look when I have time, thanks
GiteaMirror commented 2025-11-02 07:23:26 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (May 15, 2021):

You have multiple processes accessing the queue simultaneously, please consider using redis as a queue manager. Currently HA/multi-home is not thoroughly documented and so please refer to the HA ticket for more details.

@techknowlogick commented on GitHub (May 15, 2021): You have multiple processes accessing the queue simultaneously, please consider using redis as a queue manager. Currently HA/multi-home is not thoroughly documented and so please refer to the HA ticket for more details.
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#7340
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?