1. Forum
  2. USENET
  3. news.software.nntp

  • INN makehistory misfiled most of the spool?

    From Jesse Rehmer@jesse.rehmer@blueworldhosting.com to news.software.nntp on Sat Jun 27 12:29:56 2026
    From Newsgroup: news.software.nntp

    I ran makehistory (without rebuilding overview) on a server using tradspool recently. Checking through a number of groups after makehistory ran shows many/most articles are not found. When digging deeper, the articles are found with grephistory, but sm is returning the wrong path for them.

    For example, <111lhgj$ct47$11@dont-email.me> is posted to
    comp.sys.mac.vintage, but when looking at sm it cannot retrieve the article. Running sm -c provides an incorrect path to the article:

    $ grephistory '<111lhgj$ct47$11@dont-email.me>' | sm
    sm: could not retrieve @05000000AE4F000000000000091900000000@

    $ grephistory '<111lhgj$ct47$11@dont-email.me>' | sm -c @05000000AE4F000000000000091900000000@ method=tradspool class=0 ngnum=44623 artnum=0 file=/usr/local/news/spool/articles/zipnews/gov/us/faa/2329

    The article is present in /usr/local/spool/news/articles/comp/sys/mac/vintage using the same article number displayed with sm -c:

    [news@spool1 ~/spool/articles/comp/sys/mac/vintage]$ grep '<111lhgj$ct47$11@dont-email.me>' *
    2329:Message-ID: <111lhgj$ct47$11@dont-email.me>

    Articles that have arrived after makehistory ran are fine. I'm at a loss what caused this kind of behavior and what I should do to correct it, any advice? --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Jesse Rehmer@jesse.rehmer@blueworldhosting.com to news.software.nntp on Sat Jun 27 14:53:49 2026
    From Newsgroup: news.software.nntp

    On Jun 27, 2026 at 7:29:56rC>AM CDT, "Jesse Rehmer" <jesse.rehmer@blueworldhosting.com> wrote:

    I ran makehistory (without rebuilding overview) on a server using tradspool recently. Checking through a number of groups after makehistory ran shows many/most articles are not found. When digging deeper, the articles are found with grephistory, but sm is returning the wrong path for them.

    For example, <111lhgj$ct47$11@dont-email.me> is posted to comp.sys.mac.vintage, but when looking at sm it cannot retrieve the article. Running sm -c provides an incorrect path to the article:

    $ grephistory '<111lhgj$ct47$11@dont-email.me>' | sm
    sm: could not retrieve @05000000AE4F000000000000091900000000@

    $ grephistory '<111lhgj$ct47$11@dont-email.me>' | sm -c @05000000AE4F000000000000091900000000@ method=tradspool class=0 ngnum=44623 artnum=0 file=/usr/local/news/spool/articles/zipnews/gov/us/faa/2329

    The article is present in /usr/local/spool/news/articles/comp/sys/mac/vintage using the same article number displayed with sm -c:

    [news@spool1 ~/spool/articles/comp/sys/mac/vintage]$ grep '<111lhgj$ct47$11@dont-email.me>' *
    2329:Message-ID: <111lhgj$ct47$11@dont-email.me>

    Articles that have arrived after makehistory ran are fine. I'm at a loss what caused this kind of behavior and what I should do to correct it, any advice?

    I'm an idiot. Trying to fix another issue recently, I cleared the
    tradspool.map file *after* I had rebuilt the history file. Not sure why I didn't remember I needed to do that before rebuilding history, but maybe a lesson to others.
    --- Synchronet 3.22a-Linux NewsLink 1.2