Re: [WebDNA] Processor Maxing out

This WebDNA talk-list message is from

2010


It keeps the original formatting.
numero = 104982
interpreted = N
texte = On 4 Mar 2010, at 22:14, Tony Miller wrote: >>> Made the changes, but the processor is still pegged. Going to try = making this site inactive in the Sandbox Admin to see if it quits. It = might not be this site. We set up another new site yesterday about the = same time this started too. Just what I need, more variables. I think you need to pin down which site is causing the issue first, then = you can track down the code that is causing the problem. Whenever we have a problem on a server that isn't sorted by restarting a = service or rebooting the box one of the first things we look for is what = has changed. It seems to me a bit of a coincidence that this new site was added at = the same time the problem surfaced I'd shut that site off first. Put up a plain holding page if the site = can't just disappear for a few minutes. If that isn't the cause then work through the sites on the server. = Disabling and enabling them one by one. Eventually the cpu will drop = down to normal levels when you turn off the site causing problems. Once you have that look for any recent changes to the code. Paul=20= Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Processor Maxing out (Tony Miller 2010)
  2. Re: [WebDNA] Processor Maxing out (Tony Miller 2010)
  3. Re: [WebDNA] Processor Maxing out (Donovan Brooke 2010)
  4. Re: [WebDNA] Processor Maxing out (Tony Miller 2010)
  5. Re: [WebDNA] Processor Maxing out (Donovan Brooke 2010)
  6. Re: [WebDNA] Processor Maxing out (Tony Miller 2010)
  7. Re: [WebDNA] Processor Maxing out (Donovan Brooke 2010)
  8. Re: [WebDNA] Processor Maxing out (Tony Miller 2010)
  9. Re: [WebDNA] Processor Maxing out (Donovan Brooke 2010)
  10. Re: [WebDNA] Processor Maxing out (Tony Miller 2010)
  11. Re: [WebDNA] Processor Maxing out (Donovan Brooke 2010)
  12. Re: [WebDNA] Processor Maxing out (Tony Miller 2010)
  13. Re: [WebDNA] Processor Maxing out (Tony Miller 2010)
  14. Re: [WebDNA] Processor Maxing out (Tennis De Jong 2010)
  15. Re: [WebDNA] Processor Maxing out (Donovan Brooke 2010)
  16. Re: [WebDNA] Processor Maxing out (Tony Miller 2010)
  17. Re: [WebDNA] Processor Maxing out (Tony Miller 2010)
  18. Re: [WebDNA] Processor Maxing out (Tennis De Jong 2010)
  19. Re: [WebDNA] Processor Maxing out (Tony Miller 2010)
  20. Re: [WebDNA] Processor Maxing out (Paul Willis 2010)
  21. Re: [WebDNA] Processor Maxing out (Paul Willis 2010)
  22. Re: [WebDNA] Processor Maxing out (Donovan Brooke 2010)
  23. Re: [WebDNA] Processor Maxing out (Tony Miller 2010)
  24. Re: [WebDNA] Processor Maxing out (Paul Willis 2010)
  25. Re: [WebDNA] Processor Maxing out (Tony Miller 2010)
  26. Re: [WebDNA] Processor Maxing out (Tony Miller 2010)
  27. Re: [WebDNA] Processor Maxing out (Paul Willis 2010)
  28. Re: [WebDNA] Processor Maxing out (Tony Miller 2010)
  29. Re: [WebDNA] Processor Maxing out (Donovan Brooke 2010)
  30. Re: [WebDNA] Processor Maxing out (Tony Miller 2010)
  31. Re: [WebDNA] Processor Maxing out (Donovan Brooke 2010)
  32. Re: [WebDNA] Processor Maxing out (Tony Miller 2010)
  33. Re: [WebDNA] Processor Maxing out (Tony Miller 2010)
  34. Re: [WebDNA] Processor Maxing out (Dan Strong 2010)
  35. Re: [WebDNA] Processor Maxing out (Donovan Brooke 2010)
  36. Re: [WebDNA] Processor Maxing out (Donovan Brooke 2010)
  37. Re: [WebDNA] Processor Maxing out (Tony Miller 2010)
  38. Re: [WebDNA] Processor Maxing out (Donovan Brooke 2010)
  39. Re: [WebDNA] Processor Maxing out (Donovan Brooke 2010)
  40. [WebDNA] Processor Maxing out (Tony Miller 2010)
On 4 Mar 2010, at 22:14, Tony Miller wrote: >>> Made the changes, but the processor is still pegged. Going to try = making this site inactive in the Sandbox Admin to see if it quits. It = might not be this site. We set up another new site yesterday about the = same time this started too. Just what I need, more variables. I think you need to pin down which site is causing the issue first, then = you can track down the code that is causing the problem. Whenever we have a problem on a server that isn't sorted by restarting a = service or rebooting the box one of the first things we look for is what = has changed. It seems to me a bit of a coincidence that this new site was added at = the same time the problem surfaced I'd shut that site off first. Put up a plain holding page if the site = can't just disappear for a few minutes. If that isn't the cause then work through the sites on the server. = Disabling and enabling them one by one. Eventually the cpu will drop = down to normal levels when you turn off the site causing problems. Once you have that look for any recent changes to the code. Paul=20= Paul Willis

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:

Email Spam a bit of Hell (2004) Formating found categories (1997) Browser Problem?!? Still getting Error message using (1997) Part Html part WebDNA (1997) formulas.db [feature request] (2003) [WebDNA] Apache configuration fail when... (2013) quantity minimum problem (1997) Encryption of E-mail (1998) Frames and WebCat (1997) MacAuthorize and WebMerchant (1997) Some Advise needed (1997) [UPPERCASE] (1997) Quitting WebMerchant ? (1997) New iMac, now ... how do I make webdna serve .html files? (2005) Not really WebCat- (1997) Extended [Convertchars] needed (1997) Not really WebCat (1997) WebCat2b13MacPlugIn - [include] doesn't allow creator (1997) checking for [ and ] in form fields ... (1997) Quit revisited (1997)