Re: Database monitoring
This WebDNA talk-list message is from 2005
It keeps the original formatting.
numero = 63538
interpreted = N
texte = Thanks for the reply John. We dont have any triggers running on these DB's at all. As far as timeframe, it has happened at several different times during the day, nothing that constitutes a pattern that we can follow. The funny thing is that we had an entire record disappear yesterday, then today it reappeared. These problems just started when we moved over to a new server cluster. We have 2 App servers that retrieves data from the data server. I am wondering if there isnt some kind of conflict/caching happening there causing this. -----Original Message----- From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of John Peacock Sent: Thursday, December 01, 2005 2:53 PM To: WebDNA Talk Subject: Re: Database monitoring Eric Miller wrote: > Does anyone know of a script or a way to monitor events that happen to a > WebDNA database. We are experiencing some strange things (Field data in > records disappearing, database locking, etc) and it would be nice to catch > what random process is causing this. The only process that accesses WebDNA databases is... WebDNA! If you have eliminated automated triggers (which have a known problem with sandboxes in 6.0 I believe?), then the only other place is some less-well traveled section of your website, possibly caused by some search engine spider walking your pages in an odd fashion. If you can determine some time frame during which this occurs (once an hour, once a day, etc), you can turn on the "Technical Support Information" option on the Preferences page; this writes a line prior to interpreting any page. And then you have to sift though that data for a clue. It will be a lot of data, so don't leave it on for long if you are short of diskspace. In my experience, the majority of problems are code which assumes some external variable is set to reasonable value (for example, code that will work with hostnames but not IP addresses). Believe it or not but it usually is something very stupid and simple, and it will often leap out at you from the debug file. If you make it a habit of always validating all form variables for reasonable values, you will be much less likely to have any problems. HTH John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4501 Forbes Boulevard Suite H Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5748 ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Thanks for the reply John. We dont have any triggers running on these DB's at all. As far as timeframe, it has happened at several different times during the day, nothing that constitutes a pattern that we can follow. The funny thing is that we had an entire record disappear yesterday, then today it reappeared. These problems just started when we moved over to a new server cluster. We have 2 App servers that retrieves data from the data server. I am wondering if there isnt some kind of conflict/caching happening there causing this. -----Original Message----- From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of John Peacock Sent: Thursday, December 01, 2005 2:53 PM To: WebDNA Talk Subject: Re: Database monitoring Eric Miller wrote: > Does anyone know of a script or a way to monitor events that happen to a > WebDNA database. We are experiencing some strange things (Field data in > records disappearing, database locking, etc) and it would be nice to catch > what random process is causing this. The only process that accesses WebDNA databases is... WebDNA! If you have eliminated automated triggers (which have a known problem with sandboxes in 6.0 I believe?), then the only other place is some less-well traveled section of your website, possibly caused by some search engine spider walking your pages in an odd fashion. If you can determine some time frame during which this occurs (once an hour, once a day, etc), you can turn on the "Technical Support Information" option on the Preferences page; this writes a line prior to interpreting any page. And then you have to sift though that data for a clue. It will be a lot of data, so don't leave it on for long if you are short of diskspace. In my experience, the majority of problems are code which assumes some external variable is set to reasonable value (for example, code that will work with hostnames but not IP addresses). Believe it or not but it usually is something very stupid and simple, and it will often leap out at you from the debug file. If you make it a habit of always validating all form variables for reasonable values, you will be much less likely to have any problems. HTH John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4501 Forbes Boulevard Suite H Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5748 ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
"Eric Miller"
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:
Directory Overload (1998)
Re:[ShowIf] and empty fields (1997)
Dreamweaver Extensions for WC (2000)
b12 cannot limit records returned and more. (1997)
Bookmarked URL with cart (1998)
Searching multiple fields from one form field (1997)
Email (1998)
Trigger Error (2001)
Re:Change WebDNA-Talk Mail due to no digest for 1wk (1997)
Separate SSL Server (1997)
Nav4 not specifying cart (1997)
Roundup function? (1997)
wc 2 pro users - sites, quotes wanted (1997)
Some Questions (1997)
WebCatalog 2.0 b 15 mac (1997)
Linux Beta Question (2000)
More on [purchase] (1998)
Emailer and encryption (1997)
What am I missing (1997)
Word wrapping (1997)