Re: [WebDNA] Still having problems
This WebDNA talk-list message is from 2008
It keeps the original formatting.
numero = 100194
interpreted = N
texte = > OS.....................: Mac 10.3.9 + iTools > hardware...............: Mac Mini 1.25 G4 > hardware is X years old 2 > apache version.........: 2 > WebDNA version.........: 6.0a > approx. size of WebDNA bases in RAM: 50 Mb > RAM size...............: 1Gb > > crashes randomly.......: about every 10 days despite restarting WebDNA every 24 hours > crashes every X hours..: ? Exactly 72 hours, 20 mins unless it's restarted as above. > > Is there a backup system? Synchronize Pr X runs every 24 hours and copies Tenon folder via AppleTalk > Any other application running on the same box? Page Sentry V4.1.3 > UPS....................: ? (battery reset every X hours might crash a > server if the battery is dead) Machine is located in air conditioned server room at http://www.internetf.co.uk/ Our second machine is exactly the same as the above but doesn't get any hits and falls over randomly about every 10 days. On both machines, about half an hour before it fails completely, we get '[WebDNA] failed to connect to the module' in the system log and shell commands return nothing. This started about the same time as it did for everyone else, about mid March 2008 Regards, Colin Sidwell Christophe Billiottet wrote: > To all WebDNA customers with crash problems, would you be so kind to > give us those informations? > > OS.....................: > hardware...............: > hardware is X years old > apache version.........: > WebDNA version.........: > approx. size of WebDNA bases in RAM: > RAM size...............: > > crashes randomly.......: ? > crashes every X hours..: ? > > Is there a backup system? > Any other application running on the same box? > UPS....................: ? (battery reset every X hours might crash a > server if the battery is dead) > > Thank you! > chris > > On Jul 2, 2008, at 19:34, Colin Sidwell wrote: > >> I agree that it's probably not in the WebDna code as such as it would >> always have been a problem but had I bought the source code with the >> intention of bringing new versions to market, the first thing I would >> look at is this problem. >> >> Looking back at the list, a lot of developers have moved away from DNA >> due to the lack of support and communication from SM and I for one >> would not invest any more time or money developing on a platform >> that's become so unstable. >> >> Prior to this issue, I think DNA was the best solution for quick >> deployment of database driven sites despite the few bugs we've had to >> work around over the years. >> >> I have read with great interest the news that there is to be further >> development of the product and am pleased to see that previously >> disgruntled users have already pledged to return to the fold but I >> just don't see how the new owners are going to market it whilst they >> don't have an solution for this issue. >> >> Perhaps their strap line will be- >> >> "It's a great product but it regularly falls over for 50% of users and >> we've no idea why, but please buy it anyway." >> >> Prior to writing this post I have looked back over the posts from the >> new owners and cannot find any mention of this issue. Perhaps they are >> some of of the lucky few who've not been affected by it, if so, they >> should count themselves very fortunate. >> >> I think Bob Atchisons' post sums it up for all of us who have had >> irate clients of the phone in the middle of the night- >> >> "I cannot take a day off anymore because of this, we have to monitor >> the servers 24/7." >> >> Colin Sidwell >> >> Christophe Billiottet wrote: >>> Concerning this problem, we think it is not in WebDNA code itself, >>> otherwise it would have behaved like this since the beginning. Also, >>> only some customers got this problem. >>> Running servers of all sorts from years, i can think of many reasons >>> why a server will start crashing, or even why just some applications >>> will start crashing regularely: hardware reasons (dead fan, bad >>> capacitor, disk problem) or software reasons. A simple backup could >>> overheat a CPU with a bad fan and kill part of the processes (we have >>> had this problem few days ago). >>> The problem we have here, in my opinion, should be solved by a >>> complete OS reinstall and a WebDNA reinstall. >>> We talked about this to SMSI, particularely concerning the "phone >>> home" suspicion; Scott told us >>> "It has been awhile, and I do not have the code in front of me at the >>> moment. But I do remember taking into consideration the possibility of >>> the license server 'not being there' when the phone-home code is >>> executed. So if the licensing log server is down, it should not have a >>> negative impact on WebDNA engine performance. From memory, I think it >>> was set to phone home every two hours." >>> We will of course check into this deeply, but i doubt we will find >>> anything that could explain the crashes in WebDNA code. >>> - chris >>> On Jul 2, 2008, at 18:02, Bob Atchison wrote: >>>> We have this problem constantly still and it drives us nuts. We >>>> restart all the time, it still happens. We have done everything. >>>> It is not an issue of anything with a glitch in the software or some >>>> issue coming from outside... >>>> >>>> We built all of our sites in WebDNA until this started and know we >>>> are doing everything new in PHP. We have been a customer since 96 >>>> or 97 and started with Web Catalog and Webstar. >>>> >>>> I cannot take a day off anymore because of this, we have to monitor >>>> the servers 24/7. It's a nightmare for us and our customers. We >>>> used to have our customers run their own WebDNA servers but we can't >>>> anymore because of the problem. How can you use software that fails >>>> constantly like this. >>>> >>>> It is a huge problem that must be addressed right away. SM ignored >>>> this but the new company cannot. Meanwhile we are forced to go to PHP. >>>> >>>> Bob Atchison >>>> >>>> >>>> Bob Atchison >>>> President/Creative Director >>>> Pallasart >>>> http://www.pallasweb.com >>>> 101 Laurel Lane >>>> Austin, TX 78705 >>>> 512 469-7454 >>>> fax: 512 233-2672 >>>> toll free: 866 513-8916 >>>> >> > > >
Associated Messages, from the most recent to the oldest:
> OS.....................: Mac 10.3.9 + iTools > hardware...............: Mac Mini 1.25 G4 > hardware is X years old 2 > apache version.........: 2 > WebDNA version.........: 6.0a > approx. size of WebDNA bases in RAM: 50 Mb > RAM size...............: 1Gb > > crashes randomly.......: about every 10 days despite restarting WebDNA every 24 hours > crashes every X hours..: ? Exactly 72 hours, 20 mins unless it's restarted as above. > > Is there a backup system? Synchronize Pr X runs every 24 hours and copies Tenon folder via AppleTalk > Any other application running on the same box? Page Sentry V4.1.3 > UPS....................: ? (battery reset every X hours might crash a > server if the battery is dead) Machine is located in air conditioned server room at http://www.internetf.co.uk/ Our second machine is exactly the same as the above but doesn't get any hits and falls over randomly about every 10 days. On both machines, about half an hour before it fails completely, we get '[WebDNA] failed to connect to the module' in the system log and shell commands return nothing. This started about the same time as it did for everyone else, about mid March 2008 Regards, Colin Sidwell Christophe Billiottet wrote: > To all WebDNA customers with crash problems, would you be so kind to > give us those informations? > > OS.....................: > hardware...............: > hardware is X years old > apache version.........: > WebDNA version.........: > approx. size of WebDNA bases in RAM: > RAM size...............: > > crashes randomly.......: ? > crashes every X hours..: ? > > Is there a backup system? > Any other application running on the same box? > UPS....................: ? (battery reset every X hours might crash a > server if the battery is dead) > > Thank you! > chris > > On Jul 2, 2008, at 19:34, Colin Sidwell wrote: > >> I agree that it's probably not in the WebDna code as such as it would >> always have been a problem but had I bought the source code with the >> intention of bringing new versions to market, the first thing I would >> look at is this problem. >> >> Looking back at the list, a lot of developers have moved away from DNA >> due to the lack of support and communication from SM and I for one >> would not invest any more time or money developing on a platform >> that's become so unstable. >> >> Prior to this issue, I think DNA was the best solution for quick >> deployment of database driven sites despite the few bugs we've had to >> work around over the years. >> >> I have read with great interest the news that there is to be further >> development of the product and am pleased to see that previously >> disgruntled users have already pledged to return to the fold but I >> just don't see how the new owners are going to market it whilst they >> don't have an solution for this issue. >> >> Perhaps their strap line will be- >> >> "It's a great product but it regularly falls over for 50% of users and >> we've no idea why, but please buy it anyway." >> >> Prior to writing this post I have looked back over the posts from the >> new owners and cannot find any mention of this issue. Perhaps they are >> some of of the lucky few who've not been affected by it, if so, they >> should count themselves very fortunate. >> >> I think Bob Atchisons' post sums it up for all of us who have had >> irate clients of the phone in the middle of the night- >> >> "I cannot take a day off anymore because of this, we have to monitor >> the servers 24/7." >> >> Colin Sidwell >> >> Christophe Billiottet wrote: >>> Concerning this problem, we think it is not in WebDNA code itself, >>> otherwise it would have behaved like this since the beginning. Also, >>> only some customers got this problem. >>> Running servers of all sorts from years, i can think of many reasons >>> why a server will start crashing, or even why just some applications >>> will start crashing regularely: hardware reasons (dead fan, bad >>> capacitor, disk problem) or software reasons. A simple backup could >>> overheat a CPU with a bad fan and kill part of the processes (we have >>> had this problem few days ago). >>> The problem we have here, in my opinion, should be solved by a >>> complete OS reinstall and a WebDNA reinstall. >>> We talked about this to SMSI, particularely concerning the "phone >>> home" suspicion; Scott told us >>> "It has been awhile, and I do not have the code in front of me at the >>> moment. But I do remember taking into consideration the possibility of >>> the license server 'not being there' when the phone-home code is >>> executed. So if the licensing log server is down, it should not have a >>> negative impact on WebDNA engine performance. From memory, I think it >>> was set to phone home every two hours." >>> We will of course check into this deeply, but i doubt we will find >>> anything that could explain the crashes in WebDNA code. >>> - chris >>> On Jul 2, 2008, at 18:02, Bob Atchison wrote: >>>> We have this problem constantly still and it drives us nuts. We >>>> restart all the time, it still happens. We have done everything. >>>> It is not an issue of anything with a glitch in the software or some >>>> issue coming from outside... >>>> >>>> We built all of our sites in WebDNA until this started and know we >>>> are doing everything new in PHP. We have been a customer since 96 >>>> or 97 and started with Web Catalog and Webstar. >>>> >>>> I cannot take a day off anymore because of this, we have to monitor >>>> the servers 24/7. It's a nightmare for us and our customers. We >>>> used to have our customers run their own WebDNA servers but we can't >>>> anymore because of the problem. How can you use software that fails >>>> constantly like this. >>>> >>>> It is a huge problem that must be addressed right away. SM ignored >>>> this but the new company cannot. Meanwhile we are forced to go to PHP. >>>> >>>> Bob Atchison >>>> >>>> >>>> Bob Atchison >>>> President/Creative Director >>>> Pallasart >>>> http://www.pallasweb.com >>>> 101 Laurel Lane >>>> Austin, TX 78705 >>>> 512 469-7454 >>>> fax: 512 233-2672 >>>> toll free: 866 513-8916 >>>> >> > > >
Colin Sidwell
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:
Sorting nested search (2003)
Fun with Dates - revisited (1997)
WebCat2b15MacPlugin - [protect] (1997)
This list needs a digest: rant, rave... (1997)
Searchable archives gone again??? (2000)
WebCat2b13MacPlugIn - [include] doesn't allow creator (1997)
Looking up two prices in database? (1997)
Add to Cart & List of Products (1997)
Paths, relative paths, webstar server setup and security (Mac) (1997)
Viewing/Editing Databases Online (1999)
[WebDNA] PROBLEM WITH [SQL] (2009)
Firesite and WebCat (1999)
Multiple catalog databases and showcart (1997)
Banners (1997)
Bug Report, maybe (1997)
Problems with [Applescript] (1997)
[append] problem (1997)
WebCatalog for Postcards ? (1997)
ListDatabases & ShowIf (2003)
Emailer (1997)