Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:

CRM
e-Commerce
Účtovníctvo
Sklady
PoS
Projektové riadenie
MRP

All apps

All Posts People Badges

Tagy (View all)

odoo accounting v14 pos v15

About this forum

Pomoc

could not obtain lock on row in relation "ir_cron"

cron postgresql lock

7 Replies

53261 Zobrazenia

Mathias Colpaert

In my postgresql log, I see following error (keeps on beeing logged over and over):

2015-01-28 17:40:26 UTC ERROR: could not obtain lock on row in relation "ir_cron"
2015-01-28 17:40:26 UTC STATEMENT: SELECT *
   FROM ir_cron
   WHERE numbercall != 0
   AND active
   AND nextcall <= (now() at time zone 'UTC')
   AND id=2
   FOR UPDATE NOWAIT
2015-01-28 17:41:32 UTC ERROR: could not obtain lock on row in relation "ir_cron"
2015-01-28 17:41:32 UTC STATEMENT: SELECT *
   FROM ir_cron
   WHERE numbercall != 0
   AND active
   AND nextcall <= (now() at time zone 'UTC')
   AND id=7
   FOR UPDATE NOWAIT
2015-01-28 18:36:39 UTC ERROR: could not obtain lock on row in relation "ir_cron"
2015-01-28 18:36:39 UTC STATEMENT: SELECT *
   FROM ir_cron
   WHERE numbercall != 0
   AND active
   AND nextcall <= (now() at time zone 'UTC')
   AND id=1
   FOR UPDATE NOWAIT
2015-01-28 19:30:44 UTC ERROR: could not obtain lock on row in relation "ir_cron"
2015-01-28 19:30:44 UTC STATEMENT: SELECT *
   FROM ir_cron
   WHERE numbercall != 0
   AND active
   AND nextcall <= (now() at time zone 'UTC')
   AND id=9
   FOR UPDATE NOWAIT
2015-01-28 19:36:57 UTC ERROR: could not obtain lock on row in relation "ir_cron"
2015-01-28 19:36:57 UTC STATEMENT: SELECT *
   FROM ir_cron
   WHERE numbercall != 0
   AND active
   AND nextcall <= (now() at time zone 'UTC')
   AND id=1
   FOR UPDATE NOWAIT
2015-01-28 19:41:07 UTC ERROR: could not obtain lock on row in relation "ir_cron"
2015-01-28 19:41:07 UTC STATEMENT: SELECT *
   FROM ir_cron
   WHERE numbercall != 0
   AND active
   AND nextcall <= (now() at time zone 'UTC')
   AND id=2
   FOR UPDATE NOWAIT
2015-01-28 19:41:16 UTC ERROR: could not obtain lock on row in relation "ir_cron"
2015-01-28 19:41:16 UTC STATEMENT: SELECT *
   FROM ir_cron
   WHERE numbercall != 0
   AND active
   AND nextcall <= (now() at time zone 'UTC')
   AND id=7
   FOR UPDATE NOWAIT
2015-01-28 21:11:30 UTC ERROR: could not obtain lock on row in relation "ir_cron"
2015-01-28 21:11:30 UTC STATEMENT: SELECT *
   FROM ir_cron
   WHERE numbercall != 0
   AND active
   AND nextcall <= (now() at time zone 'UTC')
   AND id=7
   FOR UPDATE NOWAIT
2015-01-28 23:30:43 UTC ERROR: could not obtain lock on row in relation "ir_cron"
2015-01-28 23:30:43 UTC STATEMENT: SELECT *
   FROM ir_cron
   WHERE numbercall != 0
   AND active
   AND nextcall <= (now() at time zone 'UTC')
   AND id=9
   FOR UPDATE NOWAIT
2015-01-28 23:36:55 UTC ERROR: could not obtain lock on row in relation "ir_cron"
2015-01-28 23:36:55 UTC STATEMENT: SELECT *
   FROM ir_cron
   WHERE numbercall != 0
   AND active
   AND nextcall <= (now() at time zone 'UTC')
   AND id=1
   FOR UPDATE NOWAIT
