Re: [us...@httpd] mod_cache caching cluster

On Mon, Dec 7, 2009 at 4:04 PM, Francis GALIEGUE wrote: > On Mon, Dec 7, 2009 at 20:08, Matthew Tice wrote: > > Hello, I was wondering if anyone has run across a means consolidating or > > clustering their cache? Currently we have 20 nodes that only serve up > > static c

Re: [us...@httpd] Re: mod_cache caching cluster

On Mon, Dec 7, 2009 at 12:23 PM, Dan Poirier wrote: > Matthew Tice writes: > > > I was digging around with mod_memcache - I really like the idea but 1) it > > doesn't look like it's actively developed, and 2) I can't seem to get the > > caching to

[us...@httpd] mod_cache caching cluster

Hello, I was wondering if anyone has run across a means consolidating or clustering their cache? Currently we have 20 nodes that only serve up static content. Each node is configured with a 6G ramdisk (mod_disk_cache). This works *ok* except for a couple issues. 1) We experience intermittent pe

Re: [us...@httpd] Re: High load using memcache and 9G tmpfs

On Mon, Jul 20, 2009 at 7:00 AM, Nicholas Sherlock wrote: > Matthew Tice wrote: > >> Currently we're migrating our static node cluster from 32bit OpenSuse 10.3 >> using the disk_cache_module on a 2G tmpfs to a 64bit CentOS 5.3 using the >> disk_cache module on a 9

[us...@httpd] High load using memcache and 9G tmpfs

Hello, Currently we're migrating our static node cluster from 32bit OpenSuse 10.3 using the disk_cache_module on a 2G tmpfs to a 64bit CentOS 5.3 using the disk_cache module on a 9G tmpfs. After pushing these CentOS nodes into production (and consequently adding many more requests) we started see

[us...@httpd] Re: Disallow CONNECT method

On Thu, May 21, 2009 at 10:18 AM, Matthew Tice wrote: > I can't seem to disallow the CONNECT method. Not matter what I try I keep > getting a 502 error. Here's the output of my installation: > We ended up moving our rewrite rule INTO the virtualhost directive: RewriteEn

[us...@httpd] Disallow CONNECT method

I can't seem to disallow the CONNECT method. Not matter what I try I keep getting a 502 error. Here's the output of my installation: # /opt/apache2/bin/httpd -v Server version: Apache/2.2.9 (Unix) Server built: Jun 18 2008 03:03:38 # /opt/apache2/bin/apachectl -t -D DUMP_MODULES Loaded Module

Re: htcacheclean ignoring -l (limit)?

> > Okay, I tried that. Here are the results: [snip] Alright, I've figured it out. It's somewhat counter-intuitive (at least for me). It looks like the -l (limit) doesn't take into consideration the size of the directory. Example: # /opt/apache2/bin/htcacheclean -v -t -p/www/cache -l300M S

Re: htcacheclean ignoring -l (limit)?

> > Try setting your cache size to some rediculously low (say 5K) mark. See if > htclean does anything. Also, does root have read/write permissions on > /www/cache? try chmod -R 777 /www/cache > > Okay, I tried that. Here are the results: # df -h /www/cache FilesystemSize Used Avail

Re: htcacheclean ignoring -l (limit)?

On Tue, Dec 16, 2008 at 2:01 PM, Dan Poirier wrote: > Have you tried -t? It looks like htcacheclean just counts the sizes of > the files, but if you have a lot of empty directories, that might be > taking up some space too. -t looks like it would clean that up. > I thought so too - I tried -t

Re: htcacheclean ignoring -l (limit)?

Exactly what have you done to start the daemon? have you nohup'd it? are you using an INIT script? > > It appears that you'd have to run > nohup htcacheclean -d5 -r -l700M -i > or some such > > There IS an option that you can do. you can do this: > add to your crontab a command to change out your

Re: htcacheclean ignoring -l (limit)?

On Tue, Dec 16, 2008 at 10:09 AM, Morgan Gangwere <0.fracta...@gmail.com>wrote: > [snip] > > Could be that something is taking up more space and its not being caught. > Either that or the -l says the maximum size for 1 file. Have you RTFM'd? > > Oh yeah, I've read the man page, http://httpd.apache

htcacheclean ignoring -l (limit)?

I'm running apache 2.2.9 on several nodes that serve static content only. I'm running into a problem where the disk cache is filling up (and subsequently problems serving the files). I've the following configuration: # /etc/fstab tmpfs /www/cache tmpfs auto,rw,size=1200M,nr_inodes=1M 0 0 # ps au

[EMAIL PROTECTED] Re: Find file in mod_disk_cache cache

On Wed, Nov 5, 2008 at 3:01 PM, Matthew Tice <[EMAIL PROTECTED]> wrote: > Hello, I'm using mod_disk_cache for my static content. I need a way of > deleting a cached entry manually. I've thrown together a shell script to do > that (taking the name of the file as a comm

[EMAIL PROTECTED] Find file in mod_disk_cache cache

Hello, I'm using mod_disk_cache for my static content. I need a way of deleting a cached entry manually. I've thrown together a shell script to do that (taking the name of the file as a command argument) but rolling through 2G worth of small jpeg's takes quite a while. I was wondering if anyone

Re: [EMAIL PROTECTED] Rewrite all but one page

> > RewriteCond %{SERVER_PORT} 80 > RewriteCond %{REQUEST_URI} !^/+partners/+video\.php > RewriteRule ^/partners(.*)$ > https://testvideo101.example.com/partners$1[R,NC] > > Mike > Thanks Mike, that did it. One question. Are the '+' necessar

[EMAIL PROTECTED] Rewrite all but one page

Hello, I feel like this is an easy one - but it's throwing me off. I have my webserver behind a netscaler load balancer. The netscaler handles the SSL traffic and redirects the decrypted traffic to port 81. I need to redirect all traffic except a certain page. The rewrite rule I have is this:

Re: [EMAIL PROTECTED] upgrade mod_rewrite

> > > mod_rewrite is versioned with apache, and the only (supported) way to > upgrade it is to upgrade apache. > > What, exactly, is the reported problem? I'm guessing it is > CVE-2006-3747, in which case it can be fixed by moving to 1.3.37 or > higher. (But going to 2.2 is not a bad idea, in gener

[EMAIL PROTECTED] upgrade mod_rewrite

Hello all, I'm currently using apache 1.3.33. Because of some auditing concerns I was told I need to upgrade mod_rewrite. Problem is that I really don't know what that entails. I'm not sure how to determine what version I'm using (if it's not tied to apache 1.3). Do I need to upgrade my apache