Re: [WebDNA] Triggers.db wiped completely blank
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 107855
interpreted = N
texte = 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=20 > Triggers.db 7 days ago -- it is completely blank -- and I=20 > have no idea what might have caused this. =20 >=20 > Does anyone else have a clue why this might happen? >=20 > Along with other things I was using it to bill clients=20 > automatically. But the bills never went out last week,=20 > which explains why I never got paid this week. =20 >=20 > I'm going to recreate my triggers, and I'm adding a new=20 > trigger -- one that will send me an email every day to=20 > confirm that triggers are still working. Then I will know=20 > when this happens again from the lack of a daily email,=20 > rather than learning about it a week later. But this does=20 > not make me feel any more confident about trusting triggers,=20 > and that's why I am hoping for an explanation of how this=20 > could have happened in the first place. >=20 > I have not made any config changes on the server in months,=20 > nor has anyone else -- except possibly the hosting company=20 > -- and I do not understand how the hosting company's=20 > potential changes might have wiped out my Triggers.db while=20 > leaving all the other db's intact and functioning properly. >=20 > The only thing I can think of is that maybe the=20 > flushdatabases tag does NOT flush the Triggers.db to disk, so=20 > the Triggers.db always remains volatile in RAM ... and=20 > therefore it is subject to being wiped out when the server=20 > 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
Associated Messages, from the most recent to the oldest:
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=20 > triggers.db 7 days ago -- it is completely blank -- and I=20 > have no idea what might have caused this. =20 >=20 > Does anyone else have a clue why this might happen? >=20 > Along with other things I was using it to bill clients=20 > automatically. But the bills never went out last week,=20 > which explains why I never got paid this week. =20 >=20 > I'm going to recreate my triggers, and I'm adding a new=20 > trigger -- one that will send me an email every day to=20 > confirm that triggers are still working. Then I will know=20 > when this happens again from the lack of a daily email,=20 > rather than learning about it a week later. But this does=20 > not make me feel any more confident about trusting triggers,=20 > and that's why I am hoping for an explanation of how this=20 > could have happened in the first place. >=20 > I have not made any config changes on the server in months,=20 > nor has anyone else -- except possibly the hosting company=20 > -- and I do not understand how the hosting company's=20 > potential changes might have wiped out my triggers.db while=20 > leaving all the other db's intact and functioning properly. >=20 > The only thing I can think of is that maybe the=20 > flushdatabases tag does NOT flush the triggers.db to disk, so=20 > the triggers.db always remains volatile in RAM ... and=20 > therefore it is subject to being wiped out when the server=20 > 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
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:
WebCat2b12 forgets serial # (1997)
Oops, my mistake - (was Bad suffix error) (1997)
Installer needed (2004)
RE: Languages (1997)
check out page (SSL) not loading on Netscape 4.0+ - fixed? (1999)
WebCat2b13MacPlugin - [math][date][/math] problem (1997)
Plugin or CGI or both (1997)
Random Links (2004)
[WebDNA] Search using CL (2017)
Search probl. since change WebCatalog from 2.1.3 to 3.0 (1998)
Browser Info.txt -- newest additions? (1997)
Line items in table cells (1997)
MasterCounter - Does this work?? (1999)
2 easy questions re: [showif] and [sendmail] (1997)
[WebDNA] Styling search results (2009)
WCS Newbie question (1997)
WebCat2b12 - nesting [tags] (1997)
webcat- multiple selection in input field (1997)
carriage returns in data (1997)
Changing price for a SLU based on options (size, etc.) (1997)