2015-01-28 23:41:03 UTC ERROR: could not obtain lock on row in relation "ir_cron"
2015-01-28 23:41:03 UTC STATEMENT: SELECT *
   FROM ir_cron
   WHERE numbercall != 0
   AND active
   AND nextcall <= (now() at time zone 'UTC')
   AND id=2
   FOR UPDATE NOWAIT
2015-01-28 23:41:14 UTC ERROR: could not obtain lock on row in relation "ir_cron"
2015-01-28 23:41:14 UTC STATEMENT: SELECT *
   FROM ir_cron
   WHERE numbercall != 0
   AND active
   AND nextcall <= (now() at time zone 'UTC')
   AND id=7
   FOR UPDATE NOWAIT
2015-01-29 03:07:02 UTC ERROR: could not obtain lock on row in relation "ir_cron"
2015-01-29 03:07:02 UTC STATEMENT: SELECT *
   FROM ir_cron
   WHERE numbercall != 0
   AND active
   AND nextcall <= (now() at time zone 'UTC')
   AND id=1
   FOR UPDATE NOWAIT
2015-01-29 04:07:25 UTC ERROR: could not obtain lock on row in relation "ir_cron"
2015-01-29 04:07:25 UTC STATEMENT: SELECT *
   FROM ir_cron
   WHERE numbercall != 0
   AND active
   AND nextcall <= (now() at time zone 'UTC')
   AND id=1
   FOR UPDATE NOWAIT

What is causing this error?

I have following configuration:

Odoo v8.0
Ubuntu 14.04 LTS on vps
No outgoing mailserver configured

Bernard

Best Answer

Please check your ir_cron actions for "scheduled actions" that have very small interval_time like 1 minute interval. It is likely that the next run is starting before the previous one is finished (LOCKED FOR UPDATE). This happens in scheduled actions like fetching mail from your mail server which may take longer than 1 or 2 minutes due to connection issues or alot of emails to download.

The setting max_cron_threads=1 apparently causes another issue though. Cron jobs are just stopping to work after a few days until the docker container gets restarted.

e_sjuhain@sana.iq

In my case, it turned out there was a cron that a previous developer added to the system that was always running and never getting done. I inspected the Odoo log file for ir_cron logs. A pair of starting/done logs look like so:

2024-05-30 10:09:29,891 481994 INFO HalaFTTH_db odoo.addons.base.models.ir_cron: Starting job Jobs Garbage Collector.

2024-05-30 10:09:29,895 481994 INFO HalaFTTH_db odoo.addons.base.models.ir_cron: Job Jobs Garbage Collector done.

However, my long running cron only had a 'Starting' but never a 'done' log line. When I turned off that cron, the module upgraded normally.

Yves Goldberg

Same situation here, also looking for an answer.

Ermin Trevisan

Same situation here, also looking for an answer.

Jens Roehrssen

It seems that if the postgresql server comes up again after being down for a while, odoo tries to run all missed cron entries at once. This results in a bunch of those errors within seconds.

Zbik

You verify how many openerp server instances have run.

>ps aux | grep oepenrp

or, you set in openerp-server.conf

max_cron_threads = 1

This appears to be because two cron threads run the same command.

Mathias Colpaert

Autor

I only have 1 server instance running. max_cron_threads is set to 2, but if this is the bug, why does this option even exist? Should I always put max_cron_threads = 1, and why?

Zbik

If the whole system works properly, settings max_cron_threads = 2 is good.

Enjoying the discussion? Don't just read, join in!

Create an account today to enjoy exclusive features and engage with our awesome community!

Registrácia

Related Posts	Replies	Zobrazenia
ir.cron - Record cannot be modified right now cron scheduler postgresql lock	3 mar 15	22322
CRONs aren't executed after a certain time cron postgresql odoo16features	3 apr 24	4907
TransactionRollbackError due to concurrent update. cron table lock	1 mar 15	9180
When Odoo 14 connects to PostgreSQL 15.7, the connection is idle but cannot be released postgresql	0 feb 25	3079
psycopg2.OperationalError: connection to server at "localhost" (::1), port 5432 failed: fe_sendauth: no password supplied postgresql	2 jan 25	10434

This question has been flagged

Enjoying the discussion? Don't just read, join in!