Re: [WebDNA] Still having problems
This WebDNA talk-list message is from 2008
It keeps the original formatting.
numero = 100206
interpreted = N
texte = On Jul 3, 2008, at 1:09 AM, Christophe Billiottet wrote: > To all WebDNA customers with crash problems, would you be so kind to > give us those informations? > > OS.....................: Mac OS 10.4 > hardware...............: Xserve G4 Dual 1.33 ghz processors with 2 > gb ram. > hardware is X years old: 4 years old > apache version.........: 2.2 > WebDNA version.........: 6.0a > approx. size of WebDNA bases in RAM: 50 mb > RAM size...............: 2 gb > > crashes randomly.......: ? Yes > crashes every X hours..: ? Every 48 - 72 hours > > Is there a backup system? Raid Drive > Any other application running on the same box? iTools & Rumpus > UPS....................: ? (battery reset every X hours might crash > a server if the battery is dead) New Battery 4 months ago > > 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:
On Jul 3, 2008, at 1:09 AM, Christophe Billiottet wrote: > To all WebDNA customers with crash problems, would you be so kind to > give us those informations? > > OS.....................: Mac OS 10.4 > hardware...............: Xserve G4 Dual 1.33 ghz processors with 2 > gb ram. > hardware is X years old: 4 years old > apache version.........: 2.2 > WebDNA version.........: 6.0a > approx. size of WebDNA bases in RAM: 50 mb > RAM size...............: 2 gb > > crashes randomly.......: ? Yes > crashes every X hours..: ? Every 48 - 72 hours > > Is there a backup system? Raid Drive > Any other application running on the same box? iTools & Rumpus > UPS....................: ? (battery reset every X hours might crash > a server if the battery is dead) New Battery 4 months ago > > 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 >>>> >> > > >
Tennis De Jong
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:
How can I record purchases to a database? (1998)
trouble updating records in database (1998)
XML values to database records (grep?) (2000)
[WebDNA] Which linux distros for webdna? (2008)
test (2000)
Running 2 two WebCatalog.acgi's (1996)
Renumbering Database Records (1999)
OK, here goes... (1997)
Practice runs ? (1997)
[HTML*] (a proposition) (1997)
Re:Emailer tracking (1997)
Error: Too many nested [xxx] contexts (1997)
Uh...can someone help me out with the b10? (1997)
WebCommerce: Folder organization ? (1997)
Memory Error message (1998)
Need help with emailer- 2 issues (1997)
Configuring E-mail (1997)
Plugin or CGI or both (1997)
Dummy Credit Card Number for debug? (1997)
TCPConnect and AuthorizeNet (2001)