SERVER CRASHED! VHM/Apache2 Arrrgghh!!!
Help! Second day server's been down!! I tried to upgrade from apache 1.3.3 to 2.2.3 and now nothing works. Can't remember or find anything I changed on the old apache but that won't come up either. The problem is in proxying. I use VHM. I had to comment out the following lines in order to get Apache2 to come up: # Reverse proxy params CacheRoot "/tmp/proxy/shop.2012.vi" # CacheSize 100000 # CacheGcInterval 2 # CacheLastModifiedFactor 0.1 # CacheDefaultExpire 1 # CacheDirLength 2 Of course, then nothing in Zope works, because it's all based on VHM! I've been googling my brains out with no luck! Did the cache rules get rewritten in Apache2? Is there new syntax I should use? Here's my configure command: ./configure --enable-so --enable-expires --enable-vqadmin --enable-speling --enable-rewrite --enable-cache --enable-deflate --enable-disk-cache --enable-mime-magic --enable-mods-shared="proxy proxy_http proxy_ftp proxy_connect headers" Please help. This is my FOURTH POST, second to Zope, and NOBODY has responded to the first three!!!!! TIA, beno
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 4 Aug 2006, at 08:09, beno wrote:
Please help. This is my FOURTH POST, second to Zope, and NOBODY has responded to the first three!!!!!
Maybe because your post is *off topic* because it has nothing at all to do with Zope? Please take this to a Apache list or a BSD list where it belongs. jens -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFE0znpRAx5nvEhZLIRAjqIAJ4po17oIwTE9/84bTsjYAADc3t0pgCfUegg 36/fDPbyL1MBbTYgAjkpRNY= =6gwB -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 beno wrote:
Help! Second day server's been down!! I tried to upgrade from apache 1.3.3 to 2.2.3 and now nothing works. Can't remember or find anything I changed on the old apache but that won't come up either. The problem is in proxying. I use VHM. I had to comment out the following lines in order to get Apache2 to come up:
# Reverse proxy params CacheRoot "/tmp/proxy/shop.2012.vi" # CacheSize 100000 # CacheGcInterval 2 # CacheLastModifiedFactor 0.1 # CacheDefaultExpire 1 # CacheDirLength 2
Of course, then nothing in Zope works, because it's all based on VHM! I've been googling my brains out with no luck! Did the cache rules get rewritten in Apache2? Is there new syntax I should use? Here's my configure command:
./configure --enable-so --enable-expires --enable-vqadmin --enable-speling --enable-rewrite --enable-cache --enable-deflate --enable-disk-cache --enable-mime-magic --enable-mods-shared="proxy proxy_http proxy_ftp proxy_connect headers"
Please help. This is my FOURTH POST, second to Zope, and NOBODY has responded to the first three!!!!!
Perhaps your question is not phrased in such a way that anybody on this list can see how to help? Problems building or running Apache are *not* on-topic here; The possibly on-topic stuff for this list would relate purely to the question, "How do I configure Apache2 to do virtual hosting against Zope?" If you google for "apache2 zope virtual hosting", you will find a bunch of useful information, mostly having to do with configuring 'mod_rewrite' for the various named virtual hosts. WRT the caching directives: I have never used Apache as a caching proxy (I use Squid for that), and I doubt many others here have either. Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE00qg+gerLs4ltQ4RAuLpAJ48Qgend0eQDLi8t6R/BJZ3ZRTHugCg2BTQ q1QNK1q2Fep7Pnm4eXD64Wk= =gkF1 -----END PGP SIGNATURE-----
Several cache modules changed in apache 2.x, but the apache 1.x directives you list have nothing to do with proxying or zope, they are just apache cache tuning options. If your problem is with proxying and VHM, and the problem is in Apache configuration, the directives you need to look at are RewriteRule (with [P] flag) or ProxyPass. It really seems unlikely that these are the problem though. If VHM is the problem you should be hitting zope but just not getting the right folder/object returned. If not then the problem is likely Apache configuration. I'd suggest you start with a clean new default apache config, and start moving your configuration changes in a bit at a time, and test after each change. If you can't figure out the source of the problem and are desperate and need to get your users up, depending on what else you are doing on the box, you could just run zope directly on port 80 (and possibly set up the manual path translations in VHM via the Zope management interface if needed). -- Tim Middleton | Vex.Net | There are a thousand hacking at the branches x@veX.net | VexTech.ca | of evil [but who] at the root. --Thoreau (W)
participants (4)
-
beno -
Jens Vagelpohl -
Tim Middleton -
Tres Seaver