Re: [WebDNA] Trigger stops executing

This WebDNA talk-list message is from

2017

It keeps the original formatting. numero = 113648
interpreted = N
texte = 1243Here's a scenario I resolved for a new client who couldn'tunderstand why his daily alerts had stopped being sent to him:The server's date/time values were current and correct for a verylong time. Then something (or someone, a hacker perhaps?) changedthe server's date/time to 3 weeks in the future.WebDNA compared this new server date/time to the NextExecutevalues in the triggers.db noticed that all those NextExecutevalues were "in the past" so it immediately ran all those triggers.... and reset all those NextExecute values to a new date/time 3weeks into the future.Then the server admin discovered the problem and reset theserver's date and time properly. But the damage had already beendone ... meaning that all the NextExecute dates in the triggers.dbhad already been set for 3 weeks in the future, so none of thosetriggers would run again for 3 weeks.Is this what has happened to your failed trigger?BTW, sometimes it "makes sense" to put a sendmail context intoyour trigger pages so WebDNA can send you an email every time itruns (or just append the trigger hits to a log file if you don'twant all those emails). Then when the trigger requests your pagebut your WebDNA code doesn't do what you expect, at least you'llhave some solid evidence that the trigger still ran correctly.You should also reboot the server and see if that clears anyglitch that may have caused the triggers to stop working. This isnormally the first thing I recommend when a new and unexplainedproblem comes up.If a reboot doesn't clear the problem, another potential issuemight be corruption of the triggers.db.Regards,Kenneth GromeWebDNA Solutionshttp://www.webdnasolutions.comWeb Database Systems and Linux Server Administration> I have a trigger set through the admin triggers screen with > timeout value of 30 seconds to execute the process orders > script. This was working until a few days ago but no longer > does (the orders are not getting processed) - though the > timestamp keeps updating as though it had executed. If I copy > paste the URL designated in the trigger into a browser then> the process orders script executes as expected (the orders > process). What might cause the trigger to no longer work in > this way?---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list talk@webdna.usTo unsubscribe, E-mail to: talk-leave@webdna.usarchives: http://www.webdna.us/page.dna?numero=55Bug Reporting: support@webdna.us. Associated Messages, from the most recent to the oldest:

Re: [WebDNA] Trigger stops executing (Donovan Brooke 2017)
Re: [WebDNA] Trigger stops executing (Donovan Brooke 2017)
Re: [WebDNA] Trigger stops executing (Kenneth Grome 2017)
[WebDNA] Trigger stops executing ("mainlighting ." 2017)

1243Here's a scenario I resolved for a new client who couldn'tunderstand why his daily alerts had stopped being sent to him:The server's date/time values were current and correct for a verylong time. Then something (or someone, a hacker perhaps?) changedthe server's date/time to 3 weeks in the future.WebDNA compared this new server date/time to the NextExecutevalues in the triggers.db noticed that all those NextExecutevalues were "in the past" so it immediately ran all those triggers.... and reset all those NextExecute values to a new date/time 3weeks into the future.Then the server admin discovered the problem and reset theserver's date and time properly. But the damage had already beendone ... meaning that all the NextExecute dates in the triggers.dbhad already been set for 3 weeks in the future, so none of thosetriggers would run again for 3 weeks.Is this what has happened to your failed trigger?BTW, sometimes it "makes sense" to put a sendmail context intoyour trigger pages so WebDNA can send you an email every time itruns (or just append the trigger hits to a log file if you don'twant all those emails). Then when the trigger requests your pagebut your WebDNA code doesn't do what you expect, at least you'llhave some solid evidence that the trigger still ran correctly.You should also reboot the server and see if that clears anyglitch that may have caused the triggers to stop working. This isnormally the first thing I recommend when a new and unexplainedproblem comes up.If a reboot doesn't clear the problem, another potential issuemight be corruption of the triggers.db.Regards,Kenneth GromeWebDNA Solutionshttp://www.webdnasolutions.comWeb Database Systems and Linux Server Administration> I have a trigger set through the admin triggers screen with > timeout value of 30 seconds to execute the process orders > script. This was working until a few days ago but no longer > does (the orders are not getting processed) - though the > timestamp keeps updating as though it had executed. If I copy > paste the URL designated in the trigger into a browser then> the process orders script executes as expected (the orders > process). What might cause the trigger to no longer work in > this way?---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list talk@webdna.usTo unsubscribe, E-mail to: talk-leave@webdna.usarchives: http://www.webdna.us/page.dna?numero=55Bug Reporting: support@webdna.us. Kenneth Grome

DOWNLOAD WEBDNA NOW!

Re: [WebDNA] Trigger stops executing

2017

Top Articles:

Related Readings: