Re: inn 2.7.0, expire takes ages and hangs

Hi Adam,

3. I added noexpire to news.daily cron line to avoid it in the future. I
guess there will be no consequences in my setup

expire rebuilds the history file, and makes the database more efficient because it resizes it depending on the number of stored articles.  I would therefore suggest to keep running expire.

4. What is responsible for expiring history? Expireover or expire?

The expire program cleans up and removes old entries in the history database.

expire begin Sat Oct 19 03:08:38 CEST 2024: (-v1)
     Article lines processed  6057586
     Articles retained        6051793
     Entries expired             5793
expire end Sat Oct 19 16:15:51 CEST 2024

I don't know why it took so much time.  It definitively shouldn't have.

Another question: why does it expire anything if I have expiration
disabled? I guess "Entries expired" should be 0 in all cases? Or is it
about removing history entries for articles that are no longer in CNFS (or
that are too old, I have "remember" set to 721: "/remember/:721")?

expire indeed removes entries for articles no longer present in your spool because they were cancelled or superseded for instance for your timehash spool, or your CNFS buffers have wrapped.  Also, the history keeps track of Message-IDs rejected by filters like cleanfeed, pyClean or like.  These Message-IDs are kept during /remember/ days.
--
Julien ÉLIE
« Ex nihilo nihil. » (Perse)