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

[18.0] Job stuck in Enqueued state #751

Open
enricodg opened this issue Mar 7, 2025 · 1 comment
Open

[18.0] Job stuck in Enqueued state #751

enricodg opened this issue Mar 7, 2025 · 1 comment
Labels

Comments

@enricodg
Copy link

enricodg commented Mar 7, 2025

Module

queue_job

Describe the bug

Job get stuck in Enqueued

To Reproduce

Affected versions: 18.0

Steps to reproduce the behavior:

  1. I just tested the module in local with the url http://odoo.local:8080/queue_job/create_test_job
  2. Here's my odoo.conf:
[options]
addons_path =  xxx
admin_passwd =  xxx
db_name = odoo18
db_host = localhost
db_port = 5432
db_user =
db_password =
workers = 6
server_wide_modules = web,queue_job
max_cron_threads = 1
proxy_mode = True
[queue_job]
channels = root:2
scheme = http
host = odoo.local
port = 8080
  1. I have tested with proxy equal to True/False. But does not change anything
  2. I tried to debug, and when calling requests.get(url) the module does nothing? It logs :
2025-03-07 13:59:11,055 50596 DEBUG ? odoo.addons.queue_job.jobrunner.channels: job 987c8fc8-e9de-4949-9a3d-45d7e1eab1b8 marked pending in channel root(C:2,Q:1,R:0,F:0) 
2025-03-07 13:59:11,057 50596 DEBUG ? odoo.addons.queue_job.jobrunner.channels: job 987c8fc8-e9de-4949-9a3d-45d7e1eab1b8 marked running in channel root(C:2,Q:0,R:1,F:0) 
2025-03-07 13:59:11,057 50596 INFO ? odoo.addons.queue_job.jobrunner.runner: asking Odoo to run job 987c8fc8-e9de-4949-9a3d-45d7e1eab1b8 on db odoo18 
2025-03-07 13:59:11,067 50596 DEBUG ? odoo.addons.queue_job.jobrunner.runner: select() timeout: 60.00 sec 
2025-03-07 13:59:11,074 50574 INFO odoo18 odoo.addons.queue_job.jobrunner.channels: Configured channel: root(C:2,Q:0,R:0,F:0) 
2025-03-07 13:59:11,078 50632 INFO odoo18 odoo.service.server: Worker WorkerJobRunner (50632) alive 
2025-03-07 13:59:11,080 50632 DEBUG ? odoo.addons.queue_job.jobrunner: WorkerJobRunner (50632) starting up 
2025-03-07 13:59:16,086 50632 INFO ? odoo.addons.queue_job.jobrunner.runner: starting 
2025-03-07 13:59:16,088 50632 INFO ? odoo.addons.queue_job.jobrunner.runner: initializing database connections 
2025-03-07 13:59:16,116 50632 DEBUG ? odoo.addons.queue_job.jobrunner.channels: job 987c8fc8-e9de-4949-9a3d-45d7e1eab1b8 marked running in channel root(C:2,Q:0,R:1,F:0) 
2025-03-07 13:59:16,117 50632 INFO ? odoo.addons.queue_job.jobrunner.runner: queue job runner ready for db odoo18 
2025-03-07 13:59:16,118 50632 INFO ? odoo.addons.queue_job.jobrunner.runner: database connections ready 
2025-03-07 13:59:16,118 50632 DEBUG ? odoo.addons.queue_job.jobrunner.runner: select() timeout: 60.00 sec 
  1. If i change the workers to 0 it works just fine

Expected behavior
Should not stuck in Enqueued and should be Done state?

Additional context
I'm running python 3.11.10

@enricodg enricodg added the bug label Mar 7, 2025
@enricodg
Copy link
Author

enricodg commented Mar 7, 2025

i think it's because the db_name. if i use dbfilter it works fine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant