[nmglug] Connection Reset by Peer

[WA7BSZ]

I have seen this "connection reset by peer" many times, and the most
recent is when trying to get X to work on Debian.  Somehow when trying
to start X, there was a "connection reset by peer".  A multiple
personality computer.  Maybe one server reset the connection of another
server, so X got nowhere.  So many times the error message does not
describe the real problem.  That would take a lot more time in writing
the software, testing to get the error messages, and then changing the
messages to correspond to what really happened.  Most developers don't
have time for that, don't want to do it, or don't know their imagined
reasons the error messages would pop up are not the real reasons they
are.  

Like in dos, Bad Command or Filename.  Maybe it was a good command or
filename, but it wasn't in your path.  How about "I couldn't find that
command, you may have made a mistake in typing it or it might be in
some other directory."  If Microsoft wanted to be even more alienating
the message could have been "You messed up somehow, please get more
training before you try that again, perhaps in typing." 

So, do we know where "Connection Reset by Peer" comes from?  

Here is something from ebay pages:

"Should you receive the "Connection reset by peer" error message, it
means "the system is really busy" - try again in a few seconds. If you
hit "reload" as many times as it takes, you will eventually connect,
usually in a matter of seconds."

http://pages.ebay.com/help/welcome/connection-reset-error.html

So it is interesting, there is an example where they say, when you get
this error message it really means this.  

Kim 

> Today's Topics:
> 
>    1. Unsupported Protocol with pppd (Anthony Martinez)
> 
> 
>
----------------------------------------------------------------------
> 
> Message: 1
> Date: Fri, 18 Jun 2004 22:10:55 -0600
> From: Anthony Martinez <nmglug at pi.mrtheplague.net>
> Subject: [nmglug] Unsupported Protocol with pppd
> To: nmglug at nmglug.org
> Message-ID: <20040619041055.GF5334 at cnsp.com>
> Content-Type: text/plain; charset=us-ascii
> 
> Every once in a while when I dial into my isp with pppd, I get these
> errors
> 
> Jun 18 22:02:07 two-pi-r pppd[18830]: local  IP address
> 209.155.168.21
> Jun 18 22:02:07 two-pi-r pppd[18830]: remote IP address 67.129.71.5
> Jun 18 22:02:07 two-pi-r pppd[18830]: primary   DNS address
> 67.129.68.10
> Jun 18 22:02:07 two-pi-r pppd[18830]: secondary DNS address
> 67.129.68.11
> Jun 18 22:02:07 two-pi-r pppd[18830]: Unsupported protocol 'CallBack
> Control
> Protocol (CBCP)' (0xc029) received
> Jun 18 22:02:07 two-pi-r pppd[18830]: IPCP terminated by peer
> Jun 18 22:02:08 two-pi-r pppd[18830]: LCP terminated by peer
> Jun 18 22:02:11 two-pi-r pppd[18830]: Connection terminated.
> Jun 18 22:02:11 two-pi-r pppd[18830]: Connect time 0.1 minutes.
> Jun 18 22:02:11 two-pi-r pppd[18830]: Sent 114 bytes, received 112
> bytes.
> 
> (the callback control protocol)
> 
> Has anyone seen this error and fixed it? I'm using debian unstable
> but this has
> also happened with Redhat.
> 
> Thanks
> Pi
> 
> 
> -- 
> die_if_kernel("Kernel gets FloatingPenguinUnit disabled trap", regs);
> 	2.2.16 /usr/src/linux/arch/sparc/kernel/traps.c
> 
> 
> 
> ------------------------------
> 
> _______________________________________________
> nmglug mailing list
> nmglug at nmglug.org
> http://www.nmglug.org/mailman/listinfo/nmglug
> 
> 
> End of nmglug Digest, Vol 9, Issue 9
> ************************************
> 



	
		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail