Re: Apache 2.0.54(Worker) installation on RHES not working(Zombie processes on startup)
Quoting [EMAIL PROTECTED]: I am using Apache 2.0.54 on RHEL3u5 with no problems. It's working as a reverse-proxy with mod_disk_cache. I did have problems with RHEL3u5's Apache2 package, though. Caching did not work (and yes, DSOs were loaded), so I had to install from sources. I can't remember now, but I think RHEL3u5 comes with Apache 2.0.46 + security patches up to 2.0.53. That's the version I was having problems with. Hi, I am trying to install Apache 2.0.54 on RedHat enterprise edition, though the Installation is a succes, starting of Apache results in lots of zombie processes with no active process. Machine Information: uname -a Linux ex07 2.4.21-37.EL #1 Wed Sep 7 13:35:21 EDT 2005 i686 i686 i386 GNU/Linux more /etc/issue Red Hat Enterprise Linux AS release 3 (Taro Update 6) gcc -v gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-20) Installation steps: a) ./configure \ --prefix=/home/shiva/apache2 \ --with-mpm=worker \ --enable-modules=most \ --enable-mods-shared=all b) make c) make install Install is a success. on starting the server using apachectl I was able to compile and execute the same with success of sun solaris Is there some [EMAIL PROTECTED] logs]$ ../bin/apachectl start [EMAIL PROTECTED] logs]$ ps -aef | grep httpd shiva 8016 1 0 11:01 ?00:00:00 /home/shiva/apache2/bin/httpd -k start shiva 8017 8016 0 11:01 ?00:00:00 /home/shiva/apache2/bin/httpd -k start shiva 8018 8016 0 11:01 ?00:00:00 /home/shiva/apache2/bin/httpd -k start shiva 8019 8018 0 11:01 ?00:00:00 /home/shiva/apache2/bin/httpd -k start shiva 8020 8016 0 11:01 ?00:00:00 /home/shiva/apache2/bin/httpd -k start shiva 8021 8020 0 11:01 ?00:00:00 /home/shiva/apache2/bin/httpd -k start shiva 8023 8021 0 11:01 ?00:00:00 /home/shiva/apache2/bin/httpd -k start I was able to compile and execute the same with success of sun solaris. But in case of RedHatES all the processes die. Is there some installation step/param which is incorrect or not mentioned? Any kind of clue would be of great help to me. Thanks in advance. shiva Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments.
Re: using proxy/cache for apache mirrors
Quoting Colm MacCarthaigh <[EMAIL PROTECTED]>: * It defeats a huge part of the point of having a mirroring system in the first place. Mirroring isn't just a way of decreasing bandwidth usage on the primary, it's also a means of building content resilience. When www.apache.org goes down, users want their mirror to work. And worst of all, in the case of infrequently used mirrors, this is exactly when they'll suddenly get a lot of queries - all of which will end up in IOWAIT land, with a boat-load of back-end TCP connections, and no content served. That really sucks, for both them and their users. A few months ago I developed a patch for 2.0.54 that added a new directive (CacheGatewayUnreachable) for this not to happen. When CacheGatewayUnreachable was set to true, Apache would show the latest cached version of the resource when the gateway is unreachable. When CacheGatewayUnreachable was set to false, Apache would show the same error it currently shows. I have not tested/ported it to 2.2.0, though. If I find some time, I will.
Re: [VOTE] 2.1.10 as GA
Quoting Rich Bowen <[EMAIL PROTECTED]>: I am not an Apache developer, but I think nobody said anything about caching and I am having problems using 2.1.10 as a caching proxy. I took a configuration that is working fine on 2.0 (serving a million pages/hour) and slightly modified it (removed CacheGcInterval and CacheSize) and now it is not caching at all. An apachectl configtest returns OK and the same configuration works fine on 2.0.54 and 2.0.55. I will be performing further testing on the next days. Maybe it's my configuration. Maybe not. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Joe Orton wrote: On Sat, Nov 19, 2005 at 05:17:42PM -0800, Paul Querna wrote: Tarballs available from: http://people.apache.org/~pquerna/dev/httpd-2.1.10/ Please test and vote on releasing 2.1.10 as STABLE/General Availability. +1 tested on MacOSX (very little load, to be fair), on SuSE 9.1 Linux and on Slackware something or other. - -- Rich Bowen [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDi1tzXP03+sx4yJMRAmevAKCmU2TqJPLtySQ5HWz1WlG9Tb1MeACeOFZj zSkvw18FXPlmfJhS+e+OWIo= =zajj -END PGP SIGNATURE-
