History problems, probably chained

[Christoph Biedl]

Zenon Panoussis wrote...

> I am trying to cancel some messages and failing. As I go
> along, I run into more errors.

I cannot really help, just some questions, to you and also to the
auditory.

>    ctlinnd cancel "msg-id"
> 
> returns Ok, but the messages are still on the server and
> available to the readers after news.daily has run.

Anything in the logfiles after the ctlinnd command that might be a sign
for trouble?

And by the way, in order to cancel a list of messages I prefer
$ cat list | grephistory -s | xargs sm -r

> After various fiddling and searching exercises I tried
> Scott Russel's recipe from 11/16/2001 on this list and
> did
[ rebuild history ]
> This created a whole new history and overview and returned
> a dozen entries like
> 
>    Duplicate message-id "[0CD4F78301AD8F31A7ABD7F6F6C89B1D]" in history
> 
> in the news.daily report.

To me this is a clear sign that something went wrong before - probably
an unclean INN shutdown. My solution in such a situation was to remove
that duplicate Message-ID (hashes) using sort and perl. Works fine with
cnfs, other storage methods might require further work.

On the other hand INN should run even if you see these messages although
your users might report strange effects like articles that appear two
times in a group.

> Repeating the whole procedure
> got me nowhere except when, for some reason, I started
> getting messages like this instead:
> 
>    expire begin Sun Jun 13 19:14:32 CEST 2004: (-v1)
>        Can't reserve server
>        Article lines processed        0

I haven't seen that message since I've upgraded to 2.4.x ...

	Christoph