headers
Daniel Lo Nigro | 1 Dec 2011 08:51
Favicon

Interesting post on Cherokee performance

Interesting post I came across today: http://forum.gwan.com/index.php?p=/discussion/182/cherokee-webserver-the-fastest-really

Thoughts? Has anyone on this list used Cherokee in an environment with a large number of concurrent clients?

 - Daniel
_______________________________________________
Cherokee mailing list
Cherokee <at> lists.octality.com
http://lists.octality.com/listinfo/cherokee
Permalink | Reply | 0 comments |
headers
wolfram podien | 1 Dec 2011 09:49
Picon
Picon

(no subject)

Hello,
I want to put cherokee to friendly arm - an embedded linux system with an arm processor.
I succeeded in compiling but although I forced a static build with --enable-static-module=all and
-enable-shared=no there is an error when I start cherokee admin - libssl.so cannot open shared object.
I found that I put in the disable-tls option, but it is not working - a warning is given at configure time.
I tried to compile openssl, but I failed. I got only libssl.a - a static version;-)
So what could I do?
I would prefer to build cherokee without openssl;-)
many thanks in advance;-) 
--

-- 
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
Permalink | Reply | 2 comments |
headers
Daniel Lo Nigro | 1 Dec 2011 23:40
Favicon

Re: (no subject)

Is it only cherokee-admin that throws the error? Does Cherokee itself work if you copy a working good configuration file? 


Perhaps see if there's a --disable-ssl or --disable-openssl configuration option.

On Thu, Dec 1, 2011 at 7:49 PM, wolfram podien <gogo57 <at> gmx.de> wrote:
Hello,
I want to put cherokee to friendly arm - an embedded linux system with an arm processor.
I succeeded in compiling but although I forced a static build with --enable-static-module=all and -enable-shared=no there is an error when I start cherokee admin - libssl.so cannot open shared object.
I found that I put in the disable-tls option, but it is not working - a warning is given at configure time.
I tried to compile openssl, but I failed. I got only libssl.a - a static version;-)
So what could I do?
I would prefer to build cherokee without openssl;-)
many thanks in advance;-)
--
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
_______________________________________________
Cherokee mailing list
Cherokee <at> lists.octality.com
http://lists.octality.com/listinfo/cherokee
 

_______________________________________________
Cherokee mailing list
Cherokee <at> lists.octality.com
http://lists.octality.com/listinfo/cherokee
Permalink | Reply | 0 comments |
headers
Bertrand FRUCHET | 2 Dec 2011 02:18
Picon

PHP in subdir don't working

Hi,
I installed cherokee 1.0.8 on debian squeeze 6 kernel 2.6.32-4 by debian 
packages
PHP works well if it is on website root directory
But in a subdir, PHP files are not execute but my browser wants to 
download them.
Any idea ?

----
Bert
Permalink | Reply | 2 comments |
headers
Stefan de Konink | 2 Dec 2011 02:26
Picon
Gravatar

Re: PHP in subdir don't working

On Fri, 2 Dec 2011, Bertrand FRUCHET wrote:

> Any idea ?

You have not set PHP [Non-Final]

Or you have setup a Directory Match, and you should disable in the PHP 
rule: check file.

Stefan
Permalink | Reply | 1 comment |
headers
Bertrand FRUCHET | 2 Dec 2011 10:04
Picon

Re: PHP in subdir don't working

It was the PHP rule : check file. I disable and it's work fine.
thanks a lot.
Bert

Le 02/12/2011 02:26, Stefan de Konink a écrit :
> On Fri, 2 Dec 2011, Bertrand FRUCHET wrote:
>
>> Any idea ?
>
> You have not set PHP [Non-Final]
>
> Or you have setup a Directory Match, and you should disable in the PHP 
> rule: check file.
>
>
> Stefan
Permalink | Reply | 0 comments |
headers
Daniel Lo Nigro | 2 Dec 2011 14:11
Favicon

HTTP Status rule causing "undefined symbol: cherokee_socket_set_client"

I set the handler for a directory to "HTTP Status" to return a 403 error. Now my Cherokee server won't start due to the following:

=====
[02/12/2011 23:11:20.614] (error) plugin_loader.c:199 - Something just happened
    while opening a plug-in file | The operating system reported
    '/usr/lib/libcherokee-client.so.0: undefined symbol:
    cherokee_socket_set_client' while trying to load '/usr/lib/cherokee/libplugin_custom_error.so'.

[02/12/2011 23:11:20.614] (error) plugin_loader.c:367 - Could not open the
    'custom_error' module | Either you are trying to use an unavailable
    (uninstalled?) plugin, or there is a installation issue.

Couldn't read the config file: /etc/cherokee/cherokee.conf
=====

I needed to remove the following lines in order to get it to start again:
vserver!10!rule!360!handler = custom_error
vserver!10!rule!360!handler!error = 403
vserver!10!rule!360!match = directory
vserver!10!rule!360!match!directory = /MvcTest

Any ideas how to resolve this? I'm using the Cherokee packages from Debian Unstable
_______________________________________________
Cherokee mailing list
Cherokee <at> lists.octality.com
http://lists.octality.com/listinfo/cherokee
Permalink | Reply | 0 comments |
headers
Matt Austin | 6 Dec 2011 12:15
Picon
Favicon
Gravatar

Front-line cache: lynx and ab long response time

I recently set up front-line cache for a uwsgi application in Cherokee
1.2.101 on Ubuntu 10.04.3 i686.

It has done wonders for the CPU usage on the server, and it is now
able to handle a lot more traffic. Fantastic!

However, when accessed with certain tools (lynx, ab) it takes ~60
seconds before the response is completed.
We use the pingdom.com monitoring service, and it also reports timeouts.

However accessing in my desktop browser or using wget response time is
as expected.

Any ideas - have I missed some configuration?

Thanks,

--

-- 
Matt
Permalink | Reply | 4 comments |
headers
Mehmet Ali Sahin | 6 Dec 2011 13:17
Picon

Re: Front-line cache: lynx and ab long response time

2011/12/6 Matt Austin <mail <at> mattaustin.me.uk>
>
> I recently set up front-line cache for a uwsgi application in Cherokee
> 1.2.101 on Ubuntu 10.04.3 i686.
>
> It has done wonders for the CPU usage on the server, and it is now
> able to handle a lot more traffic. Fantastic!
>
> However, when accessed with certain tools (lynx, ab) it takes ~60
> seconds before the response is completed.
> We use the pingdom.com monitoring service, and it also reports timeouts.
>
> However accessing in my desktop browser or using wget response time is
> as expected.
>
> Any ideas - have I missed some configuration?
>
>
> Thanks,
>
> --
> Matt
> _______________________________________________
> Cherokee mailing list
> Cherokee <at> lists.octality.com
> http://lists.octality.com/listinfo/cherokee

Could you try with ab -k (Keep-Alive)
Permalink | Reply | 3 comments |
headers
Matt Austin | 6 Dec 2011 15:11
Picon
Favicon
Gravatar

Re: Front-line cache: lynx and ab long response time

On Tue, Dec 6, 2011 at 20:17, Mehmet Ali Sahin <mehmetalisahin <at> gmail.com> wrote:
> Could you try with ab -k (Keep-Alive)

Great, that did the trick - thanks! So my next question is, why is
this needed? Can I disable this requirement, or will that result in a
performance drop?

I'd like to be able to continue using the Pingdom monitoring service
if possible, but if not then the benefits of front-line cache win.
Permalink | Reply | 2 comments |

Gmane