Re: [WebDNA] Triggers.db wiped completely blank
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 107865
interpreted = N
texte = It could explain the problem, yes, assuming WebDNA is trying to flush = something to disk or write a file at the time the disk is full: the file = could be either corrupted or not written at all, and if we get a = reboot/restart afterwards, WebDNA would load the RAM with an empty file. Never tested that, so it is just a guess. - chris On Dec 30, 2011, at 14:58, Kenneth Grome wrote: > It just occurred to me that a remote backup script filled my=20 > storage allotment on this VPS recently. I deleted the=20 > backup files a couple hours later, but might the fact that=20 > the disk was full have caused this problem? >=20 > It seems like this would not cause a problem when the exact=20 > same file -- with the exact same size -- already exists on=20 > disk before the flush. Therefore it's not like WebDNA is=20 > trying to write a larger file to disk than already exists. >=20 > Or is it? >=20 > Would the existing disk-based copy of the file be wiped blank=20 > in this situation? If so, why? >=20 > Sincerely, > Kenneth Grome >=20 >=20 >=20 >> 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. >>=20 >> - chris >>=20 >> 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 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 clean like it was for no apparent reason? >>>=20 >>> Sincerely, >>> Kenneth Grome >>>=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.=20 >>>>> 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. >>>>>=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 >>>=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 >>=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:
It could explain the problem, yes, assuming WebDNA is trying to flush = something to disk or write a file at the time the disk is full: the file = could be either corrupted or not written at all, and if we get a = reboot/restart afterwards, WebDNA would load the RAM with an empty file. Never tested that, so it is just a guess. - chris On Dec 30, 2011, at 14:58, Kenneth Grome wrote: > It just occurred to me that a remote backup script filled my=20 > storage allotment on this VPS recently. I deleted the=20 > backup files a couple hours later, but might the fact that=20 > the disk was full have caused this problem? >=20 > It seems like this would not cause a problem when the exact=20 > same file -- with the exact same size -- already exists on=20 > disk before the flush. Therefore it's not like WebDNA is=20 > trying to write a larger file to disk than already exists. >=20 > Or is it? >=20 > Would the existing disk-based copy of the file be wiped blank=20 > in this situation? If so, why? >=20 > Sincerely, > Kenneth Grome >=20 >=20 >=20 >> 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. >>=20 >> - chris >>=20 >> 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 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 clean like it was for no apparent reason? >>>=20 >>> Sincerely, >>> Kenneth Grome >>>=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.=20 >>>>> 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. >>>>>=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 >>>=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 >>=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:
Maximum of found items?? (2000)
Where's Cart Created ? (1997)
WebMerchant? (1998)
Checkboxes (1998)
flushdatabases (1997)
RE: WebDNA-Talk searchable? (1997)
Need help... (1997)
Which version to buy? (2000)
Searching multiple fields from one form field (1997)
searching multiple databases in single search (1997)
[protect] on NT? (1997)
[showif] based on data from [tcpconnect][tcpsend]? (2000)
[WriteFile] problems (1997)
Upload via Browser (1999)
Adding Multiple files to a cart at once (1998)
japanese characters (1997)
Nitro plugin? (1998)
2nd WebCatalog2 Feature Request (1996)
Credit card processing - UK (1997)
Looking for WebCatalog Linux experience/comments. (2001)