Re: [WebDNA] triggers.db "next execute" fails to update

This WebDNA talk-list message is from

2012


It keeps the original formatting.
numero = 108338
interpreted = N
texte = --20cf3036387d902d6104b7a926eb Content-Type: text/plain; charset=ISO-8859-1 Can you stop webdna and find the db file to fix while not running? On Sunday, January 29, 2012, Kenneth Grome wrote: > I created a trigger on WebDNA 6.x via WebDNA Sandbox Admin. > This is the only trigger used in this sandbox. > > When it runs WebDNA fails update the "next execute" value > like it is supposed to. Therefore the trigger runs again > every 10 seconds, and the same template is interpreted by > WebDNA again ... > > This is a "bad thing" when the template has a sendmail > context it it to alert me that the trigger has run, because > it sends me another email every 10 seconds. I got more than > 1500 emails this morning before the host put an end to it by > rebooting the server ... :( > > Flushing the databases does not stop the trigger from > running. Deleting the target template via FTP does not stop > it, because even though the file is no longer on disk it is > apparently still cached in RAM. Strangely enough, the > template seems to remain cached in RAM , thus ignoring the > WebCatalog Prefs that's supposed to force the template out > of ram every 2 seconds. Issuing a FlushCache command also > fails to purge the template from RAM. > > :( > > My host refuses to investigate this issue. Whether he is > lazy, irresponsible, incompetent, or all of the above, > cannot say for certain. Nevertheless I need the problem > fixed, so I'll have to figure this out myself, hopefully with > some bright ideas from others here. > > Any idea why WebDNA might fail to update the "next execute" > value when the trigger is run? > > Sincerely, > Kenneth Grome > --------------------------------------------------------- > 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 > --20cf3036387d902d6104b7a926eb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Can you stop webdna and find the db file to fix while not running?

O= n Sunday, January 29, 2012, Kenneth Grome <kengrome@gmail.com> wrote:
> I created a trigger on W= ebDNA 6.x via WebDNA Sandbox Admin.
> This is the only trigger used in this sandbox.
>
> When it= runs WebDNA fails update the "next execute" value
> like i= t is supposed to. =A0Therefore the trigger runs again
> every 10 seco= nds, and the same template is interpreted by
> WebDNA again ...
>
> This is a "bad thing" when = the template has a sendmail
> context it it to alert me that the trig= ger has run, because
> it sends me another email every 10 seconds. = =A0I got more than
> 1500 emails this morning before the host put an end to it by
> r= ebooting the server ... :(
>
> Flushing the databases does not = stop the trigger from
> running. =A0Deleting the target template via = FTP does not stop
> it, because even though the file is no longer on disk it is
> ap= parently still cached in RAM. =A0Strangely enough, the
> template see= ms to remain cached in RAM , thus ignoring the
> WebCatalog Prefs tha= t's supposed to force the template out
> of ram every 2 seconds. =A0Issuing a FlushCache command also
> f= ails to purge the template from RAM.
>
> :(
>
> My = host refuses to investigate this issue. =A0Whether he is
> lazy, irre= sponsible, incompetent, or all of the above,
> cannot say for certain. =A0Nevertheless I need the problem
> fix= ed, so I'll have to figure this out myself, hopefully with
> some= bright ideas from others here.
>
> Any idea why WebDNA might f= ail to update the "next execute"
> value when the trigger is run?
>
> Sincerely,
> Kenn= eth Grome
> ---------------------------------------------------------=
> This message is sent to you because you are subscribed to
> = the mailing list <talk@webdna.us&g= t;.
> To unsubscribe, E-mail to: <talk-leave@webdna.us>
> archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us<= /a>
> --20cf3036387d902d6104b7a926eb-- Associated Messages, from the most recent to the oldest:

    
  1. Re: [BULK] Re: [WebDNA] triggers.db "next execute" fails to update (Kenneth Grome 2012)
  2. Re: [BULK] Re: [WebDNA] triggers.db "next execute" fails to update ("Psi Prime Inc, Matthew A Perosi " 2012)
  3. Re: [BULK] Re: [WebDNA] triggers.db "next execute" fails to update (Kenneth Grome 2012)
  4. Re: [BULK] Re: [WebDNA] triggers.db "next execute" fails to update ("Psi Prime Inc, Matthew A Perosi " 2012)
  5. [BULK] Re: [WebDNA] triggers.db "next execute" fails to update (Kenneth Grome 2012)
  6. Re: [WebDNA] triggers.db "next execute" fails to update (Stuart Tremain 2012)
  7. Re: [WebDNA] triggers.db "next execute" fails to update (Kenneth Grome 2012)
  8. [BULK] Re: [WebDNA] triggers.db "next execute" fails to update (Donovan Brooke 2012)
  9. Re: [WebDNA] triggers.db "next execute" fails to update (sal danna 2012)
  10. Re: [WebDNA] triggers.db "next execute" fails to update (Kenneth Grome 2012)
  11. Re: [WebDNA] triggers.db "next execute" fails to update (Rob 2012)
  12. Re: [WebDNA] triggers.db "next execute" fails to update (Govinda 2012)
  13. Re: [WebDNA] triggers.db "next execute" fails to update (William DeVaul 2012)
  14. [WebDNA] triggers.db "next execute" fails to update (Kenneth Grome 2012)
--20cf3036387d902d6104b7a926eb Content-Type: text/plain; charset=ISO-8859-1 Can you stop webdna and find the db file to fix while not running? On Sunday, January 29, 2012, Kenneth Grome wrote: > I created a trigger on WebDNA 6.x via WebDNA Sandbox Admin. > This is the only trigger used in this sandbox. > > When it runs WebDNA fails update the "next execute" value > like it is supposed to. Therefore the trigger runs again > every 10 seconds, and the same template is interpreted by > WebDNA again ... > > This is a "bad thing" when the template has a sendmail > context it it to alert me that the trigger has run, because > it sends me another email every 10 seconds. I got more than > 1500 emails this morning before the host put an end to it by > rebooting the server ... :( > > Flushing the databases does not stop the trigger from > running. Deleting the target template via FTP does not stop > it, because even though the file is no longer on disk it is > apparently still cached in RAM. Strangely enough, the > template seems to remain cached in RAM , thus ignoring the > WebCatalog Prefs that's supposed to force the template out > of ram every 2 seconds. Issuing a FlushCache command also > fails to purge the template from RAM. > > :( > > My host refuses to investigate this issue. Whether he is > lazy, irresponsible, incompetent, or all of the above, > cannot say for certain. Nevertheless I need the problem > fixed, so I'll have to figure this out myself, hopefully with > some bright ideas from others here. > > Any idea why WebDNA might fail to update the "next execute" > value when the trigger is run? > > Sincerely, > Kenneth Grome > --------------------------------------------------------- > 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 > --20cf3036387d902d6104b7a926eb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Can you stop webdna and find the db file to fix while not running?

O= n Sunday, January 29, 2012, Kenneth Grome <kengrome@gmail.com> wrote:
> I created a trigger on W= ebDNA 6.x via WebDNA Sandbox Admin.
> This is the only trigger used in this sandbox.
>
> When it= runs WebDNA fails update the "next execute" value
> like i= t is supposed to. =A0Therefore the trigger runs again
> every 10 seco= nds, and the same template is interpreted by
> WebDNA again ...
>
> This is a "bad thing" when = the template has a sendmail
> context it it to alert me that the trig= ger has run, because
> it sends me another email every 10 seconds. = =A0I got more than
> 1500 emails this morning before the host put an end to it by
> r= ebooting the server ... :(
>
> Flushing the databases does not = stop the trigger from
> running. =A0Deleting the target template via = FTP does not stop
> it, because even though the file is no longer on disk it is
> ap= parently still cached in RAM. =A0Strangely enough, the
> template see= ms to remain cached in RAM , thus ignoring the
> WebCatalog Prefs tha= t's supposed to force the template out
> of ram every 2 seconds. =A0Issuing a FlushCache command also
> f= ails to purge the template from RAM.
>
> :(
>
> My = host refuses to investigate this issue. =A0Whether he is
> lazy, irre= sponsible, incompetent, or all of the above,
> cannot say for certain. =A0Nevertheless I need the problem
> fix= ed, so I'll have to figure this out myself, hopefully with
> some= bright ideas from others here.
>
> Any idea why WebDNA might f= ail to update the "next execute"
> value when the trigger is run?
>
> Sincerely,
> Kenn= eth Grome
> ---------------------------------------------------------=
> This message is sent to you because you are subscribed to
> = the mailing list <talk@webdna.us&g= t;.
> To unsubscribe, E-mail to: <talk-leave@webdna.us>
> archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us<= /a>
> --20cf3036387d902d6104b7a926eb-- William DeVaul

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:

Not really WebCat (1997) Speed Optimization - Mac (1997) Checkbox question (1997) WebCatalog2 Feature Feedback (1996) Emailer tracking (1997) RE:ShowIf & HideIf Question? (1998) Download URL & access on the fly ? (1997) [WebDNA] mod_deflate and webdna (2017) RAM variables (1997) Searching (2004) Ok, I'm stumped (1998) WCS Newbie question (1997) OSX Install error (2000) Document Contains No Data! (1997) international time (1997) 2 questions (2000) encrypt/decrypt failing (2000) WebCat/CyberStudio Compatibility (1998) WC 2.0 frames feature (1997) Webcat Installation Problem? (2000)