[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.=20If 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=1DAny suggestions?Thanks!Dave HurleyManager of Departmental ComputingBiology DepartmentUniversity of Washington = = =20=
Associated Messages, from the most recent to the oldest:
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.=20If 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=1DAny suggestions?Thanks!Dave HurleyManager of Departmental ComputingBiology DepartmentUniversity 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:
Dark Horse Comics success story (1997)
writing db to disk (1997)
cookies (2001)
OT: Quick poll (2003)
Help DebugLevel Content-type: text/html (1998)
taxTotal, grandTotal (1997)
Dark Horse Comics success story (1997)
NetSplat and WebCat2 (1997)
Database (1999)
Question about replacing words (1998)
Using Applescript to process WebCatalog functions (1998)
[WebDNA] 6.2.1 fails on Apache 2.4.6 (2014)
Multi Actions (1999)
Re:mac hack (1997)
Forms Search Questions (1997)
assigning a id no. (2000)
# of real domains on 1 web server (1997)
calculating tax rates, mail order solutions and version 2 (1997)
OLD PROBLEM (1997)
[CART] inside a [LOOP] (1997)