Glad to know you had problems in the past with balancer feature in Cherokee. Sometimes I feel like I am the Cherokee reverse proxy power user around here :)
I actually saw some output from Cherokee: NOTICE: Taking source='192.168.13.243:8500' back on-line NOTICE: Taking source='192.168.13.243:8500' off-line NOTICE: Sources exhausted: re-enabling one. NOTICE: Taking source='172.24.96.243:8500' back on-line NOTICE: Taking source='172.24.96.243:8500' off-line NOTICE: Sources exhausted: re-enabling one. NOTICE: Taking source='192.168.13.243:8500' back on-line NOTICE: Taking source='192.168.13.243:8500' off-line NOTICE: Sources exhausted: re-enabling one. NOTICE: Taking source='172.24.96.243:8500' back on-line NOTICE: Taking source='192.168.13.243:8500' back on-line There were more of these... but obviously no time data stamp - so unsure when these are really occurring. Really need output in future with time/date info on output to console like this. These were after a few hours of running output to console. I belive but can't easily confirm that these are when garbage collection in Java runs on our app server. Unsure why Cherokee would react when that happens though. Haven't noticed the dreaded 503 error from Cherokee - but I suspect it's coming in the next 5 hours or so.. seems to be 12 hours or beyond of things running.... On Thu, Sep 3, 2009 at 4:20 PM, Stefan de Konink<[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > pub crawler schreef: >> Alright, output to console looks like this (I think) - for others >> needing to know such and future reference: >> /usr/sbin/cherokee-worker -C /etc/cherokee/cherokee.conf >> >> (I've ommitted the -d we run to detach from console typically) >> >> Would it be possible to pipe the output that then might occur by >> Cherokee to a file? Like this: >> /usr/sbin/cherokee-worker -C /etc/cherokee/cherokee.conf > >> /tmp/cherokeeoutput.txt >> >> Not sure if any of this console output will matter - as I've never >> seen Cherokee output anything other than startup info when attached to >> console. >> >> Feel free to correct me if I am wrong and recommend anything else. > > You can even make me happy with the normal cherokee binary. But please > save the log. It might be a regression in the handling of offline/online > hosts. > > Although I have to admit that I never got the general balancer (the > grandfather of the reverse proxy) to work for exact the same reason; > sometimes it behaves bad. Maybe we need to make some testing setup... > > > > Stefan > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.11 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEAREKAAYFAkqgJSEACgkQYH1+F2Rqwn3CBwCfeBmUcedJvXkWGlHZSeWImBRJ > iQwAnizHJc8IY0r9OE9zGkWQClYq+xm8 > =BrrH > -----END PGP SIGNATURE----- > _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
