pub crawler | 1 Sep 01:23 2009
Picon

Re: FW: Cannot start Cherokee 0.99.23

Fire extinguisher please!

What a roar we have on this thread.

Come on let's fix this issue somehow for Ray... Tone aside....

Once you go with the apt-get Ubuntu install can you safely revert to
future upgrades via the Unix installation way as laid out in the
Cookbook? Or does this create other complications?

If someone is using the Ubuntu easy install method should they apt-get
remove Cherokee first then proceed with the manual install process?
pub crawler | 1 Sep 01:45 2009
Picon

Re: Cherokee wish list discussion - CACHING

The ability to reload cache from disk is major point to consider.
There are many instances where a configuration change might have
someone hard starting Cherokee several times - thus running with no
cache for extended time should we not have a reloadable disk cache.
Usually cold starts after crashes or extended outages are the most
painful and thus Cherokee could become a good tool for many to avoid
these troubled times :)

Unsure how the reads/writes to disk will overall perform. Seems like
this Varnish does this - preallocates a single file at set amount of
memory then reads and writes as it needs to. The startup time when
spawning it fresh is unnoticeable on our gear and the pure throughput
from Varnish immediately is very high. (Wish memcached would get on
board with a similar to-disk feature).

I'd be very interested in getting this new Cherokee cache accessible
in some other abstract usable ways - like as a filesystem. It's still
unclear how the cache will be tied-in and what access will be
available. If it is like the current IO Cache in Cherokee - it will be
transparent. Is this the idea?   I would wish for more accessible
feature - where we can fetch data on-demand from other apps - not just
Cherokee per se.

Finally, getting this new cache mechanism to transparently cache set
item types from Reverse Proxy (like .gif, .jpg, etc. - static files -
user defined) is the big powerful feature for us - should it be
doable. Is that part of the cache strategy at this point?

-Paul
(Continue reading)

pub crawler | 1 Sep 02:13 2009
Picon

Reverse Proxy 503 error...

I've held off on this post all day - but time to inquire...

When I got up early this AM found our Cherokee server sending out 503
error message to users....Every page.

Checked the servers behind Cherokee by accessing them via internal
IPs... everything was fine (for a change).

I hard started Cherokee and ran into other per se unrelated issues.

Has anyone seen any funkiness with 503 errors and reverse proxy in
recent trunk releases?

What are the rest of you doing or recommend to balance multiple
Cherokee front ends to avoid such an outage due to a misbehaving
Cherokee?

-Paul
Jorge Sarmiento | 1 Sep 10:14 2009
Picon

Re: strange logs in cherokee error log

I am using Cherokee, sorry for the terrible mistake while writing.

This issue has ocurred 3 times in 2 different servers, both with
CentOS 5.3 x64 minimal installation with almost all services down,
everything was installed from CentOS official repositories (except a
couple of libraries from rpmforge) and Cherokee was compiled from
trunk.

problem is: after php-fcgi crashes (for some strange reason) memory
usage jumps and processor usage raises to almost 100%.
Today I fixed it by restarting MySQL and cherokee services (after
about 15 minutes for server to respond).

any ideas on how to debug this or where to start checking for the problem?

thanks for your time,

Jorge S.

On Mon, Aug 31, 2009 at 1:53 PM, pub crawler<pubcrawler.com <at> gmail.com> wrote:
> Jorge,
>
> Your issue is with PHP and Apache correct? How about using Cherokee
> instead of Apache :) ?
>
> Is this a reoccurring issue - and how long does it take for this
> amount of RAM to be consumed?
>
> -Paul
>
(Continue reading)

Oleg Oltar | 1 Sep 10:16 2009
Picon

I can't start the server

Hi!

Today I tried to do a redirect, for one of my servers (I needed to redirect every request which is made to / to the /home/ url), but didn't managed to do it.

After I tried to save regular expression rule (/ to /home/) the server couldn't be lunched anymore

I get an error when trying to start it

Could not launch the server

Something happened while launching the server. The error reported by the server follows:

[01/08/2009 11:13:19.323] (critical) gen_evhost.c:120 - ERROR: EvHost needs a 'tpl_document_root property'

Could you please suggest a way how to fix it, and how to add a redirect?

