← Back to team overview

c2c-oerpscenario team mailing list archive

[Bug 493544] Re: Improper cronjobs?

 

** Changed in: openobject-server
       Status: New => Invalid

-- 
Improper cronjobs?
https://bugs.launchpad.net/bugs/493544
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in OpenObject Server: Invalid
Status in Power e-Mail for Open ERP: Incomplete

Bug description:
I have had continously problems with Poweremail module, which I presume are related to cronjob part of the Poweremail

Description of the problem:

1) All sent e-mail stay at outbox for forever after Powermail module installation. I note that there is a regular poweremail task to run a cron once every hour and all other regular tasks run, but no emails are ever sent out. 

2) If I log out from Openerp database and/or restart openerp-server afterwards, the OpenERP is not reachable anymore (the server is working, but does not give the list of databases to OpenERP client). The main technical reason is, that the OpenERP becomes stuck with too many idle (at least 30-50) postgresql connections, so the postgresql database pool becomes eventually exhausted. Moreover, restarting openerp-server or postgresql does not close down these idle connections (that can stay for hours and days).  

The only solution to revert back to working installation of OpenERP is 1) reboot the machine to clean up the postgresql mess as restarting postgresql service or killing postgresql process does not kill idle connections; 2) delete manually Poweremail related cronjob from ir.cron postgresql table before starting openerp-server; 3) start openerp-server (now OpenERP becomes reachable) and enter poweremail cronjob manually. 4) If one tries to connect OpenERP before deleting Poweremail related cronjob from ir.cron, then the postgresql database pool becomes again exhausted. 


The problem has been present in two different servers (one under Ubuntu and one under RedHat) and is not related with the way I have installed a Poweremail. The plain new installation under fresh OpenERP or updating existing Poweremail installation with new version or uninstalling old version and installing new version of Poweremail have all yielded into the same result -- leaking postgresql connections that can be dealt only by manually deleting the poweremail related line in ir.cron table.