Re: [WebDNA] v7 problem?

This WebDNA talk-list message is from

2012


It keeps the original formatting.
numero = 107998
interpreted = N
texte = --001636ed67adac221904b6184398 Content-Type: text/plain; charset=ISO-8859-1 I had a recent experience with WebDNA 6.2 on Apache. I would find hundreds of httpd instances up and running with WebDNA at 99% most of the time. The sites were being run on a dedicated RedHat server with more than 8 years of continuous service. It was an old OS and an old Apache on a tired piece of equipment. The server would stop responding to incoming requests. Most of the time I could SSH to the server and reboot. I switched to a more modern Centos VPS in the last week and have seen a two-fold improvement in response time and no downtime yet. I never figured out the exact problem, but it wasn't my code or 3d party DoS from what I could tell. Likely a bad machine. One thing to consider and I know Apache has this, is to limit the number of child processes that can be started. Bill On Mon, Jan 9, 2012 at 7:33 AM, Thierry Almy wrote: > All of our sites are not "extremely" busy ... a few ones have more hits > than other that's true. > > For server 1 we had about 70'000 hits per day (hits, not visits!) during > the last two weeks, but all served with v6.2 > The ones using v7 are not heavily hit. > > Server 2 has maybe half of hits on v6.2 and only two v7 sites with almost > no hits. > The "www.maendli-freizeit.ch" vhost is in development state and has no > hits at all, as I mentioned it makes them crash also if it contains only > the WebDNA folder and nothing else. > It doesn't really matter if the v7 sites are heavily hit or not, it's the > fact that having more than a handfull of fcgi processes running at once. > > Thierry > > > Am 09.01.2012 um 13:20 schrieb christophe.billiottet@webdna.us: > > Yes, we will check this error and i will be back with informations. Could > it be that you are running extremely busy websites on a single server, the > kind of website that usually run on dedicated servers, and that one is > heavier than the others? i understand the error follows one of your > websites, www.maendli-freizeit.ch, and that the problem appears when you > add this specific website to your servers. > > I also understood the problem appeared Saturday: "*We've got 4 vhosts > running v7 since a few weeks without problems - till yesterday.*" > > - chris > > > On Jan 9, 2012, at 10:07, Thierry Almy wrote: > > Thanks Chris > > On our 2x QuadCore we can handle 2 fcgi processes, on the 2x 6-Core 4 fcgi > processes. > The next process will bring up the errors on each system. > > To be honest, it can't be a solution to set up a VPS for each web host. > We're running more than 100 vhosts, it's just impossible to do it this way > ... > > The sem_open error points to a programming problem where the application > doesn't properly close channels after usage ...as far as I understand it > ... but I'm definitely not an application programmer .... > > Thierry > > > Am 09.01.2012 um 12:19 schrieb christophe.billiottet@webdna.us: > > I will check this asap with our developer. Meanwhile, not all hosting > solutions are being equals, though the FastCGI should be able to handle > almost any UNIX/LINUX configuration. I personnally prefer the one chosen by > Ken: a single website on a VPS with a light but feature-rich linux OS like > DEBIAN associated with LIGHTTPD webserver -which is faster and lighter than > apache- and has a well-designed FastCGI implementation. This solution can > be very cheap, will run with 128MB of RAM and scales up easily with fast > processors and lots of RAM. > > The VPS is the natural extension of WebDNA 7: it gives as much control as > a dedicated server for a fraction of the cost, and makes each website an > independant entity with greater efficiency and high level of security. > > > - chris > > > > On Jan 9, 2012, at 8:39, Thierry Almy wrote: > > > Hi chris > > > sorry for the comment ... I take it back ... > > > I just want to have an environment which allows me to do my job > (programming). > > > Maybe we should leave OS X at all and move to Linux? > > > > The last error we had a few weeks ago was because of heavy load and bad > RAM. > > After changing the RAM the malloc error was gone. > > The sem_open error must have to do something with WebDNA ... v6.2 and v7 > > > Is there anybody else which has seen the sem_open error? > > > Thierry > > > > > --------------------------------------------------------- > > This message is sent to you because you are subscribed to > > the mailing list . > > To unsubscribe, E-mail to: > > archives: http://mail.webdna.us/list/talk@webdna.us > > Bug Reporting: support@webdna.us > > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us > > > --------------------------------------------------------- This message is > sent to you because you are subscribed to the mailing list **. To > unsubscribe, E-mail to: ** archives: > http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us > **** > > > --------------------------------------------------------- This message is > sent to you because you are subscribed to the mailing list **. To > unsubscribe, E-mail to: ** archives: > http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us > --001636ed67adac221904b6184398 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I had a recent experience with WebDNA 6.2 on Apache. =A0I would find hundre= ds of httpd instances up and running with WebDNA at 99% most of the time. = =A0The sites were being run on a dedicated RedHat server with more than 8 y= ears of continuous service. =A0It was an old OS and an old Apache on a tire= d piece of equipment. =A0The server would stop responding to incoming reque= sts. =A0Most of the time I could SSH to the server and reboot. =A0

