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 thatconstitutes a pattern that we can follow.The funny thing is that we had an entire record disappear yesterday, thentoday it reappeared. These problems just started when we moved over to a newserver cluster. We have 2 App servers that retrieves data from the dataserver. I am wondering if there isnt some kind of conflict/caching happeningthere causing this.-----Original Message-----From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf OfJohn PeacockSent: Thursday, December 01, 2005 2:53 PMTo: WebDNA TalkSubject: Re: Database monitoringEric 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 youhave eliminated automated triggers (which have a known problem withsandboxes in 6.0 I believe?), then the only other place is someless-well traveled section of your website, possibly caused by somesearch engine spider walking your pages in an odd fashion.If you can determine some time frame during which this occurs (once anhour, once a day, etc), you can turn on the "Technical SupportInformation" option on the Preferences page; this writes a line prior tointerpreting any page. And then you have to sift though that data for aclue. It will be a lot of data, so don't leave it on for long if youare short of diskspace.In my experience, the majority of problems are code which assumes someexternal variable is set to reasonable value (for example, code thatwill work with hostnames but not IP addresses). Believe it or not butit usually is something very stupid and simple, and it will often leapout at you from the debug file. If you make it a habit of alwaysvalidating all form variables for reasonable values, you will be muchless likely to have any problems.HTHJohn--John PeacockDirector of Information Research and TechnologyRowman & Littlefield Publishing Group4501 Forbes BoulevardSuite HLanham, MD 20706301-459-3366 x.5010fax 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 toWeb 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 thatconstitutes a pattern that we can follow.The funny thing is that we had an entire record disappear yesterday, thentoday it reappeared. These problems just started when we moved over to a newserver cluster. We have 2 App servers that retrieves data from the dataserver. I am wondering if there isnt some kind of conflict/caching happeningthere causing this.-----Original Message-----From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf OfJohn PeacockSent: Thursday, December 01, 2005 2:53 PMTo: WebDNA TalkSubject: Re: Database monitoringEric 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 youhave eliminated automated triggers (which have a known problem withsandboxes in 6.0 I believe?), then the only other place is someless-well traveled section of your website, possibly caused by somesearch engine spider walking your pages in an odd fashion.If you can determine some time frame during which this occurs (once anhour, once a day, etc), you can turn on the "Technical SupportInformation" option on the Preferences page; this writes a line prior tointerpreting any page. And then you have to sift though that data for aclue. It will be a lot of data, so don't leave it on for long if youare short of diskspace.In my experience, the majority of problems are code which assumes someexternal variable is set to reasonable value (for example, code thatwill work with hostnames but not IP addresses). Believe it or not butit usually is something very stupid and simple, and it will often leapout at you from the debug file. If you make it a habit of alwaysvalidating all form variables for reasonable values, you will be muchless likely to have any problems.HTHJohn--John PeacockDirector of Information Research and TechnologyRowman & Littlefield Publishing Group4501 Forbes BoulevardSuite HLanham, MD 20706301-459-3366 x.5010fax 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 toWeb 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:
Nested tags count question (1997)
Date format question (1998)
RE: Error -108 (1997)
Error upgrading to webDNA 5.1e (2003)
The beginning (1997)
New servers and new inline cache (1997)
webmerchant and check cashing (1998)
WebCat2 - storing unformatted date data? (1997)
Web Catalog 2 demo (1997)
Banner DNA (1997)
RE: WebDNA-Talk searchable? (1997)
Bug? (1997)
Summing a field full of numbers ... (1997)
RE: redirect with more than 256 characters (1999)
WC TableGrinder (1997)
Help!!!! Purchases not going through! (1997)
_ in front of field name (1998)
apostrophe in search item (1997)
Multi-processor Mac info ... (1997)
Re[2]: WebCatalog 3.0.8 Mac OS (2000)