1. Mailing Lists
  2. Contributors
  3. Re: Problem with scheduler

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: Problem with scheduler

Avatar

Re: Problem with scheduler

by Jay Vora <vora.jay@serpentcs.com> - 06/04/2017 14:45:14
Michael,

You may check the server logs.

Or, a possibility could be WSGI mode blocking your cron run. In that case you have to call cron frorm WSGI.

Like:

You need to add these lines to your wsgi-file in order to make cron jobs work

from openerp.service.server import ThreadedServer
 

and after the "openerp.service.server.load_server_wide_modules()"


ThreadedServer(None).cron_spawn()


On Thu, Apr 6, 2017 at 6:08 PM, Michael Delvoye <mdelvoye@misyl-services.com> wrote:
Hi everybody,
i have a very strange problem.
I need OCA contributors or an exorcism :-)  so as to find a solution of my problem.

I make tests with the scheduler.
I create an action that create an draft invoice then put it on open and at the end send me it by email.

When i execute the action by the button execute of the scheduler => Ok i reveive my invoice well format.

Now when I let the scheduler execute the action => I receive thepdf but no header and no css on footer........
Very strange.

Seriously, if someone has an idea, it would be nice.

Thanks 





--
Michael Delvoye
Directeur Technique
MISYL SERVICES

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe




--

The Splendid journey of 5 years in Numbers
---
Regards,
----------------------------------------------------------------------------------------------------------------------------
Jay Vora
Managing Director


 
Direct: +91-9879354457
Office: +91-9033472982
Skype: jaynvora
Twitter : jaynvora
   
-------------------------------------------------------------------------------------------------
Visit our website : http://www.serpentcs.com
Please consider the environment before printing this email

Reference