[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
Top Document: INN FAQ Part 7/9: Problems with INN already running
Previous Document: (7.40) Some local postings don't make it to remote, but others do
Next Document: (7.42) news.daily complains about unknown entries from syslog
-
Search the FAQ Archives
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
Top Document: INN FAQ Part 7/9: Problems with INN already running
Previous Document: (7.40) Some local postings don't make it to remote, but others do
Next Document: (7.42) news.daily complains about unknown entries from syslog
(7.41) Expire does no longer work
Q: Expire suddenly stops with : Can't store key There were some cancel articles posted recently that tried to cancel more than one message at a time. Dbz code doesn't like this. One solution is the following: Grab the Perl 'fixhist' script off http://www.cis.ohio-state.edu/~barr/INN.html and follow the instructions at the top of the file. That will clean out the cruft from your history database and allow expire to run without crashing.
Top Document: INN FAQ Part 7/9: Problems with INN already running
Previous Document: (7.40) Some local postings don't make it to remote, but others do
Next Document: (7.42) news.daily complains about unknown entries from syslog
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]
Send corrections/additions to the FAQ Maintainer:
hwr@pilhuhn.de (Heiko W.Rupp)
Last Update October 12 2008 @ 00:13 AM