malc@equinox.unr.edu (Malcolm Carlock) (10/19/90)
For the past week or so, our previously trusty version 1.5.3 of nntpd, paired
with an equally "mature" version of inews, has started saying "435 Got it" to
each and every article our newsfeed machine tries to send it, even if it
doesn't really have the article in question. For the first couple of days (a
weekend) I watched our news partition, normally full at a steady 90% or so,
slowly dwindle as new articles failed to arrive.
I tried rebuilding the history files with 'expire -r', and eventually tried
simply deleting all history*, nhistory* and ohistory* files from ~news, but
no soap -- incoming articles that our feed tries to deliver via our nntpd
continue to be rejected with "435 Got it".
My life has more or less been saved these last few days by nntpxfer, which
I've been running every so often to our newsfeed while I've been taking care
of some other pressing matters. The creation dates on our inews and nntpd
binaries haven't (embarrassingly, perhaps) changed since '88 or so.
Before I go about brute-force rebuilding a new inews and/or nntpd, has anyone
seen this sort of behavior before, and if so, do you have suggestions for
curing it??
Please respond via email, and I will summarize to the net. If you respond
here, I may not see it...
Thanks in advance.
Malcolm L. Carlock Internet: malc@unrvax.unr.edu
UUCP: uunet!unrvax!malc