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:
[WebDNA] test (2008)
5.1c not running on iTools 7.3 (2004)
Giving out error pages (1997)
Can't ping (problem with [shell]) (2006)
PIXO support (1997)
PCS Frames (1997)
[WebDNA] sem_open bugfix for os x version 6.2 (2012)
Reversed words (1997)
IE Cache Problems... (1999)
WebCat2.0 acgi vs plugin (1997)
test (2002)
WebDNA 5 - Privacy Issue (Built in sniffer) (2003)
Beta Documentation (1997)
WebCat2 several catalogs? (1997)
[OT] JavaScript Error (2002)
Trouble with carts (2000)
Math, Multiple Equasions and Show/Hide (1998)
Updating a database once per day - An example (1998)
Images (2000)
I have observed and I am gone. (1998)