(7.5) Expire had problems and won't run again after fixing the problem

When expire starts up it "reserves" the server so that nobody else can
pause or throttle it.  This prevents anyone else from coming in and
modifying the history database.  If expire bails out because of a bad
error (e.g., your expire.ctl has syntax errors) it leaves the server
reserved so that no maintenance will be done until a good expire run has
occurred.  To unblock the server, use the ctlinnd "reserve" command with
an empty string argument. See also #7.46.

Top Document: INN FAQ Part 7/9: Problems with INN already running
Previous Document: (7.4) How come my host name comes out twice in the Path line?
Next Document: (7.6) Expire says "Group not matched (removed?) -- Using default ..."

Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page

[ Usenet FAQs | Web FAQs | Documents | RFC Index ]

Send corrections/additions to the FAQ Maintainer:
hwr@pilhuhn.de (Heiko W.Rupp)

Last Update October 22 2009 @ 05:25 AM