Re: [WebDNA] Triggers.db wiped completely blank

This WebDNA talk-list message is from

2011


It keeps the original formatting.
numero = 107863
interpreted = N
texte = --14dae934062382456004b5523340 Content-Type: text/plain; charset=ISO-8859-1 Our server has filled up in the past (runaway db appends/ too many cart files, etc). When the server was full, trying to make a change to any file resulted in completely erasing the file content. For example, using FTP to overwrite a file while the server was full resulted in a 0 byte file. However, our databases were not erased, it just became impossible to append to them. Daniel Meola 301-486-0901 daniel@knifecenter.com On Fri, 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 > --14dae934062382456004b5523340 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Our server has filled up in the past (runaway db appends/ too many cart fil= es, etc). When the server was full, trying to make a change to any file res= ulted in completely erasing the file content. For example, using FTP to ove= rwrite a file while the server was full resulted in a 0 byte file.

However, our databases were not erased, it just became impos= sible to append to them.
Daniel Meola
301-486-090= 1



On Fri, Dec 30, 2011 at 11:58 AM, Kennet= h Grome <kengrom= e@gmail.com> wrote:
It just occurred to me that a remote backup script filled my
storage allotment on this VPS recently. =A0I 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. =A0Therefore 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? =A0If 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. =A0But 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<= br> > >>> 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 <talk@webdna.us>. To
> >>> unsubscribe, E-mail to: <talk-leave@webdna.us>
> >>> archives: http://mail.webdna.us/list/talk@webdna.us
> >>> Bug Reporting: suppo= rt@webdna.us
> >>
> >> ------------------------------------------------------
> >> --- This message is sent to you because you are
> >> subscribed to the mai= ling list <talk@webdna.us>.
> >> To unsubscribe, E-mail to: <talk-leave@webdna.us>
> >> archives: http://mail.webdna.us/list/talk@webdna.us
> >> Bug Reporting: support@w= ebdna.us
> >
> > -------------------------------------------------------
> > -- This message is sent to you because you are
> > subscribed to the mailing list <talk@webdna.us>.
> > To unsubscribe, E-mail to: <talk-leave@webdna.us>
> > archives: http://mail.webdna.us/list/talk@webdna.us
> > Bug Reporting: support@webdn= a.us
>
> ---------------------------------------------------------
> This message is sent to you because you are subscribed to
> the mailing list <talk@webdna.us<= /a>>.
> To unsubscribe, E-mail to: <talk-leave@webdna.us>
> archives: http://mail.webdna.us/list/talk@webdna.us
> Bug Reporting: support@webdna.us<= /a>
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us&g= t;.
To unsubscribe, E-mail to: <talk= -leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us

--14dae934062382456004b5523340-- Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Triggers.db wiped completely blank (christophe.billiottet@webdna.us 2011)
  2. Re: [WebDNA] Triggers.db wiped completely blank (Donovan Brooke 2011)
  3. Re: [WebDNA] Triggers.db wiped completely blank (Kenneth Grome 2011)
  4. Re: [WebDNA] Triggers.db wiped completely blank (Kenneth Grome 2011)
  5. Re: [WebDNA] Triggers.db wiped completely blank (Kenneth Grome 2011)
  6. Re: [WebDNA] Triggers.db wiped completely blank (christophe.billiottet@webdna.us 2011)
  7. Re: [WebDNA] Triggers.db wiped completely blank (Govinda 2011)
  8. Re: [WebDNA] Triggers.db wiped completely blank (Daniel Meola 2011)
  9. Re: [WebDNA] Triggers.db wiped completely blank (chris@usinter.net 2011)
  10. Re: [WebDNA] Triggers.db wiped completely blank (Govinda 2011)
  11. Re: [WebDNA] Triggers.db wiped completely blank (Kenneth Grome 2011)
  12. Re: [WebDNA] Triggers.db wiped completely blank (Kenneth Grome 2011)
  13. Re: [WebDNA] Triggers.db wiped completely blank (christophe.billiottet@webdna.us 2011)
  14. Re: [WebDNA] Triggers.db wiped completely blank (Kenneth Grome 2011)
  15. Re: [WebDNA] Triggers.db wiped completely blank (Donovan Brooke 2011)
  16. Re: [WebDNA] Triggers.db wiped completely blank (christophe.billiottet@webdna.us 2011)
  17. Re: [WebDNA] Triggers.db wiped completely blank (Kenneth Grome 2011)
  18. Re: [WebDNA] Triggers.db wiped completely blank (Govinda 2011)
  19. [WebDNA] Triggers.db wiped completely blank (Kenneth Grome 2011)
