Re: [WebDNA] Triggers.db wiped completely blank
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 107857
interpreted = N
texte = Hi Chris, Although this is good news for WebDNA it is not good news for my use of WebDNA on the VPS I have it installed on. Do you have any clue why my Triggers.db file would be wiped clean like it was for no apparent reason? Sincerely, Kenneth Grome > Hi Ken! just tested the worst possible situation with the > triggers: > > - WebDNA commits databases to disk only when instructed > - added two triggers > - kill -9 webdna.fcgi > - new call to webdna (to wake it up again) > - check that the PID is a new one (confirm that WebDNA > has been closed and restarted) - check the triggers: > they are still there > > - chris > > On Dec 30, 2011, at 12:07, Kenneth Grome wrote: > > I just learned that something completely wiped out my > > Triggers.db 7 days ago -- it is completely blank -- and > > I have no idea what might have caused this. > > > > Does anyone else have a clue why this might happen? > > > > Along with other things I was using it to bill clients > > automatically. But the bills never went out last week, > > which explains why I never got paid this week. > > > > I'm going to recreate my triggers, and I'm adding a new > > trigger -- one that will send me an email every day to > > confirm that triggers are still working. Then I will > > know when this happens again from the lack of a daily > > email, rather than learning about it a week later. > > But this does not make me feel any more confident > > about trusting triggers, and that's why I am hoping > > for an explanation of how this could have happened in > > the first place. > > > > I have not made any config changes on the server in > > months, nor has anyone else -- except possibly the > > hosting company -- and I do not understand how the > > hosting company's potential changes might have wiped > > out my Triggers.db while leaving all the other db's > > intact and functioning properly. > > > > The only thing I can think of is that maybe the > > flushdatabases tag does NOT flush the Triggers.db to > > disk, so the Triggers.db always remains volatile in > > RAM ... and therefore it is subject to being wiped out > > when the server crashes or the VPS is moved to a > > different computer. > > > > ??? > > > > 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 > > --------------------------------------------------------- > 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:
Hi Chris, Although this is good news for WebDNA it is not good news for my use of WebDNA on the VPS I have it installed on. Do you have any clue why my triggers.db file would be wiped clean like it was for no apparent reason? Sincerely, Kenneth Grome > Hi Ken! just tested the worst possible situation with the > triggers: > > - WebDNA commits databases to disk only when instructed > - added two triggers > - kill -9 webdna.fcgi > - new call to webdna (to wake it up again) > - check that the PID is a new one (confirm that WebDNA > has been closed and restarted) - check the triggers: > they are still there > > - chris > > On Dec 30, 2011, at 12:07, Kenneth Grome wrote: > > I just learned that something completely wiped out my > > triggers.db 7 days ago -- it is completely blank -- and > > I have no idea what might have caused this. > > > > Does anyone else have a clue why this might happen? > > > > Along with other things I was using it to bill clients > > automatically. But the bills never went out last week, > > which explains why I never got paid this week. > > > > I'm going to recreate my triggers, and I'm adding a new > > trigger -- one that will send me an email every day to > > confirm that triggers are still working. Then I will > > know when this happens again from the lack of a daily > > email, rather than learning about it a week later. > > But this does not make me feel any more confident > > about trusting triggers, and that's why I am hoping > > for an explanation of how this could have happened in > > the first place. > > > > I have not made any config changes on the server in > > months, nor has anyone else -- except possibly the > > hosting company -- and I do not understand how the > > hosting company's potential changes might have wiped > > out my triggers.db while leaving all the other db's > > intact and functioning properly. > > > > The only thing I can think of is that maybe the > > flushdatabases tag does NOT flush the triggers.db to > > disk, so the triggers.db always remains volatile in > > RAM ... and therefore it is subject to being wiped out > > when the server crashes or the VPS is moved to a > > different computer. > > > > ??? > > > > 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 > > --------------------------------------------------------- > 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:
[SearchString] usage (1997)
Does it use the two Processors ? (1999)
Visitor info (2000)
taxrate - off by 1 cent (1997)
WebCat2: Items xx to xx shown, etc. (1997)
Sorting search by date. (2000)
missing records (1998)
[writefile] and CR's (2001)
Multiple Selections in Pull-Down Menu (2000)
Something wrong with this list? (2006)
Fun with dates (1997)
Searching for (field1 OR field2) AND field3 (2000)
European dates (1998)
Question re: FlushDatabases (1997)
Issue with plug-in Webcat, webstar 4.x, SSL and IE when using the backbuttom (2000)
[founditems][replacefounditems] (2003)
Lost Field (1998)
Running _every_ page through WebCat ? (1997)
WebCatalog f2 Installation (1997)
[ConvertChars] problem (1997)