1. Mailing Lists
  2. Connectors
  3. ERROR: could not serialize access due to concurrent update

Connectors mailing list archives

connectors@odoo-community.org

Browse archives

Re: Configuration with multiple Odoo nodes

Re: Configuration with multiple Odoo nodes

Avatar

ERROR: could not serialize access due to concurrent update

by
Open Source Integrators, Maxime Chambreuil
- 10/07/2019 21:09:44
Hello,

I am running the voicent connector:

and I get the following message when the job is set to done:

2019-07-10 13:30:38.748 CDT [28944] odoo@12.4-RC3 ERROR:  could not serialize access due to concurrent update
2019-07-10 13:30:38.748 CDT [28944] odoo@12.4-RC3 STATEMENT:  UPDATE "queue_job" SET "state"='done',"priority"=10,"retry"=1,"max_retries"=5,"exc_info"=NULL,"user_id"=2,"company_id"=1,"result"=NULL,"date_enqueued"='2019-07-10 18:26:17',"date_started"='2019-07-10 18:26:17.556418',"date_done"='2019-07-10 18:30:38.746397',"eta"='2019-07-10 18:20:33.496558',"identity_key"=NULL WHERE id IN (7)

In pg_activity, I have this query that keeps running:

SELECT "backend_voicent"."id" as "id","backend_voicent"."create_date" as "create_date","backend_voicent"."write_date" as "write_date","backend_voicent"."li
 ne" as "line","backend_voicent"."callerid" as "callerid","backend_voicent"."write_uid" as "write_uid","backend_voicent"."create_uid" as "create_uid","backend_voicent"."host" as "host","backend_voicent"."port" as "port","backend_voicent"."active" as "active","backend_voicent"."name
  as "name","backend_voicent"."next_call" as "next_call" FROM "backend_voicent" WHERE "backend_voicent".id IN (1)

From I read, it sounds like the transaction is not committed or an autocommit is expected somewhere.

Can someone help? Any hint?

MAXIME CHAMBREUIL
PROJECT MANAGER/CONSULTANT
O: 1.855.877.2377 EXT. 710
M: 602.427.5632
E: MChambreuil@OpenSourcelntegrators.com
P.O. BOX 940, HIGLEY, AZ 85236