newscache: Questions about running version 0.99.22
Subject:
Questions about running version 0.99.22
From:
"Booker" ####@####.####
Date:
3 Jan 2003 21:16:30 -0000
Message-Id: <000c01c2b36c$448a0110$c17f4140@lava.net>
I have this version on a freebsd 4.6.2 box. I'm getting this error
messages and was wondering if anyone has any ideas on fixing it. The
error message I am getting in /var/log/messages:
Jan 3 10:52:07 kulolo NewsCache[33789]: Exception!
Jan 3 10:52:07 kulolo NewsCache[33789]: Type: System
Jan 3 10:52:07 kulolo NewsCache[33789]: Desc: maximum number of
retries reached ErrStr(-1): Unknown error: -1¿
Jan 3 10:52:09 kulolo NewsCache[33789]: Got address from inet_addr:
64.65.64.15
Jan 3 10:52:09 kulolo NewsCache[33789]: Exception!
Jan 3 10:52:09 kulolo NewsCache[33789]: Type: System
Jan 3 10:52:09 kulolo NewsCache[33789]: Desc: cannot connect to news
server ErrStr(49): Can't assign requested address
Jan 3 10:52:09 kulolo NewsCache[33789]: Got address from inet_addr:
64.65.64.15
Jan 3 10:52:09 kulolo NewsCache[33789]: Exception!
Jan 3 10:52:09 kulolo NewsCache[33789]: Type: System
Jan 3 10:52:09 kulolo NewsCache[33789]: Desc: cannot connect to news
server ErrStr(49): Can't assign requested address
Jan 3 10:52:09 kulolo NewsCache[33789]: Got address from inet_addr:
64.65.64.15
Jan 3 10:52:09 kulolo NewsCache[33789]: Exception!
Jan 3 10:52:09 kulolo NewsCache[33789]: Type: System
Jan 3 10:52:09 kulolo NewsCache[33789]: Desc: cannot connect to news
server ErrStr(49): Can't assign requested addres
My guess is this occurs because of SuperNews's very log timeout value.
And NewsCache's in ability to handle that. I'm assuming this because I
use tin to connect to my newscache server and it works fine when I first
start the program up. But If I leave my tin session unattended for more
than 5 minutes then the error messages above me occur. My tin reader
also cannot retrieve any more articles and just gives me an error that
the article is not on the server. Tin get's into this abort loop and I
have to kill the process because tin is stuck. But once I get out and
restart tin, things work fine again, until I hit that timeout value. Is
there a specific configuration I should be using with supernews so that
I can circumvent this 5 minutes session timeout they have?
My configuration for supernews is as follow:
NewsServerList {
Server corp.supernews.com nntp {
Retries 3
Read *
PostTo *
GroupTimeout 150
BindFrom 64.65.64.15
# Options not-offline
# Commands listgroup over
}
}
I'm waiting for the ports versin on freebsd to get to 1.1.8 and then I
can try that version also.
Mahalo,
Booker