--14dae934062382456004b5523340 Content-Type: text/plain; charset=ISO-8859-1 Our server has filled up in the past (runaway db appends/ too many cart files, etc). When the server was full, trying to make a change to any file resulted in completely erasing the file content. For example, using FTP to overwrite a file while the server was full resulted in a 0 byte file. However, our databases were not erased, it just became impossible to append to them. Daniel Meola 301-486-0901 daniel@knifecenter.com On Fri, 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 > --14dae934062382456004b5523340 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Our server has filled up in the past (runaway db appends/ too many cart fil= es, etc). When the server was full, trying to make a change to any file res= ulted in completely erasing the file content. For example, using FTP to ove= rwrite a file while the server was full resulted in a 0 byte file.

However, our databases were not erased, it just became impos= sible to append to them.
Daniel Meola
301-486-090= 1



On Fri, Dec 30, 2011 at 11:58 AM, Kennet= h Grome <kengrom= e@gmail.com> wrote:
It just occurred to me that a remote backup script filled my
storage allotment on this VPS recently. =A0I 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. =A0Therefore 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? =A0If 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. =A0But 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<= br> > >>> 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 <talk@webdna.us>. To
> >>> unsubscribe, E-mail to: <talk-leave@webdna.us>
> >>> archives: http://mail.webdna.us/list/talk@webdna.us
> >>> Bug Reporting: suppo= rt@webdna.us
> >>
> >> ------------------------------------------------------
> >> --- This message is sent to you because you are
> >> subscribed to the mai= ling list <talk@webdna.us>.
> >> To unsubscribe, E-mail to: <talk-leave@webdna.us>
> >> archives: http://mail.webdna.us/list/talk@webdna.us
> >> Bug Reporting: support@w= ebdna.us
> >
> > -------------------------------------------------------
> > -- This message is sent to you because you are
> > subscribed to the mailing list <talk@webdna.us>.
> > To unsubscribe, E-mail to: <talk-leave@webdna.us>
> > archives: http://mail.webdna.us/list/talk@webdna.us
> > Bug Reporting: support@webdn= a.us
>
> ---------------------------------------------------------
> This message is sent to you because you are subscribed to
> the mailing list <talk@webdna.us<= /a>>.
> To unsubscribe, E-mail to: <talk-leave@webdna.us>
> archives: http://mail.webdna.us/list/talk@webdna.us
> Bug Reporting: support@webdna.us<= /a>
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us&g= t;.
To unsubscribe, E-mail to: <talk= -leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us

--14dae934062382456004b5523340-- Daniel Meola

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:

session handling (2004) Template not found error messages (1997) Help with database strategy (1998) WCS Newbie question (1997) Off Topic: Frames Killer? (1998) Can WC remember people? (1998) nested context (1998) Two submit buttons ? (1997) Associative lookup style? + bit more (1997) Cookies and domains (2006) UPPERCASE (1997) Locking up with WebCatalog... (1997) Security (2002) protect acting looney?? (2003) WC2b12: Yes, Formulas.db is for real (1997) Check boxes (1997) Emailer help....! (1997) Interesting speed comparison .. (2003) Running 2 two WebCatalog.acgi's (1996) [shell] command (2000)