Re: [WebDNA] triggers.db "next execute" fails to update
This WebDNA talk-list message is from 2012
It keeps the original formatting.
numero = 108343
interpreted = N
texte = > 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
Associated Messages, from the most recent to the oldest:
> 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
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:
Summing fields (1997)
Another bug to squash (WebCat2b13 Mac .acgi) (1997)
gremlins? (2000)
dynamic giffing. (2000)
[OT] Mozilla | Was: R.I.P. Netscape (2003)
New commands in Final candidate (1997)
Search as error page (2002)
[WebDNA] Should I be able to use [setmimeheader name=Content-Type (2018)
[shownext] and descending order (1997)
Buying sans cart (1997)
Location of Webcat site in folder hierarchy (1997)
[WebDNA] How to code a 301 redirect (2008)
PLEASE REMOVE MY EMAIL ADDRESS (1997)
Sorting error (1997)
Extended [ConvertChars] (1997)
2.0Beta Command Ref (can't find this instruction) (1997)
Generating Report Totals (1997)
WebCatalog can't find database (1997)
Shopping Cart - prices? (1997)
Some shell fun (2004)