-
-
Notifications
You must be signed in to change notification settings - Fork 460
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
[10.0]Could not acquire advisory lock #55
Comments
The interesting line is The WARNING line indicates that the job has been set on a channel The last 3 lines are normal operations of the jobrunner. Back to the advisory lock: First you may want to show the full traceback in your logs, because The exporter tries to acquires the advisory lock here: If it can't acquires it, it's probably because it has already been acquired by another transaction (but you may find another reason I guess). The purpose of this lock is to prevent 2 jobs to import the same record at the same time. The lock is set on a hash composed from attributes that define the uniqueness of a job (https://github.com/OCA/connector-odoo2odoo/pull/7/files#diff-490b3ec0560bd042a97411edb4d1e534R180). Are you sure the values you use here are unique? Also, check if you don't have a staled transaction in postgres which would have kept the lock. I don't see any issue in the queue, it's either in your setup, either in your implementation. I find it weird that the exception is logged by |
Thanks @guewen , I'll gonna give feedback on this |
Thanks @guewen you're right, a constraint was missing and I had duplicates in bindings ! |
Hi,
I'm running odoo connector and working on this PR : OCA/connector-odoo2odoo#7
My job working correctly except 2 jobs that are always restated as pending the started with this message :
In the logs I can see those kind of messages :
Any advice would be appreciated
The text was updated successfully, but these errors were encountered: