OpenERP 6.1 stops working after postgresql restart
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo Server (MOVED TO GITHUB) |
New
|
Undecided
|
OpenERP Publisher's Warranty Team |
Bug Description
That problem is rather critical for us, cause it affects production environment. That problem occurs time to time and may lead to serious delays in the work, cause OpenERP becomes unusable until somebody restarts it.
We're using OpenERP version 6.1-20121129-003502 on Ubuntu 12 server. PostgreSQL 9.1
Steps to reproduce are the following:
1) Login to some OpenERP database and logout
2) Now stop postgresql server (/etc/init.
3) Try to login to the same database
4) You got Error message - that is OK
5) Now start postgresql service (/etc/init.
6) Now try to log into same database again and see error message shown at the end of the ticket description
Only restart of OpenERP server helps
Expected behavior:
- OpenERP should automatically clear broken connections from pool and try to reconnect to DB Server
Additional problems:
- We're using 2 servers - one for OpenERP and second for PostgreSQL database. So it is not easy for us to write script that will restart OpenERP just after PostgreSQL restart. And obviously that problem need to be solved from OpenERP side.
-------
"/opt/expansaer
req.
File "/opt/expansaer
uid = self.proxy(
File "/opt/expansaer
result = self.connector.
File "/opt/expansaer
raise xmlrpclib.
Server Traceback (most recent call last):
File "/opt/expansaer
return openerp.
File "/opt/expansaer
result = ExportService.
File "/opt/expansaer
return fn(*params)
File "/opt/expansaer
return res_users.
File "/opt/expansaer
uid = self.login(db, login, password)
File "/opt/expansaer
cr = pooler.
File "/opt/expansaer
return Cursor(self._pool, self.dbname, serialized=
File "/opt/expansaer
self.
File "/opt/expansaer
return f(self, *args, **kwargs)
File "/opt/expansaer
self.
OperationalError: no connection to the server
Changed in openobject-server: | |
assignee: | nobody → OpenERP Publisher's Warranty Team (openerp-opw) |
tags: | added: maintenance |
Same here, the only workaround is to restart openerp by hand. But that might not always be possible, e.g. when there is an unattended upgrade of postgres at night.