Re: [WebDNA] WebDNA Crashing or Not **YES**
This WebDNA talk-list message is from 2008
It keeps the original formatting.
numero = 100300
interpreted = N
texte = Yes, the errors are intermittent. Yes the code, and case is correct. Seriously, the system can't even find it's own admin files!!! I tried to log in to the admin and got: " Error: template 'CGI-Executables/WebCatalogEngine/Admin/Welcome.tpl' not found" Details: OS.....................: Mac OSX 10.3.9 hardware...............: G4 Xserve hardware is X years old: 4 years apache version.........: Apache 2.0.55 (iTools 8.0.5) WebDNA version.........: 6.0a (whatever the last patch was...) approx. size of WebDNA bases in RAM: 2 megs ? RAM size...............: 2 GB crashes randomly.......: ? crashes every X hours..: 72 hrs? Is there a backup system? Yes Any other application running on the same box? No UPS....................: Yes --------------------------------- The logs are chock-full of "www WebDNA[23572]: Could not establish connection with the module." I truly hope that these server instability issues are at the top of your priority list, and that you have gathered the resources to deal with, what I see as an impending fatal flaw of WebDNA. Until you get this handled, any efforts on new features or marketing will be as effective as rearranging the deck chairs on the Titanic. "...can't hold on much longer." Truly concerned, -Chris On 7/15/08 9:12 AM, "Donovan Brooke"
wrote: > cw@e-wave.net wrote: > >> We have experienced the same crashing symptoms as everyone else all along, >> but we also started getting crippling db errors at the same. >> >> "An unknown error occurred:
DBError
prefs.db
Database file could >> not be found or opened
" >> >> Yes the db's are there. >> Yes, the ownership and permissions are correct... AFAIK >> >> At this point, the custom script that restarts Webcatalog is the only thing >> that is keeping it running, but it is a very, very serious problem for us, >> and it is getting worse. >> >> Is anyone else experiencing "db not found errors"? Any suggestions? >> >> Thanks, >> -Chris > > > Hard to comment without details Chris, but, in addition to permissions, > you might want to check "case". Lots of times, especially in working with a > site > that has made it's way from the classic Mac OS to a new Mac or Linux > server, there will be left over case problems. "Prefs.db" is not the > same as "prefs.db". If the problem in intermittent, then this > is always something to consider as calls to a single database can > happen in many different places within a site. > > > Donovan > >
Associated Messages, from the most recent to the oldest:
Yes, the errors are intermittent. Yes the code, and case is correct. Seriously, the system can't even find it's own admin files!!! I tried to log in to the admin and got: " Error: template 'CGI-Executables/WebCatalogEngine/Admin/Welcome.tpl' not found" Details: OS.....................: Mac OSX 10.3.9 hardware...............: G4 Xserve hardware is X years old: 4 years apache version.........: Apache 2.0.55 (iTools 8.0.5) WebDNA version.........: 6.0a (whatever the last patch was...) approx. size of WebDNA bases in RAM: 2 megs ? RAM size...............: 2 GB crashes randomly.......: ? crashes every X hours..: 72 hrs? Is there a backup system? Yes Any other application running on the same box? No UPS....................: Yes --------------------------------- The logs are chock-full of "www WebDNA[23572]: Could not establish connection with the module." I truly hope that these server instability issues are at the top of your priority list, and that you have gathered the resources to deal with, what I see as an impending fatal flaw of WebDNA. Until you get this handled, any efforts on new features or marketing will be as effective as rearranging the deck chairs on the Titanic. "...can't hold on much longer." Truly concerned, -Chris On 7/15/08 9:12 AM, "Donovan Brooke" wrote: > cw@e-wave.net wrote: > >> We have experienced the same crashing symptoms as everyone else all along, >> but we also started getting crippling db errors at the same. >> >> "An unknown error occurred:
DBError
prefs.db
Database file could >> not be found or opened
" >> >> Yes the db's are there. >> Yes, the ownership and permissions are correct... AFAIK >> >> At this point, the custom script that restarts Webcatalog is the only thing >> that is keeping it running, but it is a very, very serious problem for us, >> and it is getting worse. >> >> Is anyone else experiencing "db not found errors"? Any suggestions? >> >> Thanks, >> -Chris > > > Hard to comment without details Chris, but, in addition to permissions, > you might want to check "case". Lots of times, especially in working with a > site > that has made it's way from the classic Mac OS to a new Mac or Linux > server, there will be left over case problems. "Prefs.db" is not the > same as "prefs.db". If the problem in intermittent, then this > is always something to consider as calls to a single database can > happen in many different places within a site. > > > Donovan > >
Chris Wilkinson
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:
[WebDNA] Cicada - WebDNA_CICADA_6.1.b02 - gratz and request...! (2009)
WC2.0 Memory Requirements (1997)
WebCat vs MS SiteServer? (1999)
Shhh, very quiet. (2006)
WebCatalog NT beta 18 problem (1997)
Test - sorry (2003)
Webstar 1.3.1 PPC (1997)
So many lookers, hey smith micro (2003)
Passing WebCat data to SSL server (1997)
Webstar Search and WebDNA (2000)
japanese characters (1997)
Problem (1997)
OS X, Communigate Pro & Line Breaks (2003)
Off Topic: Frames Killer? (1998)
Tags not being Interpreted-Resending (1999)
Reversed words (1997)
Forumulas.db & Variables (2002)
Image upload (2000)
bypassing typo's (1998)
Displaying text and populating form fields (2005)