[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#914577: marked as done (ITP: dropwatch -- tool for detecting and diagnosing dropped network packets)

Your message dated Tue, 12 Nov 2019 11:02:13 +0000
with message-id <E1iUTw5-000HiT-Nu@fasolo.debian.org>
and subject line Bug#914577: fixed in dropwatch 1.5.1-1
has caused the Debian Bug report #914577,
regarding ITP: dropwatch -- tool for detecting and diagnosing dropped network packets
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
914577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914577
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist

* Package name    : dropwatch
  Version         : 1.5
  Upstream Author : Neil Horman <nhorman@redhat.com>
* URL             : https://github.com/nhorman/dropwatch
* License         : GPL
  Programming Lang: C
  Description     : A tool for detecting and diagnosing packets being dropped

What is Dropwatch? Dropwatch is a project I started in an effort to improve the ability for developers and system administrator to diagnose problems in the Linux Networking stack, specifically in our ability to diagnose where packets are getting dropped. From my probing, I've come to the conclusion that there are four main shortcommings in our current environment:

1.    Consolidation, or lack thereof. Currently, if you would like to check on the status of dropped packets in the kernel, you need to check at least 3 places, and possibly more: The /proc/net/snmp file, the netstat utility, the tc utility, and ethool. This project aims to consolidate several of those checks into one tool, making it easier for a sysadmin or developer to detect lost packets

2.    Clarity of information. Dropped packets are not obvious. a sysadmin needs to be intimately familiar with each of the above tools to understand which events or statistics correlate to a dropped packet and which do not. While that is often self evident, it is also often not. Dropwatch aims to improve that clarity

3.    Ambiguity. Even when a dropped packet is detected, the causes for those dropped packets are not always clear. Does a UDPInError mean the application receive buffer was full, or does it mean its checksum was bad? Dropwatch attempts to disambiguate the causes for dropped packets.

4.    Performance. Utilties can be written to aggregate the data in the various other utilities to solve some of these problems, but such solutions require periodic polling of several interfaces, which is far from optimal, especially when lost packets are rare. This solution improves on the performance aspect by implementing a kernel feature which allows asyncronous notification of dropped packets when they happen.

--- End Message ---
--- Begin Message --- 
Source: dropwatch
Source-Version: 1.5.1-1

We believe that the bug you reported is fixed in the latest version of
dropwatch, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 914577@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Smirnov <onlyjob@debian.org> (supplier of updated dropwatch package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 04 Nov 2019 04:11:01 +1100
Source: dropwatch
Binary: dropwatch dropwatch-dbgsym
Architecture: source amd64
Version: 1.5.1-1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov <onlyjob@debian.org>
Changed-By: Dmitry Smirnov <onlyjob@debian.org>
Description:
 dropwatch  - tool for detecting and diagnosing dropped network packets
Closes: 914577
Changes:
 dropwatch (1.5.1-1) unstable; urgency=medium
 .
   * Initial release (Closes: #914577).
Checksums-Sha1:
 d0582a812fd3152f928547f4035164b4febeb946 1908 dropwatch_1.5.1-1.dsc
 bf702cfbdd80ad300454259b419de4c7b9fdb2a3 15676 dropwatch_1.5.1.orig.tar.xz
 1e57fb5eb759d0c4e00757b200d6bfd9f5483bff 4536 dropwatch_1.5.1-1.debian.tar.xz
 57d1327b52b2343b5e64ac3b8b840a6e8bf3ebad 57608 dropwatch-dbgsym_1.5.1-1_amd64.deb
 3f60b31a9b31b446e42cf8b5081862156706c28d 6116 dropwatch_1.5.1-1_amd64.buildinfo
 514533f8c06fd01b736e508a32d12092d91c5e04 11240 dropwatch_1.5.1-1_amd64.deb
Checksums-Sha256:
 8354395253c3121e3fce6afd318671598f05f6cc6b789ddee5933d68eb577250 1908 dropwatch_1.5.1-1.dsc
 1995e4727f0135e3805dddbfd953ee5fee8ebe36cc942fdc07b5145eb4c0604d 15676 dropwatch_1.5.1.orig.tar.xz
 13235ad84e23b7c74250f8deff8d7d3b9e91d7a6791de478c639a3ea6012b2c8 4536 dropwatch_1.5.1-1.debian.tar.xz
 996048744fa35c79b169f02054750b655d151cb93fbd844b52bc2fc44f5ccb9e 57608 dropwatch-dbgsym_1.5.1-1_amd64.deb
 efef184fff3e8255ee8b090c890906d13c6f0b7ba6924043b819f2b66ef6fb55 6116 dropwatch_1.5.1-1_amd64.buildinfo
 7e50438b08de5b15b9338d97bb7de44ddda8a051d16e59520b153a66c9116a75 11240 dropwatch_1.5.1-1_amd64.deb
Files:
 700a2e8d24aba614483eb5b314dc3525 1908 net optional dropwatch_1.5.1-1.dsc
 1324dccddbf5b003fdcda8f681199f40 15676 net optional dropwatch_1.5.1.orig.tar.xz
 bc40e0bad997603fbd7faa1a29d30fd7 4536 net optional dropwatch_1.5.1-1.debian.tar.xz
 1590e9b6729f023f42505af8d4da66d5 57608 debug optional dropwatch-dbgsym_1.5.1-1_amd64.deb
 638a32ce227e54a379ef5836b4efc1fa 6116 net optional dropwatch_1.5.1-1_amd64.buildinfo
 9adf553f8c0db6d582c2d1eaf0fb0832 11240 net optional dropwatch_1.5.1-1_amd64.deb

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEULx8+TnSDCcqawZWUra72VOWjRsFAl2/CmEACgkQUra72VOW
jRvNrQ//fSherP5tjmCtktgqNAGDDK/FIQcta4PpcA7SpbtTM3D+tiMWwQdCjfmr
EYKarzldpyWelc8Pte6L0ZHTWO+uikDp9+n1nb4HrsIsFuQhA61JNpKitSPAEVrE
zSwXbr+tMIH4uDI5YuRWbY4tYZz9cDD8Bmt9gVfesWbghAMmltXu7BbMMKrp28mV
cMFVvydk7EPC561qKMpdxg2YUp62Cmsrr7G2ozKzd6zPCDJjlWV874UGbejPbWjg
ZTuH1dDGqQ3MUHpfO+7WesPYbXWu48f81R24PC8aLjSgR2QjOFN+52nAZ6n7pWy/
JP/5/LEMFU6GS3rr8Ga0GWr9UlKSopTE7N+wGzwj4LdkMrZUXNr9FPKqsuwiw9As
1e/k65Tf0o1MrZOwrWqzYCCguPR6+32qu36pTBop9+HogFpbniHh0GYP82J0DMx6
BCNJQ+l1E82Ssxc1mh+U+yaXkoWkoq7z07Whz7i3g4Sx2ncCqj9ZPaXVO4akpxOi
G9Z89kWhSZ77kzhi68AowJ/cIN3fe02/XiBUKtUfNCNTWQpb6MyRQzIqhpUzWqr0
CVu37o6O242iFyi4altTltWKyIRCM7aZZtndjjp/nisfhF/cglhYMV4ojhyBBCsh
87AhiaFvDdsq4lp4qbLQ8A00cfIP2Fi9CZ69DLkd6GJTFlMsrJw=
=2GDG
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: