Skip to Content
Meniu
Trebuie să fiți înregistrat pentru a interacționa cu comunitatea.
Această întrebare a fost marcată
3 Răspunsuri
12188 Vizualizări

this instance has been running for a few months now and it has ocurred a few times, three or four, that all scheduled task stops working, they no longer execute regardless of interval, the next execution date is not updated and the effects one expects from the tasks are not performed, i also checked adding log("something") to some task to see if the mesages were logged in ir.logging but no, the problem was solved when i restarted the postgresql service, initially i thought it was due to some heavy task having very little intervals, like 5 minutes for the Mail: Fetchmail Service, but upon increasing to one hour, the problem has ocurred again, both the incoming and outgoing mail server is office365.com, what could be the cause of such behavior? it is a bug? could be a misconfiguration?

UPDATE

The solution was to leave a single database


Imagine profil
Abandonează

If you have some custom addons and if addons are not updating properly then you might face this issue so try to update custom addons.

i have the same problem

Cel mai bun răspuns

Hello There,

Am having the same issue and it's causing me a lot of problems because am using some custom crons that are important for my clients workflow.

NOTE: Restarting  postgresql did not solve the issue even temporarily.

Please if you found any solution post it, so me and others could benefit from it.


The Solution I Found:

I recently found out that specifying a db_host, db_name, db_password,db_port,db_user

in the /etc/odoo/odoo.conf

will solve the issue.

And After digging deep, i found that the day my problem started was the exact day that i created another database in that instance of odoo.

best of regards.

Imagine profil
Abandonează

you can create as many database as u want and that will not stop the cron jobs
some problems came from the OS

This worked for me with two databases.
I had to put the parameters in the run command instead of the odoo.conf because of a certain docker configuration we are using, but it worked and the crons started running as soon as the server went up

Cel mai bun răspuns

I ran into this problem recently the issue was the uninstallation of an app. The odoo.log showed actions failing because of a missing field in the db due to the uninstall.

A simple restart of the odoo server resolved it. 

Imagine profil
Abandonează
Cel mai bun răspuns

We faced the same problema on our Odoo instance and I find out two solutions. 

  1. Run 'sudo dpkg-reconfigure tzdata' command and set server timezone to UTC. 
  2. Check the 'max_cron_thread' parameter in odoo.cfg and set it to value 2. max_cron_thread set as value 1, cause bug on cron stopping work.
  3. restart Odoo service
Imagine profil
Abandonează
Related Posts Răspunsuri Vizualizări Activitate
5
dec. 23
21115
1
iul. 25
2359
2
iul. 25
7854
2
iul. 25
4251
2
iul. 25
4016