Thanks Alvaro For question one, your answer cannot be the case. I always check up the other sources and there are are still up and working. Maybe I described the situation wrongly. I have two sources for each domain/ Vhost, each source runs on a separate port
Question 2 Indeed, I am using the latest in the Ubuntu repository, very practicable, all I have to do is issue an update using the package manager. Should I do this manually in the future? Thanks On May 12, 3:02 pm, Alvaro Lopez Ortega <[email protected]> wrote: > On Sat, May 7, 2011 at 3:13 PM, Voltron <[email protected]> wrote: > > Question one: Failed source handling > > > I have 3 Vhosts, each with 2 Python backend sources for load > > balancing. I noticed that when 1 source misbehaves, and Cherokee emits > > errors like this: > > > {'type': "warning", 'time': "27/04/2011 09:16:47.358", 'title': > > "Sources exhausted: re-enabling one.", 'code': "balancer_round_robin.c: > > 122", 'error': "64", 'description': "All the Information Sources have > > been off-lined. .... > > > It takes the whole server down, which is terrible. Every source lives > > in its own environment, why should 1 take down 3 domains, the default > > host and 5 other innocent sources? > > > How can I configure Cherokee to continue to "live" even though a > > source is misbehaving? > > That's what Cherokee does by default. > > In this case the problem does not seem to be the one you described, > actually. Instead, it seems that _all_ the sources are misbehaving, and > that's why the server ends up emitting the "All the Information Sources > have been off-lined." error. -- Anyway, when that happens, Cherokee > re-activates a source, just in case it's working again. > > Question two: Cherokee admin > > > > > I noticed, for several versions back now, that Cherokee-Admin does not > > consequently detect when Cherokee is up or down. It is very bothersome > > that Upstart on Ubuntu 10.04 64 bit brings Cherokee automatically back > > on and the status is not detected by the admin. I make my changes, try > > to restart and get errors that another server is using port 80. I have > > to stop Cherokke admin, kill the newly started Cherokee worker > > process, restart Cherokee-Admin just to save my changes and restart. > > > Is there a way to set the status polling to a higher value in Cherokee- > > Admin? > > Looks like a bug that was fixed a few months ago. What version of Cherokee > are you using? In you mail you said the "latest" although that could mean > "the latest in Ubuntu" or the actual latest. > > > Question 3: Wildcard matching > > > I would like to match a domain like this "http://mydomain.com"; or > > "www.mydomain.com". I put "*.mydomain.com" as the wildcard value, this > > works but does not match "http://mydomain.com";. > > Indeed. That's what it must do. > <whatever>.mydomain.com -- Mind the first dot. > > Even though it isn't perfect, the easiest way to do it is to use: * > mydomain.com > > -- > Greetings, alohttp://www.octality.com/ > > _______________________________________________ > Cherokee mailing list > [email protected]http://lists.octality.com/listinfo/cherokee _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
