Skip to Content
Menu
This question has been flagged
1 Reply
7646 Views

I was trying a reading operation with OdooLocust module on product.template. User was 40 and spawn rate were 1. 
After few minute locust rps gets 0 

I went to check from UI and saw that server stopped responding. The server was running on a linux vm with docker environment but the database was in AWS. 

I restarted the docker with docker compose but next what I see was like this

```

| Traceback (most recent call last):

odoo-16-docker-odoo-1  |   File "/usr/lib/python3/dist-packages/odoo/addons/base/models/ir_cron.py", line 115, in _process_jobs

odoo-16-docker-odoo-1  |     registry = odoo.registry(db_name)

odoo-16-docker-odoo-1  |   File "/usr/lib/python3/dist-packages/odoo/__init__.py", line 104, in registry

odoo-16-docker-odoo-1  |     return modules.registry.Registry(database_name)

odoo-16-docker-odoo-1  |   File "/usr/lib/python3/dist-packages/odoo/modules/registry.py", line 67, in __new__

odoo-16-docker-odoo-1  |     return cls.new(db_name)

odoo-16-docker-odoo-1  |   File "", line 2, in new

odoo-16-docker-odoo-1  |   File "/usr/lib/python3/dist-packages/odoo/tools/func.py", line 87, in locked

odoo-16-docker-odoo-1  |     return func(inst, *args, **kwargs)

odoo-16-docker-odoo-1  |   File "/usr/lib/python3/dist-packages/odoo/modules/registry.py", line 91, in new

odoo-16-docker-odoo-1  |     odoo.modules.load_modules(registry, force_demo, status, update_module)

odoo-16-docker-odoo-1  |   File "/usr/lib/python3/dist-packages/odoo/modules/loading.py", line 478, in load_modules

odoo-16-docker-odoo-1  |     processed_modules += load_marked_modules(cr, graph,

odoo-16-docker-odoo-1  |   File "/usr/lib/python3/dist-packages/odoo/modules/loading.py", line 371, in load_marked_modules

odoo-16-docker-odoo-1  |     loaded, processed = load_module_graph(

odoo-16-docker-odoo-1  |   File "/usr/lib/python3/dist-packages/odoo/modules/loading.py", line 207, in load_module_graph

odoo-16-docker-odoo-1  |     registry.init_models(cr, model_names, {'module': package.name}, new_install)

odoo-16-docker-odoo-1  |   File "/usr/lib/python3/dist-packages/odoo/modules/registry.py", line 453, in init_models

odoo-16-docker-odoo-1  |     model._auto_init()

odoo-16-docker-odoo-1  |   File "/usr/lib/python3/dist-packages/odoo/models.py", line 2591, in _auto_init

odoo-16-docker-odoo-1  |     self._check_removed_columns(log=False)

odoo-16-docker-odoo-1  |   File "/usr/lib/python3/dist-packages/odoo/models.py", line 2514, in _check_removed_columns

odoo-16-docker-odoo-1  |     tools.drop_not_null(cr, self._table, row['attname'])

odoo-16-docker-odoo-1  |   File "/usr/lib/python3/dist-packages/odoo/tools/sql.py", line 189, in drop_not_null

odoo-16-docker-odoo-1  |     cr.execute('ALTER TABLE "{}" ALTER COLUMN "{}" DROP NOT NULL'.format(tablename, columnname))

odoo-16-docker-odoo-1  |   File "/usr/lib/python3/dist-packages/odoo/sql_db.py", line 315, in execute

odoo-16-docker-odoo-1  |     res = self._obj.execute(query, params)

odoo-16-docker-odoo-1  | psycopg2.errors.LockNotAvailable: canceling statement due to lock timeout


```

I suspect this is something with postgres. Is there any workaround for this. 
Any help is appreciated. 


Avatar
Discard
Best Answer

Please log_lock_waits = on in postgresql.conf and restart the posrgres

Avatar
Discard
Related Posts Replies Views Activity
1
Feb 24
1243
3
Apr 23
2617
0
Nov 22
1571
0
Jan 24
161
0
Oct 23
724