I switched to a more modern Centos VPS in the last week and = have seen a two-fold improvement in response time and no downtime yet. =A0<= /div>

I never figured out the exact problem, but it wasn= 't my code or 3d party DoS from what I could tell. =A0Likely a bad mach= ine. =A0

One thing to consider and I know Apache has this, is to= limit the number of child processes that can be started. =A0
Bill

On Mon, Jan 9, 2012 at 7= :33 AM, Thierry Almy <lists@almy.ch> wrote:
All= of our sites are not "extremely" busy ... a few ones have more h= its than other that's true.

For server 1 we had about 70'000 hits per day (hits= , not visits!) during the last two weeks, but all served with v6.2
The ones using v7 are not heavily hit.

Server 2 = has maybe half of hits on v6.2 and only two v7 sites with almost no hits.
The "www.maendli-freizeit.ch" vhost is in development state and has no hits at al= l, as I mentioned it makes them crash also if it contains only the WebDNA f= older and nothing else.
It doesn't really matter if the v7 sites are heavily hit or not, i= t's the fact that having more than a handfull of fcgi processes running= at once.

Thierry


Am 09.01.2012 um 13:20 schrieb christophe.billiottet@webdna.us:

Yes, we will check this error and i will be back with informations. Could i= t be that you are running extremely busy websites on a single server, the k= ind of website that usually run on dedicated servers, and that one is heavi= er than the others? i understand the error follows one of your websites,=A0= www.maendli-f= reizeit.ch, and that the problem appears when you add this specific web= site to your servers.

I also understood the problem appeared Saturday: "We= 've got 4 vhosts running v7 since a few weeks without problems - till y= esterday."

- chris


On Jan 9, 2012, at 10:07, Thierry Almy wrote:

Thanks Chris

On our 2x QuadCore we can handle 2= fcgi processes, on the 2x 6-Core 4 fcgi processes.
The next process wi= ll bring up the errors on each system.

To be honest, it can't be a solution to set up a VPS for each web h= ost. We're running more than 100 vhosts, it's just impossible to do= it this way ...

The sem_open error points to a programming problem = where the application doesn't properly close channels after usage ...as= far as I understand it ... =A0but I'm definitely not an application pr= ogrammer ....

Thierry


Am 09.01.2012 um 12:19 schrieb christophe.billiottet@webdn= a.us:

I will check this asap with our = developer. Meanwhile, not all hosting solutions are being equals, though th= e FastCGI should be able to handle almost any UNIX/LINUX configuration. I p= ersonnally prefer the one chosen by Ken: a single website on a VPS with a l= ight but feature-rich linux OS like DEBIAN associated with LIGHTTPD webserv= er -which is faster and lighter than apache- and has a well-designed FastCG= I implementation. This solution can be very cheap, will run with 128MB of R= AM and scales up easily with fast processors and lots of RAM.
The VPS is the natural extension of = WebDNA 7: it gives as much control as a dedicated server for a fraction of = the cost, and makes each website an independant entity with greater efficie= ncy and high level of security.

- chris

<= blockquote type=3D"cite">
On Jan = 9, 2012, at 8:39, Thierry Almy wrote:

