SV: SV: SV: SV: Some help with INN

[Gert Koefoed Andersen]

> >> As near as I can tell, INN 2.4 will never log that error message
> >> without some additional information (at least a colon and a space).
>
> > The last line I got in my /var/log/news/news is this Nov 3
> > 09.00.04.523 - localhost
> > <1194121285.701385.140370 at k79g2000hse.googlegroups.com> 436
> cant store
> > article
>
> Oh, wait, I'm wrong.  I misread the code.  The log message
> that includes the error message is logged to syslog, not to
> the news log.  Look in news.err to see the corresponding full
> error message.  (And make sure that you have syslog logging
> set up properly.)
>
This sound more like what I could see errors in.
I have tried to just run "pullnews > pullnews.log" and look in it and got
messages of groups there has both . * x and +, and what I found out is + the
accepted articles and x is for when my peer not could send some articles.
The . Should be for refusing and * for rejected on my localhost server.

I have then work a deal around it and run emerge --sync and emerge portage
to get the latest updated inn home, then unmerged inn some times and emerged
again (about 3 times)
Then noe have it installed with soem of the config not changed from main
inatall of, and just put my isp into incoming.conf and innfeed.conf, but
before the last emerge inn I deleted all old articles and reboot the mashie
3-4 times to be sure it will chck the hd on hda3 to be sure on no errors on
the hd and partion.
So i now have to be sure what is best setup for inn getting work around for
incoming and innfeed of articles form my isp news server.

In my system log file /var/log/messages have have this after a pullnews:
Innfeed[32129]: tdc final seconds 315 offered 0 accepted 0 refused 0
rejected 0 ......
Innfeed[32129]: tdc spooling no active connections
Innfeed[32129]: tdc:0 connections
Innfeed[32129]: tdc remote MODE STREAM
Innfeed[32129]: tdc final seconds 30 spooled 0 on_close 0 sleeping 0
Innd: s
Innd: localhost connected 20 streaming allowed

Then nothing more for this.
There is no news.err now but the old one there were was by 0 byte.


--
Gert Andersen
gert at kofo.org