Are you starting a lot of cron tasks that do not terminate before the next one starts? I suggest you use a background process and do not use cron. To my knowledge there is no bug but cron become unpredictable if jobs take too long.
Massimo On Jul 5, 10:34 am, John Duddy <jdu...@gmail.com> wrote: > I'm getting the following stack trace in my console after leaving my > app running overnight. We use cron for several tasks. > > I saw the below thread, which indicated that the issue has been > resolved: > > http://groups.google.com/group/web2py/browse_thread/thread/e788b0783e... > > Has there been a regression? > > Here's the stack trace. Thanks! > > Traceback (most recent call last): > File "/usr/local/lib/python2.7/threading.py", line 552, in > __bootstrap_inner > self.run() > File "/root/web2py/gluon/newcron.py", line 63, in run > s.run() > File "/usr/local/lib/python2.7/sched.py", line 117, in run > File "/root/web2py/gluon/newcron.py", line 55, in launch > crondance(self.path, 'hard', startup = False) > File "/root/web2py/gluon/newcron.py", line 234, in crondance > cronmaster = token.acquire(startup=startup) > File "/root/web2py/gluon/newcron.py", line 101, in acquire > self.master = open(self.path,'rb+') > IOError: [Errno 24] Too many open files: '/root/web2py/applications/ > admin/cron/cron.master'
