[ 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.7) syslog: cant symlink
Next Document: (5.9) inews says "bad message-id"
-
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.7) syslog: cant symlink
Next Document: (5.9) inews says "bad message-id"
(5.8) syslog: cant read Connection reset by peer
This means that the client vanished or deliberately aborted the nnrpd TCP stream rather than closing it gracefully. This is a common situation, and it does not normally indicate a problem. Most, or all, of these messages are due to clients crashing or being aborted in the middle of a dialogue with nnrpd. For example, a PC or Mac user shuts off their machine at 5pm. Or, you are seeing the results of a bad design decision in the NewsWatcher newsreading program for the Mac. Future versions of NewsWatcher will be (hopefully) more graceful about closing connections. In other words, they should send "QUIT\r\n" on the socket, then close it.
Top Document: INN FAQ Part 5/9: Other error messages and what they mean
Previous Document: (5.7) syslog: cant symlink
Next Document: (5.9) inews says "bad message-id"
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