This question has been flagged
2 Replies
4843 Views

I get this log many times in all odoo versions. is it postgres boundry or odoo code issue. I get this issue in default odoo also.

Please Help if any one have idea.

File "/opt/odoo-9.0/Internal-Odoo/openerp/api.py", line 250, in wrapper return old_api(self, *args, **kwargs) File "/opt/odoo-9.0/Internal-Odoo/openerp/addons/base/ir/ir_qweb.py", line 254, in render return self.render_node(element, qwebcontext, generated_attributes=qwebcontext.pop('generated_attributes', '')) File "/opt/odoo-9.0/Internal-Odoo/openerp/addons/base/ir/ir_qweb.py", line 297, in render_node result = self.render_element(element, template_attributes, generated_attributes, qwebcontext) File "/opt/odoo-9.0/Internal-Odoo/openerp/addons/base/ir/ir_qweb.py", line 320, in render_element generated_attributes= name == "t" and generated_attributes or '')) File "/opt/odoo-9.0/Internal-Odoo/openerp/addons/base/ir/ir_qweb.py", line 295, in render_node result = self._render_tag[t_render](self, element, template_attributes, generated_attributes, qwebcontext) File "/opt/odoo-9.0/Internal-Odoo/openerp/addons/base/ir/ir_qweb.py", line 448, in render_tag_call d[0] = self.render_element(element, template_attributes, generated_attributes, d) File "/opt/odoo-9.0/Internal-Odoo/openerp/addons/base/ir/ir_qweb.py", line 320, in render_element generated_attributes= name == "t" and generated_attributes or '')) File "/opt/odoo-9.0/Internal-Odoo/openerp/addons/base/ir/ir_qweb.py", line 295, in render_node result = self._render_tag[t_render](self, element, template_attributes, generated_attributes, qwebcontext) File "/opt/odoo-9.0/Internal-Odoo/openerp/addons/base/ir/ir_qweb.py", line 489, in render_tag_set qwebcontext[template_attributes["set"]] = self.render_element(element, template_attributes, generated_attributes, qwebcontext) File "/opt/odoo-9.0/Internal-Odoo/openerp/addons/base/ir/ir_qweb.py", line 325, in render_element raise_qweb_exception(message="Could not render element %r" % element.tag, node=element, template=template) File "/opt/odoo-9.0/Internal-Odoo/openerp/addons/base/ir/ir_qweb.py", line 320, in render_element generated_attributes= name == "t" and generated_attributes or '')) File "/opt/odoo-9.0/Internal-Odoo/openerp/addons/base/ir/ir_qweb.py", line 295, in render_node result = self._render_tag[t_render](self, element, template_attributes, generated_attributes, qwebcontext) File "/opt/odoo-9.0/Internal-Odoo/openerp/addons/base/ir/ir_qweb.py", line 481, in render_tag_call_assets return bundle.to_html(css=css, js=js, debug=bool(qwebcontext.get('debug')), async=async, qwebcontext=qwebcontext) File "/opt/odoo-9.0/Internal-Odoo/openerp/addons/base/ir/ir_qweb.py", line 1195, in to_html css_attachments = self.css() File "/opt/odoo-9.0/Internal-Odoo/openerp/addons/base/ir/ir_qweb.py", line 1326, in css self.save_attachment("css", ' '.join(page), inc=idx) File "/opt/odoo-9.0/Internal-Odoo/openerp/addons/base/ir/ir_qweb.py", line 1285, in save_attachment self.clean_attachments(type) File "/opt/odoo-9.0/Internal-Odoo/openerp/addons/base/ir/ir_qweb.py", line 1252, in clean_attachments return ira.unlink(self.cr, openerp.SUPERUSER_ID, attachment_ids, context=self.context) File "/opt/odoo-9.0/Internal-Odoo/openerp/api.py", line 250, in wrapper return old_api(self, *args, **kwargs) File "/opt/odoo-9.0/Internal-Odoo/openerp/addons/base/ir/ir_attachment.py", line 416, in unlink res = super(ir_attachment, self).unlink(cr, uid, ids, context) File "/opt/odoo-9.0/Internal-Odoo/openerp/api.py", line 250, in wrapper return old_api(self, *args, **kwargs) File "/opt/odoo-9.0/Internal-Odoo/openerp/models.py", line 3677, in unlink 'where id IN %s', (sub_ids,)) File "/opt/odoo-9.0/Internal-Odoo/openerp/sql_db.py", line 141, in wrapper return f(self, *args, **kwargs) File "/opt/odoo-9.0/Internal-Odoo/openerp/sql_db.py", line 220, in execute res = self._obj.execute(query, params)QWebException: could not serialize access due to concurrent update

Avatar
Discard

We are facing same issue in odoo 9. please let me know the solutions above issue

Best Answer

Hello,

usually this happens when a database table is locked since another query is done on it, by a cron job, a job of the job queue,... or by a bad query that locked the table ans since it is bad it failed but the lock still there.

So things to try:

- check whether there is another error happening before this concurrent update, and solve it, this will solve the concurrent update.

- check if there are jobs too long, so that the next iteration is starting before that the current iteration finishes, if so then check why it is long, if normal then give more time between iterations.

Avatar
Discard