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.2The 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.=div>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.ThierryAm 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.---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list .To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.usBug Reporting: suppo=rt@webdna.usI also understood the problem appeared Saturday: "We='ve got 4 vhosts running v7 since a few weeks without problems - till y=esterday."- chrisOn 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 tothe mailing list <t=alk@webdna.us>.To unsubscribe, E-mail to: <talk-leave@webdna.us=a>>archives: http://mail.webdna.=us/list/talk@webdna.usBug 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
|
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.2The 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.=div>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.ThierryAm 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.---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list .To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.usBug Reporting: suppo=rt@webdna.usI also understood the problem appeared Saturday: "We='ve got 4 vhosts running v7 since a few weeks without problems - till y=esterday."- chrisOn 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 tothe mailing list <t=alk@webdna.us>.To unsubscribe, E-mail to: <talk-leave@webdna.us=a>>archives: http://mail.webdna.=us/list/talk@webdna.usBug 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
DOWNLOAD WEBDNA NOW!
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...