rkt logo

INN FAQ Part 5

Subject: (5.18) syslog message: innxmit[1234]: max connect failed Error 0

John Line <jml4@cus.cam.ac.uk> writes:

If you get syslog messages like
innxmit[1234]: max connect failed Error 0
when using nntpsend, it probably means you messed up a line in
nntpsend.ctl (specifically, missed out one of the first two fields).
While nntpsend.ctl is an obvious place to look for an nntpsend problem,
there is nothing obvious to link the error message directly to the
problem, because the text "max" is actually something invented by
nntpsend when processing the file, and doesn't exist in nntpsend.ctl.
It means the next-to-last field was null, but was the second field when
it should have been the third!

NB Remember to try inncheck when you have problems like this. I only
just thought of it, after finding the problem the hard way, and it
immediately reported "nntpsend.ctl:18: malformed line."


[Source: INN FAQ Part 5 Archive-name: usenet/software/inn-faq/part5]
[Last Changed: $Date: 1997/09/16 01:25:56 $ $Revision: 2.25 $]
[Copyright: 1997 Heiko Rupp, portions by Tom Limoncelli, Rich Salz, et al.]

(Corrections, notes, and links by Mib Software)
More Detailed Topics

Overview and Related Topics
Up to: INN Troubleshooting by message
Up to: INN Troubleshooting by Topic: outbound news
Up to: INN FAQ Table Of Contents for Part 5/9
INN Man Pages by Topic: Outgoing news
Installing InterNetNews

RKT Rapid-Links:[ Search ] [ RKT Tips ] Path: Usenet RKT / For Providers / INN FAQ / Part 5 / 0043.htm

You are reading from the Usenet RKT
Copyright 1997-1999, Forrest J. Cavalier III, Mib Software
INN customization and consulting
E-mail comments