Hi chris

sorry for the comment ... I take it back ...
<= /blockquote>

I just want to have an environment which allows me to do my job (programmin= g).

Maybe we should leave OS X at all and move to Linux?


The last e= rror we had a few weeks ago was because of heavy load and bad RAM.
Af= ter changing the RAM the malloc error was gone.
The sem_open error must have to do something with WebDNA ... v6.2 and v7=

Is there anybody else which has seen the sem_open error?

<= /blockquote>
Thierry



-------------------------------------------------= --------
This message is sent to = you because you are subscribed to
the mailing list <t= alk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.= us/list/talk@webdna.us
Bug Reporting: support@webdna.us
---------------------------------------------------------
This message = is sent to you because you are subscribed to
the mailing list <ta= lk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
arch= ives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: suppo= rt@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: suppo= rt@webdna.us
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: suppo= rt@webdna.us

--001636ed67adac221904b6184398-- Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] v7 problem? (Thierry Almy 2012)
  2. Re: [WebDNA] v7 problem? (christophe.billiottet@webdna.us 2012)
  3. Re: [WebDNA] v7 problem? (christophe.billiottet@webdna.us 2012)
  4. Re: [WebDNA] v7 problem? (Paul Willis 2012)
  5. Re: [WebDNA] v7 problem? (sal danna 2012)
  6. Re: [WebDNA] v7 problem? (christophe.billiottet@webdna.us 2012)
  7. Re: [WebDNA] v7 problem? (Donovan Brooke 2012)
  8. Re: [WebDNA] v7 problem? (christophe.billiottet@webdna.us 2012)
  9. Re: [WebDNA] v7 problem? (Govinda 2012)
  10. Re: [WebDNA] v7 problem? (Thierry Almy 2012)
  11. Re: [WebDNA] v7 problem? (Kenneth Grome 2012)
  12. Re: [WebDNA] v7 problem? (christophe.billiottet@webdna.us 2012)
  13. Re: [WebDNA] v7 problem? (William DeVaul 2012)
  14. Re: [WebDNA] v7 problem? (Thierry Almy 2012)
  15. Re: [WebDNA] v7 problem? (christophe.billiottet@webdna.us 2012)
  16. Re: [WebDNA] v7 problem? (Thierry Almy 2012)
  17. Re: [WebDNA] v7 problem? (christophe.billiottet@webdna.us 2012)
  18. Re: [WebDNA] v7 problem? (Thierry Almy 2012)
  19. Re: [WebDNA] v7 problem? (Thierry Almy 2012)
  20. Re: [WebDNA] v7 problem? (christophe.billiottet@webdna.us 2012)
  21. [WebDNA] v7 problem? (Thierry Almy 2012)
--001636ed67adac221904b6184398 Content-Type: text/plain; charset=ISO-8859-1 I had a recent experience with WebDNA 6.2 on Apache. I would find hundreds of httpd instances up and running with WebDNA at 99% most of the time. The sites were being run on a dedicated RedHat server with more than 8 years of continuous service. It was an old OS and an old Apache on a tired piece of equipment. The server would stop responding to incoming requests. Most of the time I could SSH to the server and reboot. I switched to a more modern Centos VPS in the last week and have seen a two-fold improvement in response time and no downtime yet. I never figured out the exact problem, but it wasn't my code or 3d party DoS from what I could tell. Likely a bad machine. One thing to consider and I know Apache has this, is to limit the number of child processes that can be started. Bill On Mon, Jan 9, 2012 at 7:33 AM, Thierry Almy wrote: > All of our sites are not "extremely" busy ... a few ones have more hits > than other that's true. > > For server 1 we had about 70'000 hits per day (hits, not visits!) during > the last two weeks, but all served with v6.2 > The ones using v7 are not heavily hit. > > Server 2 has maybe half of hits on v6.2 and only two v7 sites with almost > no hits. > The "www.maendli-freizeit.ch" vhost is in development state and has no > hits at all, as I mentioned it makes them crash also if it contains only > the WebDNA folder and nothing else. > It doesn't really matter if the v7 sites are heavily hit or not, it's the > fact that having more than a handfull of fcgi processes running at once. > > Thierry > > > Am 09.01.2012 um 13:20 schrieb christophe.billiottet@webdna.us: > > Yes, we will check this error and i will be back with informations. Could > it be that you are running extremely busy websites on a single server, the > kind of website that usually run on dedicated servers, and that one is > heavier than the others? i understand the error follows one of your > websites, www.maendli-freizeit.ch, and that the problem appears when you > add this specific website to your servers. > > I also understood the problem appeared Saturday: "*We've got 4 vhosts > running v7 since a few weeks without problems - till yesterday.*" > > - chris > > > On Jan 9, 2012, at 10:07, Thierry Almy wrote: > > Thanks Chris > > On our 2x QuadCore we can handle 2 fcgi processes, on the 2x 6-Core 4 fcgi > processes. > The next process will bring up the errors on each system. > > To be honest, it can't be a solution to set up a VPS for each web host. > We're running more than 100 vhosts, it's just impossible to do it this way > ... > > The sem_open error points to a programming problem where the application > doesn't properly close channels after usage ...as far as I understand it > ... but I'm definitely not an application programmer .... > > Thierry > > > Am 09.01.2012 um 12:19 schrieb christophe.billiottet@webdna.us: > > I will check this asap with our developer. Meanwhile, not all hosting > solutions are being equals, though the FastCGI should be able to handle > almost any UNIX/LINUX configuration. I personnally prefer the one chosen by > Ken: a single website on a VPS with a light but feature-rich linux OS like > DEBIAN associated with LIGHTTPD webserver -which is faster and lighter than > apache- and has a well-designed FastCGI implementation. This solution can > be very cheap, will run with 128MB of RAM and scales up easily with fast > processors and lots of RAM. > > The VPS is the natural extension of WebDNA 7: it gives as much control as > a dedicated server for a fraction of the cost, and makes each website an > independant entity with greater efficiency and high level of security. > > > - chris > > > > On Jan 9, 2012, at 8:39, Thierry Almy wrote: > > > Hi chris > > > sorry for the comment ... I take it back ... > > > I just want to have an environment which allows me to do my job > (programming). > > > Maybe we should leave OS X at all and move to Linux? > > > > The last error we had a few weeks ago was because of heavy load and bad > RAM. > > After changing the RAM the malloc error was gone. > > The sem_open error must have to do something with WebDNA ... v6.2 and v7 > > > Is there anybody else which has seen the sem_open error? > > > Thierry > > > > > --------------------------------------------------------- > > This message is sent to you because you are subscribed to > > the mailing list . > > To unsubscribe, E-mail to: > > archives: http://mail.webdna.us/list/talk@webdna.us > > Bug Reporting: support@webdna.us > > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us > > > --------------------------------------------------------- This message is > sent to you because you are subscribed to the mailing list **. To > unsubscribe, E-mail to: ** archives: > http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us > **** > > > --------------------------------------------------------- This message is > sent to you because you are subscribed to the mailing list **. To > unsubscribe, E-mail to: ** archives: > http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us > --001636ed67adac221904b6184398 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I had a recent experience with WebDNA 6.2 on Apache. =A0I would find hundre= ds of httpd instances up and running with WebDNA at 99% most of the time. = =A0The sites were being run on a dedicated RedHat server with more than 8 y= ears of continuous service. =A0It was an old OS and an old Apache on a tire= d piece of equipment. =A0The server would stop responding to incoming reque= sts. =A0Most of the time I could SSH to the server and reboot. =A0

I switched to a more modern Centos VPS in the last week and = have seen a two-fold improvement in response time and no downtime yet. =A0<= /div>

I never figured out the exact problem, but it wasn= 't my code or 3d party DoS from what I could tell. =A0Likely a bad mach= ine. =A0

One thing to consider and I know Apache has this, is to= limit the number of child processes that can be started. =A0
Bill

On Mon, Jan 9, 2012 at 7= :33 AM, Thierry Almy <lists@almy.ch> wrote:
All= of our sites are not "extremely" busy ... a few ones have more h= its than other that's true.

