Community mailing list archives

Re: Experiences with unusual -u MODULE behaviours?

David Arnold
- 08/03/2014 01:36:32
This is one, which for once shows me an error message.. I understand that this probably has to do with DB connections. If so, -u should probably deal with that, too?

2014-08-03 05:33:37,202 9167 ERROR ? openerp.addons.bus.bus: Bus.loop error, sleep and retry
Traceback (most recent call last):
  File "/vagrant/odoo/addons/bus/", line 136, in run
  File "/vagrant/odoo/addons/bus/", line 114, in loop
    with openerp.sql_db.db_connect('postgres').cursor() as cr:
  File "/vagrant/odoo/openerp/", line 565, in cursor
    return Cursor(self.__pool, self.dbname, serialized=serialized)
  File "/vagrant/odoo/openerp/", line 176, in __init__
    self._cnx = pool.borrow(dsn(dbname))
  File "/vagrant/odoo/openerp/", line 458, in _locked
    return fun(self, *args, **kwargs)
  File "/vagrant/odoo/openerp/", line 521, in borrow
    result = psycopg2.connect(dsn=dsn, connection_factory=PsycoConnection)
  File "/usr/lib/python2.7/dist-packages/psycopg2/", line 179, in connect
    connection_factory=connection_factory, async=async)
OperationalError: FATAL:  remaining connection slots are reserved for non-replication superuser connections

El Alemán S.A.S

David Arnold BA HSG / Gerente
315 304 13 68/ david²

El Alemán S.A.S Office: +57 (1) 651 3766 / Fax: +57 (1) 651 3772 
CRA 13 93 40 P4, Bogotá, Colombia


This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. El Aleman S.A.S is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.

2014-08-03 0:02 GMT-05:00 <>:
Hi Developers

I just wanted to ask, if you also sometimes experience very weird behavious in your development workflow. I think -u is supposed to ceep your database consistend with the changes you make in the code?

Wired things I could observe, even after the usual mitigation procedures:
(Cache clearing, odoo restart, db restart)

- Blank page and hanging on a 200 HTTP operation
- eternal loop on module loading

These are very difficult to hunt down, that's probably why they are usually just quietely accepted as being "too complex to solve". (I'm thinkin loud)

So I thought a first step would be probably sharing such issues and trying to establish some common patterns out of a collection, because I think this is one of the trickier part of Anthony Lesuisse's developer friendliness...

If no one has a better idea, I would propose sharing here all those kind of behaviours, that persist

- " -u MODULE"-restart
- cache clearing

- db restart
- server restart
- db dump and trying on a fresh db (th point beeing that -u should do this persistance job on the db, right?)

Thanks for you opinion, objections, contributions, etc. I'm not even sure, if this is a good idea, but when thinking of "developer friendliness", this is an issue.

Regards, David

Post to: