Timeout error attempting to create internal queue for task #5341

Closed
opened 2025-11-02 06:22:05 -06:00 by GiteaMirror · 7 comments
Owner

Originally created by @lunny on GitHub (May 2, 2020).

2020/05/02 17:23:02 ...ueue_disk_channel.go:144:Run() [F] Unable to create internal queue for task Error: Timedout creating queue level with cfg queue.LevelQueueConfiguration{ByteFIFOQueueConfiguration:queue.ByteFIFOQueueConfiguration{WorkerPoolConfiguration:queue.WorkerPoolConfiguration{QueueLength:1000, BatchLength:20, BlockTimeout:1000000000, BoostTimeout:300000000000, BoostWorkers:5, MaxWorkers:6}, Workers:1, Name:"task-level"}, DataDir:"/data/gitea/data/queues/task"} in task
Originally created by @lunny on GitHub (May 2, 2020). ```log 2020/05/02 17:23:02 ...ueue_disk_channel.go:144:Run() [F] Unable to create internal queue for task Error: Timedout creating queue level with cfg queue.LevelQueueConfiguration{ByteFIFOQueueConfiguration:queue.ByteFIFOQueueConfiguration{WorkerPoolConfiguration:queue.WorkerPoolConfiguration{QueueLength:1000, BatchLength:20, BlockTimeout:1000000000, BoostTimeout:300000000000, BoostWorkers:5, MaxWorkers:6}, Workers:1, Name:"task-level"}, DataDir:"/data/gitea/data/queues/task"} in task ```
GiteaMirror added the issue/confirmedtype/bug labels 2025-11-02 06:22:05 -06:00
Author
Owner

@zeripath commented on GitHub (May 4, 2020):

Presumably there are some logs preceding this. The issue is that the persistent queue for the task is locked and can't be opened.

@zeripath commented on GitHub (May 4, 2020): Presumably there are some logs preceding this. The issue is that the persistent queue for the task is locked and can't be opened.
Author
Owner

