Expiry issue

[Bettina Fink]

Russ Allbery <rra at stanford.edu> wrote:

>> The CURRENT-20030120 did the expiry as expected but not the
>> CURRENT-20030123.
>> 
>> What changed?
> 
> I did a whole bunch of cleanups aimed at making things easier to audit for
> security, and a lot of those changes were tricky.  Could you give me more
> information on what failed?  It's possible that I missed something.

I'm experiencing expiry problems too, with both CURRENT-20030122 and
CURRENT-20030125.

[...]

ctlinnd: Empty reason
Daily Usenet report from Jan 25 03:00:01 to Jan 26 03:00:01

[...]

ctlinnd: Cannot read input file
Expire messages:
expire begin Sun Jan 26 03:01:07 CET 2003: (-v1 -z/news/log/expire.rm)
    expire: cannot reserve server
    Article lines processed        0
    Articles retained              0
    Entries expired                0
    Articles dropped               0
expire end Sun Jan 26 03:01:07 CET 2003
        all done Sun Jan 26 03:01:07 CET 2003
        expireover start Sun Jan 26 03:01:07 CET 2003
        expireover end Sun Jan 26 03:12:51 CET 2003
lowmarkrenumber begin Sun Jan 26 03:12:51 CET 2003: (/news/log/expire.lowmark)
lowmarkrenumber end Sun Jan 26 03:12:52 CET 2003

The server itself seems to be running fine.

HTH,
Bettina