Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #45728
| Date | 2013-05-22 08:50 -0400 |
|---|---|
| From | Dave Angel <davea@davea.name> |
| Subject | Re: Diagnosing socket "Connection reset by peer" |
| References | <038ecc3e-1272-46c0-84d5-556daeffbde0@googlegroups.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.1963.1369227039.3114.python-list@python.org> (permalink) |
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
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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