Thanks,
Oleg
_______________________________________________
Cherokee mailing list
Cherokee <at> lists.octality.com
http://lists.octality.com/listinfo/cherokee
Oleg Oltar | 1 Sep 10:18 2009
Picon

Re: I can't start the server

Sorry, now I see it's my error (I turned on Advance virtual hosting, but didn't configure it)

Anyway looking how to set up the redirect now

On Tue, Sep 1, 2009 at 11:16 AM, Oleg Oltar <oltarasenko <at> gmail.com> wrote:
Hi!

Today I tried to do a redirect, for one of my servers (I needed to redirect every request which is made to / to the /home/ url), but didn't managed to do it.

After I tried to save regular expression rule (/ to /home/) the server couldn't be lunched anymore

I get an error when trying to start it

Could not launch the server

Something happened while launching the server. The error reported by the server follows:

[01/08/2009 11:13:19.323] (critical) gen_evhost.c:120 - ERROR: EvHost needs a 'tpl_document_root property'

Could you please suggest a way how to fix it, and how to add a redirect?

Thanks,
Oleg

_______________________________________________
Cherokee mailing list
Cherokee <at> lists.octality.com
http://lists.octality.com/listinfo/cherokee
Alejandro Barrera | 1 Sep 10:20 2009

Re: strange logs in cherokee error log

On Tuesday 01 September 2009 10:14:53 Jorge Sarmiento wrote:
> problem is: after php-fcgi crashes (for some strange reason) memory
> usage jumps and processor usage raises to almost 100%.
> Today I fixed it by restarting MySQL and cherokee services (after
> about 15 minutes for server to respond).

What version on php-fcgi are you using? What version of Cherokee are you 
using?

I experienced similar problems and it was a conjunction of a faulty php-cgi 
and an old version of cherokee. 

--

-- 
http://www.neurosecurity.com

"We must be the change we wish to see in the world"
Mahatma Gandhi
Jorge Sarmiento | 1 Sep 10:24 2009
Picon

Re: strange logs in cherokee error log

Version are:

php-5.1.6-23.2.el5_3 (CentOS 5.3 latest package)

cherokee-0.99.22

Jorge S.

On Tue, Sep 1, 2009 at 3:20 AM, Alejandro
Barrera<abarrera <at> neurosecurity.com> wrote:
> On Tuesday 01 September 2009 10:14:53 Jorge Sarmiento wrote:
>> problem is: after php-fcgi crashes (for some strange reason) memory
>> usage jumps and processor usage raises to almost 100%.
>> Today I fixed it by restarting MySQL and cherokee services (after
>> about 15 minutes for server to respond).
>
> What version on php-fcgi are you using? What version of Cherokee are you
> using?
>
> I experienced similar problems and it was a conjunction of a faulty php-cgi
> and an old version of cherokee.
>
> --
> http://www.neurosecurity.com
>
> "We must be the change we wish to see in the world"
> Mahatma Gandhi
>
Alejandro Barrera | 1 Sep 10:37 2009

Re: strange logs in cherokee error log

On Tuesday 01 September 2009 10:24:47 Jorge Sarmiento wrote:
> php-5.1.6-23.2.el5_3 (CentOS 5.3 latest package)

I know it's a pain in the ass but, could you try a newer php version? They're 
on the 5.2.10. Try if you can a different version, maybe in the 5.1.x range but 
x > 6. Can't remember which version I had gave me problems, but it might go 
away with a newer one. I'm currently using 5.2.10 myself and it's not giving 
me any problems.

--

-- 
http://www.neurosecurity.com

"We must be the change we wish to see in the world"
Mahatma Gandhi
Alvaro Lopez Ortega | 1 Sep 10:40 2009

Re: strange logs in cherokee error log

On 01-sep-09, at 10:24, Jorge Sarmiento wrote:

> Version are:
>
> php-5.1.6-23.2.el5_3 (CentOS 5.3 latest package)
> cherokee-0.99.22

Cherokee 0.99.23 was shipped with a number of improvements in the  
spawning mechanism. That something that would most probably help here.  
However, it won't fix the source of the problem (some hoggy process  
eating all your server memory).

BTW, I'm releasing Cherokee 0.99.24 within the next few hours. If  
you're thinking of updating, just bare for the new version.

Cheers!

--
Octality
http://www.octality.com/

Gmane