[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:

off topic fetch vs PCS photomaster (1997) WebDna Consultants (2004) webcat restarting script on Linux? (1999) WebCatalog dying in NT (1998) search double negative comparison (2001) Multiple adding (1997) Hard Questions ? (1997) Sorting by highest number of matches unique to a field (2003) a small clarification (2002) WebCatalog 2.0 & WebDNA docs in HTML ... (1997) Shipcost formula (2004) Date Formats (1997) Re[2]: Date Time Oddness (1999) [template] tag (1998) Multiple Pulldowns (1997) [authenticate] (1999) Attn: Bug in GeneralStore example b15 (1997) Showif, Hideif reverse logic ? (1997) Emailer help....! (1997) SiteEdit Pro Update Announcement (1997)