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 on its own tables. I've seen that happen with SQLite without WAL and multiple workers, because of the well known problems related to SQLite concurrency, but never on a "production-ready" backend. That's why I asked for what db is used in that app. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
