I found the problem: Because I have a set up with test and production on Linux and development on Windows I am using environment variables to detect on which platform the code is running. and select a database connection accordingly (could be much much smarter) So on my test machine there are different variables if I start it from commandline or as a service and this caused that it could not find the database and stopped. No error message was generated so I could not see it. Now I have a better variables tests and everything works as it should.
On Friday, July 10, 2015 at 1:32:28 AM UTC+2, icodk wrote: > > I added >> /tmp/scheduler.out. All I got was: > > web2py Web Framework > Created by Massimo Di Pierro, Copyright 2007-2015 > Version 2.11.2-stable+timestamp.2015.05.30.16.33.24 > Database drivers available: psycopg2, pymysql, imaplib, pg8000, sqlite3, > sqlite2 > starting single-scheduler for "myapp"... > web2py Web Framework > Created by Massimo Di Pierro, Copyright 2007-2015 > Version 2.11.2-stable+timestamp.2015.05.30.16.33.24 > Database drivers available: psycopg2, pymysql, imaplib, pg8000, sqlite3, > sqlite2 > starting single-scheduler for "myapp"... > web2py Web Framework > Created by Massimo Di Pierro, Copyright 2007-2015 > Version 2.11.2-stable+timestamp.2015.05.30.16.33.24 > Database drivers available: psycopg2, pymysql, imaplib, pg8000, sqlite3, > sqlite2 > starting single-scheduler for "myapp"... > > > No extra information to explain why the restarts > > > > On Thursday, July 9, 2015 at 3:00:51 PM UTC+2, Massimo Di Pierro wrote: >> >> Does this work? >> https://github.com/web2py/web2py/blob/master/scripts/web2py-scheduler.conf >> Today we are discussing whether to keep it or remove it from web2py. >> Opinion? >> >> On Thursday, 9 July 2015 07:46:57 UTC-5, icodk wrote: >>> >>> Running the scheduler from command line with no problem: >>> python /home/user/web2py/web2py.py -K myapp -D 0 >>> Runs for ever and execute tasks >>> However if I run it as a demon according to the recipe in the book, it >>> actually restart the process 8 times and stops: >>> $ sudo status web2py-scheduler >>> web2py-scheduler stop/waiting >>> >>> I can see it with ps -ax, it gets new process id and after 8 process ids >>> it stops/give up. >>> In ps it looks like this: >>> 9027 ? Ss 0:00 sudo -u user python >>> /home/user/web2py/web2py.py -K myapp >>> 9029 ? S 0:00 python /home/user/web2py/web2py.py -K myapp >>> >>> Both process ids are changing >>> >>> I managed to log the commandline with -D 0 to the console but can't use >>> it for anything because it works fine >>> I also get a file: logs/web2py.log when I run the demon but it is empty. >>> >>> My logging.conf is: >>> >>> [logger_root] >>> level=DEBUG >>> handlers=consoleHandler,rotatingFileHandler >>> >>> [handler_rotatingFileHandler] >>> class=handlers.RotatingFileHandler >>> level=DEBUG >>> formatter=simpleFormatter >>> args=("logs/web2py.log", "a", 1000000, 5) >>> >>> >>> >>> -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
