Re: [WebDNA] triggers.db "next execute" fails to update
This WebDNA talk-list message is from 2012
It keeps the original formatting.
numero = 108347
interpreted = N
texte = Thanks Sal, I already have a work-around in mind but I will keep this one in my files in case I need it. Sincerely, Kenneth Grome > I found this old work around posted in the archives using > cron+wget . Not a fix, but might be a work around for > the moment. > > http://dev.webdna.us/TalkListArchive/DetailResults.tpl?co > mmand=search&db=webdna-talk.db&eqIDdata=28195 > > Sal > > On Jan 29, 2012 7:39 AM, "Kenneth Grome"
wrote: > > > Can you stop webdna and find the db file to fix while > > > not running? > > > > I cannot do anything of consequence on the server. I > > cannot stop it, I cannot download the Triggers.db, and > > of course I cannot open the Triggers.db in a text > > editor to confirm whether or not it is formatted > > properly. > > > > But I do not suspect a problem with the db file > > anyways. Instead I suspect WebDNA itself because there > > have been other problems on this server lately which > > required a reboot to eliminate. For example: > > > > I have two different scripts that generate email files > > on the server. Both work properly by creating only > > one file per recipient and placing it into the > > EmailFolder. But some of these emails are sent > > multiple time ... > > > > The host "thinks" that WebDNA is creating multiple > > emails (from each individual email file) in its > > Emailer Queue and then sending those multiple emails > > to the mail server for delivery. The reason he > > believes this is because the mail server is on a > > different box, yet after he rebooted the WebDNA server > > the duplicate email problem went away. > > > > --------------------------- > > > > Has anyone ever had the "next execute" field fail to > > update when the trigger is run? > > > > I suggested to the host that perhaps he gave the > > Triggers.db the wrong permissions when he created the > > sandbox. My thought was that even though I can edit > > the Triggers.db via WebDNA Admin, perhaps somehow the > > WebDNA software itself cannot edit the db because it > > doesn't have enough permission. > > > > The host sent me this in response to my suggestion: > > > Here are the permission levels on the triggers.db > > > file in their sandbox. > > > > > > -rw-rw-r-- 1 apache apache 233 Jan 28 > > > 06:40 Triggers.db > > > > Is this the correct permissions on the Triggers.db > > file? > > > > I really do not think it is possible for WebDNA Admin > > to be able to edit a db while the WebDNA software > > itself cannot, because they are "one an the same" > > aren't they? > > > > Other than this possibility I'm at a loss as to what > > might cause the Triggers.db to fail to update after > > the trigger is run ... except in the case of a bug of > > course, or possibly a corrupted database. > > > > But after I deleted all triggers then recreated a new > > one the problem persisted, which makes me think it is > > not a corrupt db. So this brings me back to the > > thought that the WebDNA software may be corrupted. > > > > All other thoughts welcome. > > > > 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
Associated Messages, from the most recent to the oldest:
Thanks Sal, I already have a work-around in mind but I will keep this one in my files in case I need it. Sincerely, Kenneth Grome > I found this old work around posted in the archives using > cron+wget . Not a fix, but might be a work around for > the moment. > > http://dev.webdna.us/TalkListArchive/DetailResults.tpl?co > mmand=search&db=webdna-talk.db&eqIDdata=28195 > > Sal > > On Jan 29, 2012 7:39 AM, "Kenneth Grome" wrote: > > > Can you stop webdna and find the db file to fix while > > > not running? > > > > I cannot do anything of consequence on the server. I > > cannot stop it, I cannot download the triggers.db, and > > of course I cannot open the triggers.db in a text > > editor to confirm whether or not it is formatted > > properly. > > > > But I do not suspect a problem with the db file > > anyways. Instead I suspect WebDNA itself because there > > have been other problems on this server lately which > > required a reboot to eliminate. For example: > > > > I have two different scripts that generate email files > > on the server. Both work properly by creating only > > one file per recipient and placing it into the > > EmailFolder. But some of these emails are sent > > multiple time ... > > > > The host "thinks" that WebDNA is creating multiple > > emails (from each individual email file) in its > > Emailer Queue and then sending those multiple emails > > to the mail server for delivery. The reason he > > believes this is because the mail server is on a > > different box, yet after he rebooted the WebDNA server > > the duplicate email problem went away. > > > > --------------------------- > > > > Has anyone ever had the "next execute" field fail to > > update when the trigger is run? > > > > I suggested to the host that perhaps he gave the > > triggers.db the wrong permissions when he created the > > sandbox. My thought was that even though I can edit > > the triggers.db via WebDNA Admin, perhaps somehow the > > WebDNA software itself cannot edit the db because it > > doesn't have enough permission. > > > > The host sent me this in response to my suggestion: > > > Here are the permission levels on the triggers.db > > > file in their sandbox. > > > > > > -rw-rw-r-- 1 apache apache 233 Jan 28 > > > 06:40 triggers.db > > > > Is this the correct permissions on the triggers.db > > file? > > > > I really do not think it is possible for WebDNA Admin > > to be able to edit a db while the WebDNA software > > itself cannot, because they are "one an the same" > > aren't they? > > > > Other than this possibility I'm at a loss as to what > > might cause the triggers.db to fail to update after > > the trigger is run ... except in the case of a bug of > > course, or possibly a corrupted database. > > > > But after I deleted all triggers then recreated a new > > one the problem persisted, which makes me think it is > > not a corrupt db. So this brings me back to the > > thought that the WebDNA software may be corrupted. > > > > All other thoughts welcome. > > > > 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
Kenneth Grome
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:
WebCat2 - storing unformatted date data? (1997)
WebDNA 4.5.1 Now Available (2003)
PIXO support (1997)
Date Time Oddness (1999)
Ampersand (1997)
Replace and Date (2002)
Help! WebCat2 bug (1997)
Comments in db? (1997)
international time (1997)
Sort of a Dilemma! (1998)
Multiple fields on 1 input (1997)
[isfile] ? (1997)
totals (1997)
Duplicate Hell (1999)
WC2b15 File Corruption (1997)
Searching multiple fields from one form field (1997)
WebDNA color code chart - oops (2002)
For those of you not on the WebCatalog Beta... (1997)
restarting service remotely on NT (1997)
WCS Newbie question (1997)