Re: [Rabbit-proxy-users] Temporary Files

[Jason F. <xen...@gm...>]

On 3/20/07, Robert Olofsson <ro...@kh...> wrote:
> Rabbit writes out an index file every now and then. Rabbit reads that
> index file when it starts up so the cache info should be reused.

I figured as much, just checking ...  :)

> As I told you the key/hook files are not part of the cache size
> (and they ought to be).

Is there any way to get a listing of just those files and check the
size on that?  ...

I *think* I accomplished this.  Tried the following sequence :

ls -laR | egrep "(hook|key)" > /tmp/list.txt

TOTAL=0 cat /tmp/list.txt | while read a b c d e f ; do let
TOTAL=$TOTAL+$e ; echo "$TOTAL" ; done

I came up with a grand total of about 32 Meg of hook and key files.
Subtract that from the total size of 1.6 Gig and there's still over 1
gig of unaccounted for data...

To verify my results, I took just the cache files, minus the hook and
key files, and tried the same test.. :

ls -laR | egrep -v "(hook|key)" > /tmp/list2.txt

TOTAL=0 cat /tmp/list2.txt | grep ^- | while read a b c d e f ; do let
TOTAL=$TOTAL+$e ; echo "$TOTAL" ; done

Here I got a grand total of about 899 meg.  Added to the 32 meg about
and this is about 920 meg, a tad lower than the 1.6 gig that du
reports.

If I use --apparent-size on my du command, I get 928 meg.  The error
is probably time dependent as this is a live cache, so files were
created/deleted as I performed these tests.  I can believe, I suppose,
that there's 500 meg of wasted space due to block size.  Still, that's
about 400 meg more than there should be if rabbit is cleaning at 500
meg.

So it would appear, at least to me, that rabbit isn't cleaning out
when it should?  Is there a way to "force" a cleanup, or see when the
cleanup occurs?

> I will try to fix the broken accounting, I will hopefully have time
> to do that in the next few days.

Ok, sounds good.  I'll keep hand-cleaning the cache till then...

BTW.  I've tried, and failed, to get into CacheStatus.  According to
what I've read, I need to have a user defined in the users file and my
IP not blocked in the access file.  Both of these hold true, but when
I try to login to the cache :

http://user:pass@mycache:8081/CacheStatus

It fails with a proxy authentication error.  Any idea what's going on here?

> /robo

Thanks!

-- 
Jason 'XenoPhage' Frisvold
Xen...@gm...
http://blog.godshell.com