Hi, I'm back again. You may recall that I had a scheduled task that was firing 5 times for undiscovered causes? I decided to go with the cron job solution (which I scheduled at a new time) - and have REMOVED ALL scheduled tasks from the OpenBD admin.
Well, it's trigger time again, and the ghost task has fired 5 times again - at the ORIGINAL CF task time (not the new CRON job time). System details are already in this thread. So I am back to my original question: After the XML file, where do I look next? Should I grep my entire system for remnants of the task path somewhere? Al On Friday, August 10, 2012 11:36:53 AM UTC-7, Al Holden wrote: > > I need to track down the reason why a single scheduled task appears to be > firing 5 times in succession (a number which seems to increase each time I > attempt to remove and re-create the task). > > This is OpenBD 2,0,2 (built 2012-01-01 10:14:17 GMT) WAR deployment - > Apache Tomcat/6.0.24 on Linux i386 (2.6.32-38-generic-pae) > > First, what file contains the settings one makes within Matt's totally > awesome Administrator app? I would look for multiple entries here to start > my audit. > > Next, by what mechanism does a scheduled task rise up from its slumber and > actually invoke the URL call itself? For example, can I look for a record > of a cron job actually created in Linux somewhere? > > I fear these questions might cause a flurry of "Don't even use THAT... I > use THIS instead" responses, which I totally encourage. But an actual > answer would be nice too, because I'd really like to know! > > Al > > P.S. Yes, the job is based on a query, and yes: the query only contains > one record (the job emails it to me). > -- online documentation: http://openbd.org/manual/ http://groups.google.com/group/openbd?hl=en