For server 1 we had about 70'000 hits per day (hits= , not visits!) during the last two weeks, but all served with v6.2
The ones using v7 are not heavily hit.

Server 2 = has maybe half of hits on v6.2 and only two v7 sites with almost no hits.
The "www.maendli-freizeit.ch" vhost is in development state and has no hits at al= l, as I mentioned it makes them crash also if it contains only the WebDNA f= older and nothing else.
It doesn't really matter if the v7 sites are heavily hit or not, i= t's the fact that having more than a handfull of fcgi processes running= at once.

Thierry


Am 09.01.2012 um 13:20 schrieb christophe.billiottet@webdna.us:

Yes, we will check this error and i will be back with informations. Could i= t be that you are running extremely busy websites on a single server, the k= ind of website that usually run on dedicated servers, and that one is heavi= er than the others? i understand the error follows one of your websites,=A0= www.maendli-f= reizeit.ch, and that the problem appears when you add this specific web= site to your servers.

I also understood the problem appeared Saturday: "We= 've got 4 vhosts running v7 since a few weeks without problems - till y= esterday."

- chris


On Jan 9, 2012, at 10:07, Thierry Almy wrote:

Thanks Chris

On our 2x QuadCore we can handle 2= fcgi processes, on the 2x 6-Core 4 fcgi processes.
The next process wi= ll bring up the errors on each system.

To be honest, it can't be a solution to set up a VPS for each web h= ost. We're running more than 100 vhosts, it's just impossible to do= it this way ...

The sem_open error points to a programming problem = where the application doesn't properly close channels after usage ...as= far as I understand it ... =A0but I'm definitely not an application pr= ogrammer ....

Thierry


Am 09.01.2012 um 12:19 schrieb christophe.billiottet@webdn= a.us:

I will check this asap with our = developer. Meanwhile, not all hosting solutions are being equals, though th= e FastCGI should be able to handle almost any UNIX/LINUX configuration. I p= ersonnally prefer the one chosen by Ken: a single website on a VPS with a l= ight but feature-rich linux OS like DEBIAN associated with LIGHTTPD webserv= er -which is faster and lighter than apache- and has a well-designed FastCG= I implementation. This solution can be very cheap, will run with 128MB of R= AM and scales up easily with fast processors and lots of RAM.
The VPS is the natural extension of = WebDNA 7: it gives as much control as a dedicated server for a fraction of = the cost, and makes each website an independant entity with greater efficie= ncy and high level of security.

- chris

<= blockquote type=3D"cite">
On Jan = 9, 2012, at 8:39, Thierry Almy wrote:

Hi chris

sorry for the comment ... I take it back ...
<= /blockquote>

I just want to have an environment which allows me to do my job (programmin= g).

Maybe we should leave OS X at all and move to Linux?


The last e= rror we had a few weeks ago was because of heavy load and bad RAM.
Af= ter changing the RAM the malloc error was gone.
The sem_open error must have to do something with WebDNA ... v6.2 and v7=

Is there anybody else which has seen the sem_open error?

<= /blockquote>
Thierry



-------------------------------------------------= --------
This message is sent to = you because you are subscribed to
the mailing list <t= alk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.= us/list/talk@webdna.us
Bug Reporting: support@webdna.us
---------------------------------------------------------
This message = is sent to you because you are subscribed to
the mailing list <ta= lk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
arch= ives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: suppo= rt@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: suppo= rt@webdna.us
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: suppo= rt@webdna.us

--001636ed67adac221904b6184398-- William DeVaul

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:

textarea inputs and returns (1999) checking for [ and ] in form fields ... (1997) Forms Search Questions (1997) Explorer 3.0/ Access Denied! (1997) os 8.5 (1999) authnet good news (2003) Help name our technology! (1997) Validation (2000) Word search (1997) Help with Repost Data msg from form (1997) 5.0 Pricing (2003) Re(5): Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (1998) problems with 2 tags shakur (1997) WebTen and WebCat (1997) Showif, Hideif reverse logic ? (1997) version 2 for NT (1997) Clearly.home (1998) [returnraw] (2005) Tax Moratorium Expiring (2001) Converting Quotes in Javascript (2001)