Re: [WebDNA] Triggers.db wiped completely blank
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 107858
interpreted = N
texte = Absolutely no idea, except that somebody erased your triggers either = intentionally or accidentally. Even if you do not flush or commit to = disk, and even if WebDNA crashes, triggers are not erased. - chris On Dec 30, 2011, at 14:42, Kenneth Grome wrote: > Hi Chris, >=20 > Although this is good news for WebDNA it is not good news=20 > for my use of WebDNA on the VPS I have it installed on. >=20 > Do you have any clue why my Triggers.db file would be wiped=20 > clean like it was for no apparent reason? >=20 > Sincerely, > Kenneth Grome >=20 >=20 >=20 >> Hi Ken! just tested the worst possible situation with the >> triggers: >>=20 >> - 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 >>=20 >> - chris >>=20 >> 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. >>>=20 >>> Does anyone else have a clue why this might happen? >>>=20 >>> 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. >>>=20 >>> 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.=20 >>> 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. >>>=20 >>> 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. >>>=20 >>> 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. >>>=20 >>> ??? >>>=20 >>> 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 >>=20 >> --------------------------------------------------------- >> 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:
Absolutely no idea, except that somebody erased your triggers either = intentionally or accidentally. Even if you do not flush or commit to = disk, and even if WebDNA crashes, triggers are not erased. - chris On Dec 30, 2011, at 14:42, Kenneth Grome wrote: > Hi Chris, >=20 > Although this is good news for WebDNA it is not good news=20 > for my use of WebDNA on the VPS I have it installed on. >=20 > Do you have any clue why my triggers.db file would be wiped=20 > clean like it was for no apparent reason? >=20 > Sincerely, > Kenneth Grome >=20 >=20 >=20 >> Hi Ken! just tested the worst possible situation with the >> triggers: >>=20 >> - 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 >>=20 >> - chris >>=20 >> 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. >>>=20 >>> Does anyone else have a clue why this might happen? >>>=20 >>> 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. >>>=20 >>> 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.=20 >>> 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. >>>=20 >>> 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. >>>=20 >>> 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. >>>=20 >>> ??? >>>=20 >>> 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 >>=20 >> --------------------------------------------------------- >> 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
christophe.billiottet@webdna.us
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:
searching multiple databases (1997)
Um...how do I ask this? (1999)
ShowNext (1997)
[protect admin] (1997)
WebMerchant 1.6 and https (1997)
For those of you not on the WebCatalog Beta... (1997)
possible, WebCat2.0 and checkboxes-restated (1997)
Providing hard copy of database to client (1997)
Snake Bites (1997)
Weird problems with [SHOWIF]s (1997)
How to best sort in a pre-defined item-by-item order ... (2003)
help testing quicktime delivery (1997)
Security for malls with different webmasters (1998)
[WebDNA] Where is Speed Test? (2009)
E-mailer error codes (1997)
OSX Dev Server? (2004)
WebCat2.0 [format thousands .0f] no go (1997)
BIAP relay (1999)
Navigator 4.01 (1997)
[protect admin] (1997)