[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
Top Document: INN FAQ Part 5/9: Other error messages and what they mean
Previous Document: (5.9) inews says "bad message-id"
Next Document: (5.11) "File exists writing symlinking article file -- throttling"
-
Search the FAQ Archives
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
Top Document: INN FAQ Part 5/9: Other error messages and what they mean
Previous Document: (5.9) inews says "bad message-id"
Next Document: (5.11) "File exists writing symlinking article file -- throttling"
(5.10) Why do all these "readclose" messages show up in my syslog?
Chris Schmidt <cs@germany.eu.net> says: The "readclose" message indicates that a remote connection to your server was not correctly terminated with the server-command "quit". This can have two reasons. First the line your feed uses to connect to you might be instable so that the connection drops every now and then. Solution: either ignore theses messages or find out why the line is unstable. The second reason for these messages could be a missconfigured client-program at your feed. This means the program (e.g nntplink) does close the connection without sending the "quit" first. If you configure a lower number for the exit-timeout (-e) than the close-timeout (-C) in nntplink then exactly this will happen. Solution: ask your feed to fix its nntplink-setup. Let me repeat that: If you are using "nntplink" your -e value must be higher than your -C value.
Top Document: INN FAQ Part 5/9: Other error messages and what they mean
Previous Document: (5.9) inews says "bad message-id"
Next Document: (5.11) "File exists writing symlinking article file -- throttling"
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
Send corrections/additions to the FAQ Maintainer:
hwr@pilhuhn.de (Heiko W.Rupp)
Last Update October 22 2009 @ 05:25 AM