[WebDNA] crashing loop

This WebDNA talk-list message is from

2011


It keeps the original formatting.
numero = 106682
interpreted = N
texte = Apologies for cross-posting with the forum. After years of running WebDNA reliably, I'm suddenly confronted with = crashing behavior that I can't seem to fix. I'm running WebDNA 6.2 on = Mac OS X Server 10.6.7. After creating some scripts with SQL commands I = managed to cause the process to crash and restart many times per second, = which consumes almost 100% of the CPU and returns a "Sorry WebDNA server = not running" error when pages are hit. Killing and starting the process = doesn't fix the problem, nor does restarting Apache or rebooting the = server.=20 If I watch the system log in Console, I see the WebDNAMonitor process = report that the WebDNA process is alive. Then it's dead. Then it's = restarted. Then it receives a SIGBUS. Repeat infinitely or until I stop = the process manually. It's very reproducible. The suspect code is no longer on the server so that's not the problem = anymore. The only WebDNA code on the server now are files that have been = stable and unchanged for over a year. I've had similar problems only one or two other times in 8 years, so I'm = shocked that a clean reinstall of webDNA doesn't fix the problem as it = has in the past.=1D=1D=1D=1D Any suggestions? Thanks! Dave Hurley Manager of Departmental Computing Biology Department University of Washington = = =20= Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] crashing loop - SOLVED (Dave Hurley 2011)
  2. [WebDNA] crashing loop (Dave Hurley 2011)
Apologies for cross-posting with the forum. After years of running WebDNA reliably, I'm suddenly confronted with = crashing behavior that I can't seem to fix. I'm running WebDNA 6.2 on = Mac OS X Server 10.6.7. After creating some scripts with SQL commands I = managed to cause the process to crash and restart many times per second, = which consumes almost 100% of the CPU and returns a "Sorry WebDNA server = not running" error when pages are hit. Killing and starting the process = doesn't fix the problem, nor does restarting Apache or rebooting the = server.=20 If I watch the system log in Console, I see the WebDNAMonitor process = report that the WebDNA process is alive. Then it's dead. Then it's = restarted. Then it receives a SIGBUS. Repeat infinitely or until I stop = the process manually. It's very reproducible. The suspect code is no longer on the server so that's not the problem = anymore. The only WebDNA code on the server now are files that have been = stable and unchanged for over a year. I've had similar problems only one or two other times in 8 years, so I'm = shocked that a clean reinstall of webDNA doesn't fix the problem as it = has in the past.=1D=1D=1D=1D Any suggestions? Thanks! Dave Hurley Manager of Departmental Computing Biology Department University of Washington = = =20= Dave Hurley

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:

Emailer Problem (1999) RE: Redirect (1998) [WebDNA] Friday Fun with Variable Names (2017) 2.1 bugs left over from beta cycle (1998) WebCat Admin access w/ClearlyHome p.i. (1997) Re2: Calculating multiple shipping... (1997) Grep support request for SMSI ... (2003) [cart] tag (2000) cart info (1998) Quit revisited (1997) [Webcat 2]Next (1997) Transferring textareas (1997) suggestions (1998) [WebDNA] test email (2014) Most Efficiant Way to do restricted Areas (1997) Great product and great job ! (1997) WCS Newbie question (1997) The Depths of Credit Card Payment (2003) Re:no [search] with NT (1997) Need help (1998)