Re: [WebDNA] Triggers.db wiped completely blank
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 107862
interpreted = N
texte = I can say for certain from experience that a full disk will cause databases to be lost. When it happened to me, any open database became truncated or empty. Chris US Internet On Dec 30, 2011, at 11:58 AM, Kenneth Grome wrote: > It just occurred to me that a remote backup script filled my > storage allotment on this VPS recently. I deleted the > backup files a couple hours later, but might the fact that > the disk was full have caused this problem? > > It seems like this would not cause a problem when the exact > same file -- with the exact same size -- already exists on > disk before the flush. Therefore it's not like WebDNA is > trying to write a larger file to disk than already exists. > > Or is it? > > Would the existing disk-based copy of the file be wiped blank > in this situation? If so, why? > > Sincerely, > Kenneth Grome > > > >> 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, >>> >>> 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 >>> >>> ------------------------------------------------------- >>> -- 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 > --------------------------------------------------------- > 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:
I can say for certain from experience that a full disk will cause databases to be lost. When it happened to me, any open database became truncated or empty. Chris US Internet On Dec 30, 2011, at 11:58 AM, Kenneth Grome wrote: > It just occurred to me that a remote backup script filled my > storage allotment on this VPS recently. I deleted the > backup files a couple hours later, but might the fact that > the disk was full have caused this problem? > > It seems like this would not cause a problem when the exact > same file -- with the exact same size -- already exists on > disk before the flush. Therefore it's not like WebDNA is > trying to write a larger file to disk than already exists. > > Or is it? > > Would the existing disk-based copy of the file be wiped blank > in this situation? If so, why? > > Sincerely, > Kenneth Grome > > > >> 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, >>> >>> 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 >>> >>> ------------------------------------------------------- >>> -- 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 > --------------------------------------------------------- > 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
chris@usinter.net
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] Froala Editor working with WebDNA (2016)
problems with 2 tags shakur (1997)
OT - royalty free images (2002)
webcat- multiple selection in input field (1997)
Country & Ship-to address & other fields ? (1997)
searchable list archive (1997)
Linux WebDNA Server probs (2004)
WebCat2b14MacPlugIn - [include] doesn't hide the search string (1997)
[WebDNA] can webdna set the email header (w/[sendmail]) that controls where bounced email goes? (2012)
All choices on IE different than Netscape (1997)
IP address & domain name problem (2003)
SSL and Webstar 3 with Webcatalog (1998)
Is there a max number of fields? (1998)
A little syntax help (1997)
when will the list move? (nm) (2000)
Adding up weights (1998)
[WebDNA] Sorry WebDNA server not running. (2015)
firewall ports for Mac OS X/WebCatalog (2001)
summ=T (2003)
Emailer (1997)