Re: [WebDNA] v7 problem?
This WebDNA talk-list message is from 2012
It keeps the original formatting.
numero = 107996
interpreted = N
texte = --Apple-Mail-4--87922306Content-Transfer-Encoding: quoted-printableContent-Type: text/plain;charset=us-asciiYes, 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."- chrisOn Jan 9, 2012, at 10:07, Thierry Almy wrote:> Thanks Chris>=20> On our 2x QuadCore we can handle 2 fcgi processes, on the 2x 6-Core 4 =fcgi processes.=20> The next process will bring up the errors on each system.>=20> 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 ...>=20> 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 ....=20=>=20> Thierry>=20>=20> Am 09.01.2012 um 12:19 schrieb christophe.billiottet@webdna.us:>=20>> 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.>>=20>> - chris>>=20>>=20>> On Jan 9, 2012, at 8:39, Thierry Almy wrote:>>=20>>> Hi chris>>>=20>>> sorry for the comment ... I take it back ...>>>=20>>> I just want to have an environment which allows me to do my job =(programming).>>>=20>>> Maybe we should leave OS X at all and move to Linux?>>>=20>>>=20>>> 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>>>=20>>> Is there anybody else which has seen the sem_open error?>>>=20>>> Thierry>>=20>>=20>>=20>> --------------------------------------------------------->> 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>=20> ---------------------------------------------------------> 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--Apple-Mail-4--87922306Content-Transfer-Encoding: quoted-printableContent-Type: text/html;charset=us-asciiYes, =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@webd=na.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 <talk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/l=ist/talk@webdna.us
Bug =Reporting: support@webdna.us
---------------------------------------------------------
This =message is sent to you because you are subscribed to
the mailing list =<talk@webdna.us>.
To =unsubscribe, E-mail to: <talk-leave@webdna.us>
archi=ves: http://mail.webdna.us/l=ist/talk@webdna.us
Bug Reporting: support@webdna.us
=--Apple-Mail-4--87922306--
Associated Messages, from the most recent to the oldest:
--Apple-Mail-4--87922306Content-Transfer-Encoding: quoted-printableContent-Type: text/plain;charset=us-asciiYes, 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."- chrisOn Jan 9, 2012, at 10:07, Thierry Almy wrote:> Thanks Chris>=20> On our 2x QuadCore we can handle 2 fcgi processes, on the 2x 6-Core 4 =fcgi processes.=20> The next process will bring up the errors on each system.>=20> 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 ...>=20> 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 ....=20=>=20> Thierry>=20>=20> Am 09.01.2012 um 12:19 schrieb christophe.billiottet@webdna.us:>=20>> 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.>>=20>> - chris>>=20>>=20>> On Jan 9, 2012, at 8:39, Thierry Almy wrote:>>=20>>> Hi chris>>>=20>>> sorry for the comment ... I take it back ...>>>=20>>> I just want to have an environment which allows me to do my job =(programming).>>>=20>>> Maybe we should leave OS X at all and move to Linux?>>>=20>>>=20>>> 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>>>=20>>> Is there anybody else which has seen the sem_open error?>>>=20>>> Thierry>>=20>>=20>>=20>> --------------------------------------------------------->> 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>=20> ---------------------------------------------------------> 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--Apple-Mail-4--87922306Content-Transfer-Encoding: quoted-printableContent-Type: text/html;charset=us-asciiYes, =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@webd=na.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 <talk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/l=ist/talk@webdna.us
Bug =Reporting: support@webdna.us
---------------------------------------------------------
This =message is sent to you because you are subscribed to
the mailing list =<talk@webdna.us>.
To =unsubscribe, E-mail to: <talk-leave@webdna.us>
archi=ves: http://mail.webdna.us/l=ist/talk@webdna.us
Bug Reporting: support@webdna.us
=--Apple-Mail-4--87922306--
christophe.billiottet@webdna.us
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:
Setting up shop (1997)
WebCat2final1 crashes (1997)
Bug Report, maybe (1997)
Bug Report, maybe (1997)
using showpage and showcart commands (1996)
Errata: WCS Newbie question (1997)
Credit Card not accepted (1998)
CMS - Formatting Content (2004)
quotation marks (2004)
[WebDNA] Paypal Sandbox TCPConnect (2012)
[WebDNA] Uploading Specific File Types (2009)
carriage returns in data (1997)
WebCatalog2 Feature Feedback (1996)
Bug Report, maybe (1997)
Document Contains No Data! (1997)
WebCatalog-NT?'s (1996)
WebCatalog2 Feature Feedback (1996)
RE: [WebDNA] Ubuntu 14.04 & WebDNA (2017)
Multiple Pulldowns/Gary (1997)
[WebDNA] WebDNA Roll Call (2013)