Re: [WebDNA] Trigger troubles

This WebDNA talk-list message is from

2014


It keeps the original formatting.
numero = 111519
interpreted = N
texte = Restarting WebDNA does reset the next execution. Perhaps look for: 1.) a corrupted triggers database 2.) logs, upon around the time the problem happens.. if you can catch = it. On Aug 6, 2014, at 5:57 AM, Tom Duke wrote: > Hi all, >=20 > I have a set of triggers that have been running well for over six = months. In the last week however they have started to fail. >=20 > I *think* that one of the triggers is causing a difficulty, and that = is then shutting down all the triggers (i.e. the next execution time is = not updating) and the only way to sort it out is a reboot of WebDNA. >=20 > Soooo ... do people have any suggestions about bulletproofing = triggers: >=20 > - what the best practice re: timeout and retry settings > - should I use spawn in trigger templates to prevent a rogue trigger = from bringing all triggers to a halt > - is there any way to test that triggers are active and script a = WebDNA reboot if they stop > - if I switch to cron can I add / edit the crontab using [shell] > - can cron hit protected templates >=20 > Thanks > - Tom >=20 > --------------------------------------------------------- This message = is sent to you because you are subscribed to the mailing list . To = unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us Bug Reporting: = support@webdna.us Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Trigger troubles (Donovan Brooke 2014)
  2. Re: [WebDNA] Trigger troubles (Dan Strong 2014)
  3. [WebDNA] Trigger troubles (Tom Duke 2014)
Restarting WebDNA does reset the next execution. Perhaps look for: 1.) a corrupted triggers database 2.) logs, upon around the time the problem happens.. if you can catch = it. On Aug 6, 2014, at 5:57 AM, Tom Duke wrote: > Hi all, >=20 > I have a set of triggers that have been running well for over six = months. In the last week however they have started to fail. >=20 > I *think* that one of the triggers is causing a difficulty, and that = is then shutting down all the triggers (i.e. the next execution time is = not updating) and the only way to sort it out is a reboot of WebDNA. >=20 > Soooo ... do people have any suggestions about bulletproofing = triggers: >=20 > - what the best practice re: timeout and retry settings > - should I use spawn in trigger templates to prevent a rogue trigger = from bringing all triggers to a halt > - is there any way to test that triggers are active and script a = WebDNA reboot if they stop > - if I switch to cron can I add / edit the crontab using [shell] > - can cron hit protected templates >=20 > Thanks > - Tom >=20 > --------------------------------------------------------- This message = is sent to you because you are subscribed to the mailing list . To = unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us Bug Reporting: = support@webdna.us Donovan Brooke

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

RE: WebDNA-Talk searchable? (1997) Alternating colors (1997) sorting dates (1999) M$loth messes with our sites (again) 2004/02/03 (2004) Possible Bug in 2.0b15.acgi (1997) Signal Raised (1997) WebCat2 several catalogs? (1997) can WC render sites out? (1997) Force a search at the default.tmpl page? (1997) Appending Information from one db to another (1998) NT lockup cont'd (1998) re:check boxes (1997) Problems getting parameters passed into email. (1997) Not really WebCat (1997) Running _every_ page through WebCat ? (1997) Press Release hit the NewsWire!!! (1997) WebCatalog 2.0 & WebDNA docs in HTML ... (1997) [protect admin] (1997) Country & Ship-to address & other fields ? (1997) Associative lookup style? + bit more (1997)