@stale[bot] commented on GitHub (Jul 3, 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[bot] commented on GitHub (Jul 3, 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.
Author
Owner

@mbedded commented on GitHub (Jul 18, 2020):

I run into this error as i updated from 1.11.3 to 1.12.3 today.
The server is not started and i can't access the website via browser.

EDIT:
I tried all 1.12.x versions on a Raspberry Pi 4 and none of them is working. Everyone writes the same error message into the logfile.
I updated 1.11.3 to 1.11.8 (arm-6) this version works without any issues.

EDIT2:
I tried a new run with 1.12.3 and i get the following error:
Error: migrate: do migrate: Error 1118: Row size too large.

$ cat /var/log/gitea/gitea.log
2020/08/09 18:20:12 routers/init.go:70:initDBEngine() [I] ORM engine initialization attempt #2/10...
2020/08/09 18:20:12 ...rm/session_schema.go:25:Ping() [I] PING DATABASE mysql
2020/08/09 18:20:12 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT `TABLE_NAME` from `INFORMATION_SCHEMA`.`TABLES` WHERE `TABLE_SCHEMA`=? and `TABLE_NAME`=? [Gitea version] - 2.574358ms
2020/08/09 18:20:12 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT `COLUMN_NAME` FROM `INFORMATION_SCHEMA`.`COLUMNS` WHERE `TABLE_SCHEMA` = ? AND `TABLE_NAME` = ? AND `COLUMN_NAME` = ? [Gitea version id] - 2.32436ms
2020/08/09 18:20:12 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT `COLUMN_NAME` FROM `INFORMATION_SCHEMA`.`COLUMNS` WHERE `TABLE_SCHEMA` = ? AND `TABLE_NAME` = ? AND `COLUMN_NAME` = ? [Gitea version version] - 2.437068ms
2020/08/09 18:20:12 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT `id`, `version` FROM `version` WHERE `id`=? LIMIT 1 [1] - 1.652542ms
2020/08/09 18:20:12 ...ations/migrations.go:300:Migrate() [I] Migration[121]: add is_restricted column for users table
2020/08/09 18:20:12 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT `TABLE_NAME`, `ENGINE`, `AUTO_INCREMENT`, `TABLE_COMMENT` from `INFORMATION_SCHEMA`.`TABLES` WHERE `TABLE_SCHEMA`=? AND (`ENGINE`='MyISAM' OR `ENGINE` = 'InnoDB' OR `ENGINE` = 'TokuDB') [Gitea] - 5.111321ms
2020/08/09 18:20:12 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT `COLUMN_NAME`, `IS_NULLABLE`, `COLUMN_DEFAULT`, `COLUMN_TYPE`, `COLUMN_KEY`, `EXTRA`,`COLUMN_COMMENT` FROM `INFORMATION_SCHEMA`.`COLUMNS` WHERE `TABLE_SCHEMA` = ? AND `TABLE_NAME` = ? [Gitea user] - 4.654553ms
2020/08/09 18:20:12 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT `INDEX_NAME`, `NON_UNIQUE`, `COLUMN_NAME` FROM `INFORMATION_SCHEMA`.`STATISTICS` WHERE `TABLE_SCHEMA` = ? AND `TABLE_NAME` = ? [Gitea user] - 2.274516ms
2020/08/09 18:20:12 ...m.io/xorm/core/db.go:277:ExecContext() [I] [SQL] ALTER TABLE `user` ADD `is_restricted` TINYINT(1) DEFAULT false NOT NULL  [] - 1.962487ms
2020/08/09 18:20:12 routers/init.go:76:initDBEngine() [E] ORM engine initialization attempt #2/10 failed. Error: migrate: do migrate: Error 1118: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs
2020/08/09 18:20:12 routers/init.go:77:initDBEngine() [I] Backing off for 3 seconds

@mbedded commented on GitHub (Jul 18, 2020): I run into this error as i updated from 1.11.3 to 1.12.3 today. The server is not started and i can't access the website via browser. EDIT: I tried all 1.12.x versions on a Raspberry Pi 4 and none of them is working. Everyone writes the same error message into the logfile. I updated 1.11.3 to 1.11.8 (arm-6) this version works without any issues. EDIT2: I tried a new run with 1.12.3 and i get the following error: Error: migrate: do migrate: Error 1118: Row size too large. ``` $ cat /var/log/gitea/gitea.log 2020/08/09 18:20:12 routers/init.go:70:initDBEngine() [I] ORM engine initialization attempt #2/10... 2020/08/09 18:20:12 ...rm/session_schema.go:25:Ping() [I] PING DATABASE mysql 2020/08/09 18:20:12 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT `TABLE_NAME` from `INFORMATION_SCHEMA`.`TABLES` WHERE `TABLE_SCHEMA`=? and `TABLE_NAME`=? [Gitea version] - 2.574358ms 2020/08/09 18:20:12 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT `COLUMN_NAME` FROM `INFORMATION_SCHEMA`.`COLUMNS` WHERE `TABLE_SCHEMA` = ? AND `TABLE_NAME` = ? AND `COLUMN_NAME` = ? [Gitea version id] - 2.32436ms 2020/08/09 18:20:12 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT `COLUMN_NAME` FROM `INFORMATION_SCHEMA`.`COLUMNS` WHERE `TABLE_SCHEMA` = ? AND `TABLE_NAME` = ? AND `COLUMN_NAME` = ? [Gitea version version] - 2.437068ms 2020/08/09 18:20:12 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT `id`, `version` FROM `version` WHERE `id`=? LIMIT 1 [1] - 1.652542ms 2020/08/09 18:20:12 ...ations/migrations.go:300:Migrate() [I] Migration[121]: add is_restricted column for users table 2020/08/09 18:20:12 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT `TABLE_NAME`, `ENGINE`, `AUTO_INCREMENT`, `TABLE_COMMENT` from `INFORMATION_SCHEMA`.`TABLES` WHERE `TABLE_SCHEMA`=? AND (`ENGINE`='MyISAM' OR `ENGINE` = 'InnoDB' OR `ENGINE` = 'TokuDB') [Gitea] - 5.111321ms 2020/08/09 18:20:12 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT `COLUMN_NAME`, `IS_NULLABLE`, `COLUMN_DEFAULT`, `COLUMN_TYPE`, `COLUMN_KEY`, `EXTRA`,`COLUMN_COMMENT` FROM `INFORMATION_SCHEMA`.`COLUMNS` WHERE `TABLE_SCHEMA` = ? AND `TABLE_NAME` = ? [Gitea user] - 4.654553ms 2020/08/09 18:20:12 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT `INDEX_NAME`, `NON_UNIQUE`, `COLUMN_NAME` FROM `INFORMATION_SCHEMA`.`STATISTICS` WHERE `TABLE_SCHEMA` = ? AND `TABLE_NAME` = ? [Gitea user] - 2.274516ms 2020/08/09 18:20:12 ...m.io/xorm/core/db.go:277:ExecContext() [I] [SQL] ALTER TABLE `user` ADD `is_restricted` TINYINT(1) DEFAULT false NOT NULL [] - 1.962487ms 2020/08/09 18:20:12 routers/init.go:76:initDBEngine() [E] ORM engine initialization attempt #2/10 failed. Error: migrate: do migrate: Error 1118: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs 2020/08/09 18:20:12 routers/init.go:77:initDBEngine() [I] Backing off for 3 seconds ```
Author
Owner

@stale[bot] commented on GitHub (Oct 10, 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[bot] commented on GitHub (Oct 10, 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.
Author
Owner

@lunny commented on GitHub (Feb 18, 2021):

Presumably there are some logs preceding this. The issue is that the persistent queue for the task is locked and can't be opened.

But cannot know this from the log information.

@lunny commented on GitHub (Feb 18, 2021): > Presumably there are some logs preceding this. The issue is that the persistent queue for the task is locked and can't be opened. But cannot know this from the log information.
Author
Owner

@adyanth commented on GitHub (Feb 26, 2022):

Seeing something similar to this on 1.16.2 as well. Promptly crashes in 2 minutes after coming up. (not timeout tho, opening a new bug)

@adyanth commented on GitHub (Feb 26, 2022): Seeing something similar to this on 1.16.2 as well. Promptly crashes in 2 minutes after coming up. (not timeout tho, opening a new bug)
Author
Owner

@lunny commented on GitHub (Feb 26, 2022):

Let's move to your issue and close this one.

@lunny commented on GitHub (Feb 26, 2022): Let's move to your issue and close this one.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#5341