🚀 go-pugleaf

In <KATZ.93Jan11110023@carbon.elements.rpal.rockwell.com> katz@rpal.rockwell.com writes:
>Can some tell me what causes error messages of the form shown below in
>INN?
>Jan 11 09:57:47 carbon innd: ME cant update_active talk.politics.misc
>Jan 11 09:58:15 carbon innd: ME cant update_active soc.motss
It tried to assign an article number that is too big to fit into your
active file.

>I then nfs mounted the new location on the old ...
Most people believe that it is best to have the spool directory be a local
filesystem on the same host where innd or relaynews resides.  They believe
this to be even more true of the lib directory.  Nobody can directly point
fingers at NFS bugs or (mis-)features that cause problems, but experienced
sys admins are generally very paranoid about doing this.  Just a data point.

>Jan 11 09:30:37 carbon innd: ME cant symlink /usr/local/news/alt/politics/clinton/23120 and talk/politics/misc/99999 File exists
Sounds like your active file got messed up?  Do 'ctlinnd throttle' and
edit the active file to make sure that all your fields are wide enough.
The reload the active file, do 'ctlinnd renumber' to get everything in
sync, and then do 'ctlinnd go'.

>I know that this can happen as a result of doing something like tar to
>copy news and thereby splitting cross-posted articles.
No, INN will revert to symlinks fine.  Make sure to use the -l flag in
your expire, however.  See also the caveats in news-recovery.8.
	/r$