I'm having some problems with nntpcache constantly expiring
everything out of the cache. Despite the 'Current Configuration
assignments' of the status page showing:
int minFilesFreePercent 10
int minBlocksFreePercent 10
time maxArtAge 14d
it keeps blowing everything away, with syslog messages like:
Apr 15 00:23:24 sten nntpcache-expire[13174]: expire.c:212: usedblocks = 52.5%, usedinodes = 22.9%, maxArtAge = 46s, expire ended
Clearly, there are more then 10% of the inodes and blocks
free, but everything is being wiped clean. In what I think is a
related matter, after this finished, it keeps logging errors like the
following:
Apr 15 00:24:46 sten nntpcache-client[13166]: xover.c:727:Operation not permitted: unable to open/create/fstat 'news.tivoli.com./rec/arts/sf/tv/babylon5/moderated/98304_xover'
Apr 15 00:24:46 sten nntpcache-client[13166]: xover.c:732:Bad file descriptor: unable to lockex 'news.tivoli.com./rec/arts/sf/tv/babylon5/moderated/98304_xover'
I think that this is due to the expire process blowing away
the directory that the client process is wanting to put the xover
files into. HELP!
--
Either you can say I'm for Open Source, open standards, or I'm against
standards. Either you can say I'm for giving customers and communities
a choice or I'm against giving customers and communities a choice.
- Sam Palmisano, IBM President and COO at LinuxWorld Expo 2001
