-------- Original Message --------
Subject: Re: [Cherokee] cherokee crashes on slowloris https check?
From: Gunnar Wolf <[email protected]>
To: Michiel van Es <[email protected]>
Date: 07/07/2009 03:57 PM

> Michiel van Es dijo [Tue, Jul 07, 2009 at 03:16:40PM +0200]:
>>> Michiel van Es wrote:
>>>> Hi,
>>>> I am running slowloris against my cherokee SSL website and could not
>>>> connect to my https website anymore.
>>>> Logfile shows:
>>>> Jul  7 14:22:59 pcintelw01 cherokee-worker: *** glibc detected ***
>>>> /usr/local/sbin/cherokee-worker: double free or co
>>>> rruption (!prev): 0xabcec248 ***
> 
> Which version of Cherokee are you running, Ubuntu's provided or the
> latest (via Leonel's PPA)?

No I use the source:

Cherokee Web Server 0.99.21 (Jul  2 2009): Listening on ports
80.79.194.24:80,
80.79.194.24:443(TLS), 80.79.194.25:443(TLS), 80.79.194.25:80, with TLS

support via libssl, IPv6 enabled, using epoll, 2048 fds system limit,
max.
1016 connections, caching I/O, 20 threads, 50 connections per thread,

> 
>>>> Is it a small bug in cherokee or something else?
>>> Pretty please do! You could help us even more by doing the following:
>>>
>>> Compile cherokee with -g (that is the default option). 
>> So if it is default I don't have to recompile cherokee right?
> 
> Your Cherokee is built with the following flags:
> ./configure  --host=$(DEB_HOST_GNU_TYPE)           \
>                             --build=$(DEB_BUILD_GNU_TYPE)  \
>                             --enable-os-string="Debian GNU/Linux"  \
>                             --enable-pthreads  \
>                             --prefix=/usr  \
>                             --localstatedir=/var  \
>                             --mandir=\$${prefix}/share/man  \
>                             --infodir=\$${prefix}/share/info  \
>                             --sysconfdir=/etc  \
>                             --docdir=/usr/share/doc/cherokee-doc  \
>                             --with-wwwroot=/var/www  \
>                             --with-included-gettext
> 
> We are not explicitly unsetting -g (I am just quoting this so that the
> developers can assert it does not clash with anything we specify), so
> you won't have to recompile. Even if you did, I can provide
> custom-built packates for you if you so need.
> 
>> I don't have to start cherokee from within the init script? Just above
>> commands?
> 
> Starting from the init script is roughly equivalent to running 
> /usr/sbin/cherokee; it specifies some extra invocation options (via
> start-stop-daemon) to aid the init system (i.e. setting pidfiles,
> reporting results)
> 
> 
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee

Reply via email to