"... but note that soft cron is not enabled by default in the standard wsgihandler.py file provided with web2py ..."
Maybe you could check the above (as I think that default cron method is soft in the server) if you haven't. Also, I belive that tasks are triggered after client requests if you are using soft cron, meaning that if there is no server activity your task could not run untill the server listens to a new request. On 3 mar, 14:52, Serpent_Guard <[email protected]> wrote: > I've been developing a web2py app under Mac OS X, which utilizes the > built-in cron. It's been working great. Yesterday I deployed my app to a > web2py install sitting on an EC2 instance running Ubuntu. Now, cron isn't > working anymore. I'm not an expert in cron syntax, so I wonder if there's > something I need to change now that it's running in a different OS. > > Note that I used the instructions > athttp://www.scribd.com/doc/26436821/Howto-deploy-Web2py-on-amazon-Ec2to > get web2py up and running. Thanks to whoever put that together, it worked > beautifully. > > Here's my crontab: > > #crontab > * * * * * root *mailer/send_messages > > That's how it looked under Mac OS X, when it was working. Like I said, I'm > no expert in cron syntax, so I'm not sure what the 'root' has to do with > the line, I couldn't find anything like it in any online cron tutorials. I > tried changing it to 'ubuntu', the default shell user for the instance, but > no dice. Any help would be appreciated. > > Note also that the send_messages function has the signature, > 'send_messages(noop="noop")', just so the function isn't exposed as a URL > If there are any better ways of doing this that'd be good to know as well. > Thanks!
