Re: [web2py] Re: Scheduler - a second try

2013-11-08 Thread Niphlod
the only thing is that only syslog-ng is multiprocess-safe, so the standard logging to file and/or console may incur in problems. On Friday, November 8, 2013 5:46:29 AM UTC+1, Jonathan Lundell wrote: > > On 7 Nov 2013, at 7:05 PM, Andrew W > > wrote: > > Thanks. I've never been quite sure what

Re: [web2py] Re: Scheduler - a second try

2013-11-08 Thread Johann Spies
Postgresql On 7 November 2013 15:16, Niphlod wrote: > what db are you using ? > > > On Thursday, November 7, 2013 12:07:40 PM UTC+1, Johann Spies wrote: >> >> It was a year ago that I have tried for 4 days to get the scheduler >> working. In the end I gave up and decided to use the operating s

Re: [web2py] Re: Scheduler - a second try

2013-11-07 Thread Jonathan Lundell
On 7 Nov 2013, at 9:00 PM, Andrew W wrote: > Well, I just added -D 0 when starting the scheduler and it prints to the > console. > Yes, we should add something, because after reading the logging sections of > the book I was sure I had to add something to the conf file. scheduler.py has this:

Re: [web2py] Re: Scheduler - a second try

2013-11-07 Thread Andrew W
Well, I just added -D 0 when starting the scheduler and it prints to the console. Yes, we should add something, because after reading the logging sections of the book I was sure I had to add something to the conf file. On Friday, November 8, 2013 3:46:29 PM UTC+11, Jonathan Lundell wrote: >

Re: [web2py] Re: Scheduler - a second try

2013-11-07 Thread Jonathan Lundell
On 7 Nov 2013, at 7:05 PM, Andrew W wrote: > Thanks. I've never been quite sure what to put in logging.conf for the > scheduler debug key, based on the "logger =" statement in scheduler.py. We should add a schedule section to the logging example file. -- Resources: - http://web2py.com - htt

[web2py] Re: Scheduler - a second try

2013-11-07 Thread Andrew W
Thanks. I've never been quite sure what to put in logging.conf for the scheduler debug key, based on the "logger =" statement in scheduler.py. On Friday, November 8, 2013 6:59:17 AM UTC+11, Niphlod wrote: > logging is enabled as anything else in web2py. > just start the scheduler with > w

[web2py] Re: Scheduler - a second try

2013-11-07 Thread Niphlod
logging is enabled as anything else in web2py. just start the scheduler with web2py.py -K appname -D 0 to enable the DEBUG level. Of course logging.conf must be configured to allow DEBUG messages to be printed in the console. BTW: *Error cleaning up* shows up usually when the scheduler can't act

[web2py] Re: Scheduler - a second try

2013-11-07 Thread Andrew W
herbou1 is a function in my isi-controller. Shouldn't this function be in your models? A question for you: how did you turn on debugging for the scheduler? -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://cod

[web2py] Re: Scheduler - a second try

2013-11-07 Thread Niphlod
what db are you using ? On Thursday, November 7, 2013 12:07:40 PM UTC+1, Johann Spies wrote: > > It was a year ago that I have tried for 4 days to get the scheduler > working. In the end I gave up and decided to use the operating systems's > cron to handle scheduled jobs. > > I am trying again