Re: [WebDNA] Still having problems
This WebDNA talk-list message is from 2008
It keeps the original formatting.
numero = 100187
interpreted = N
texte = 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:
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 >>> >
Christophe Billiottet
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:
Alternating colors (1997)
FW: Large File Uploads Impact WebDNA Performance (IIS) (2003)
Emailer errors - repost (2000)
Search and path arguments (1998)
UNSUBSCRIBE (2001)
creator code (1997)
WC 3.0.1 Mac days_to_date (1998)
problem with NT beta (1997)
[LOOKUP] (1997)
[SQL] - COUNT, SUM retrieval (2000)
Site Builder & IE Mac (2004)
suffix mapping for NT? (1997)
Is this google friendly? (2003)
WebCat2 several catalogs? (1997)
my SOS last week... (1996)
Showcart in [include] (1999)
Shipping by order total (2003)
Calendar Snippet Problems (1998)
FEA REQ: One .hdr, multiple .db's (2003)
OFF-TOPIC: Check www.godaddy.com for me ... (2003)