Re: Diagnosing socket "Connection reset by peer"

Path	csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!xlned.com!feeder5.xlned.com!news2.euro.net!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Return-Path	<davea@davea.name>
X-Original-To	python-list@python.org
Delivered-To	python-list@mail.python.org
X-Spam-Status	OK 0.021
X-Spam-Evidence	'H': 0.96; 'S': 0.00; 'causing': 0.04; 'subject:reset': 0.07; 'quiet': 0.09; 'subject:peer': 0.09; 'python': 0.11; '(note': 0.16; 'packets.': 0.16; 'received:74.208.4.195': 0.16; 'wrote:': 0.18; 'later': 0.20; 'help.': 0.21; 'network,': 0.22; 'header:User-Agent:1': 0.23; 'header:In-Reply-To:1': 0.27; 'am,': 0.29; 'code': 0.31; 'could': 0.34; 'but': 0.35; 'there': 0.35; 'filter': 0.38; 'to:addr:python- list': 0.38; 'files': 0.38; 'to:addr:python.org': 0.39; 'either': 0.39; 'read': 0.60; 'analysis,': 0.60; 'subject:"': 0.60; 'establish': 0.61; 'save': 0.62; 'within': 0.65; 'received:74.208': 0.68
Date	Wed, 22 May 2013 08:50:24 -0400
From	Dave Angel <davea@davea.name>
User-Agent	Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version	1.0
To	python-list@python.org
Subject	Re: Diagnosing socket "Connection reset by peer"
References	<038ecc3e-1272-46c0-84d5-556daeffbde0@googlegroups.com>
In-Reply-To	<038ecc3e-1272-46c0-84d5-556daeffbde0@googlegroups.com>
Content-Type	text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding	7bit
X-Provags-ID	V02:K0:28drIaKevr9eDYDB6OwL1K9Snd49EP+qdyjen4UKcpz NjaTV7z9MAodt7N3plVbyHjR/UoCUPVy5rg0CgrUoe8TTgmqWp Vs9/LF+60RUw0GlWJzVJd3Tjn74dJYeZ8+n0uHWGUDAfpqNYxp UWGZGtPyinPSQvNHMunu/otKGwt6puIZpZc9N4ArlpBOP/1ApH USfaTnD1r/VCf7pBuUBOYjjR14+geaRcjljnUL+n+Kmh8QOaLT d6TLTSiMtMglrk4TEmacijl41hhrEoiBbra2jZhQftzDaJVD4F gn9/8bqzqul+V5DsdZcRgxEdbcOSQ/HdUrfBMKgAcJekTIMRF/ ODvS2Afja6V3hz2gE2Xs=
X-BeenThere	python-list@python.org
X-Mailman-Version	2.1.15
Precedence	list
List-Id	General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe	<http://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive	<http://mail.python.org/pipermail/python-list/>
List-Post	<mailto:python-list@python.org>
List-Help	<mailto:python-list-request@python.org?subject=help>
List-Subscribe	<http://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups	comp.lang.python
Message-ID	<mailman.1963.1369227039.3114.python-list@python.org> (permalink)
Lines	17
NNTP-Posting-Host	2001:888:2000:d::a6
X-Trace	1369227039 news.xs4all.nl 15888 [2001:888:2000:d::a6]:41258
X-Complaints-To	abuse@xs4all.nl
Xref	csiph.com comp.lang.python:45728

Show key headers only | View raw

On 05/22/2013 04:46 AM, loial wrote:
>    <SNIP>
>
> .... Is there any additional traceing I can do(either within my python code or on the network) to establish what is causing this error?
>

Try using Wireshark.  It can do a remarkable job of filtering, 
capturing, and analyzing packets.  It can also read and write pcap 
files, which you could either save for later analysis, or send to 
someone who might help.  (Note - unfiltered pcap files can be very large 
on a busy network, but if you can quiet other traffic, you may not need 
to filter at all.)

-- 
DaveA

Thread

Diagnosing socket "Connection reset by peer" loial <jldunn2000@gmail.com> - 2013-05-22 01:46 -0700
  Re: Diagnosing socket "Connection reset by peer" Matt Jones <matt.walker.jones@gmail.com> - 2013-05-22 06:46 -0500
    Re: Diagnosing socket "Connection reset by peer" Jorgen Grahn <grahn+nntp@snipabacken.se> - 2013-05-22 19:54 +0000
  Re: Diagnosing socket "Connection reset by peer" Dave Angel <davea@davea.name> - 2013-05-22 08:50 -0400
    Re: Diagnosing socket "Connection reset by peer" Jorgen Grahn <grahn+nntp@snipabacken.se> - 2013-05-22 19:44 +0000
      Re: Diagnosing socket "Connection reset by peer" Grant Edwards <invalid@invalid.invalid> - 2013-05-22 19:55 +0000

csiph-web