Nethogs doesn't quit normally on ^C

[fzhedu]

Waiting for first packet to arrive (see sourceforge.net bug 1019381)
and couldn't quit normally, please help me!

[raboof]

Hmm, what version are you on?

[fzhedu]

0.8.2, the master branch. one centos6.5

[raboof]

That's odd. Can you try specifying the interface(s) to listen on explicitly, and running with 'strace'?

[fzhedu]

[claims@90s191 ~]$ sudo /usr/local/sbin/nethogs -V
version 0.8.2-SNAPSHOT
[claims@90s191 ~]$ sudo /usr/local/sbin/nethogs -t
Ethernet link detected
Ethernet link detected
Adding local address: fe80::da9d:67ff:fe23:885d
Ethernet link detected
Adding local address: 10.11.1.191
Adding local address: 2001:da8:8005:4422:da9d:67ff:fe23:885c
Adding local address: fe80::da9d:67ff:fe23:885c
Ethernet link detected
Waiting for first packet to arrive (see sourceforge.net bug 1019381)

Refreshing:
unknown TCP/0/0 0 0

---

then it's blocking, and couldn't quit.

[Busindre]

Hi, I have the same problem.

nethogs: version 0.8.2-SNAPSHOT
SO: Red Hat Enterprise Linux Server release 6.3 (Santiago)
Command: nethogs em1

Attached strace output command.
report.txt

[alexya]

me 2. I want to redirect the nethogs data to a log file, so that I can analysis the network information.
I tried the following script but got the same issue as above.
-> % sudo nethogs -d 5 | sed 's/[^[:print:][:cntrl:]]//g' > nethogs.txt
Waiting for first packet to arrive (see sourceforge.net bug 1019381)

I used apt-get install to install it, and the version is 0.8.0

[raboof]

@alexya I think you're having a different issue (or you might not have an issue at all): this message may sound like an error, but in fact it was printed every time nethogs starts.

You normally wouldn't notice it as the first packet would arrive quickly, but since you're sending stdout to a nethogs.txt it's more distracting for you.

I've removed the message in 8e9de7a as it's probably more confusing than useful at this point.

[raboof]

@fzhedu hmm, I tried reproducing on centos 6.5 with vagrant init nrel/CentOS-6.5-x86_64; vagrant up --provider virtualbox but it worked for me.

[raboof]

I'm afraid I'm not sure how to make progress on this issue without a way to reproduce. Help welcome!

[eternaltyro]

I can reproduce this bug on Amazon Linux instance 2016.09-release. The problem is as described. It blocks the terminal and won't quit.

[root@appserver user]# ps aux | grep nethogs
root      9135 32.8  0.0  26240  8188 pts/1    R+   16:05   0:06 nethogs
root      9547  0.0  0.0 110460  2160 pts/0    S+   16:05   0:00 grep --color=auto nethogs
[root@appserver user]# lsof | grep nethogs
nethogs    9135       root  cwd       DIR              202,1        4096      21978 /home/user
nethogs    9135       root  rtd       DIR              202,1        4096          2 /
nethogs    9135       root  txt       REG              202,1       56968      34046 /usr/sbin/nethogs
nethogs    9135       root  mem       REG                0,7               10593870 socket:[10593870] (stat: No such file or directory)
nethogs    9135       root  mem       REG              202,1       19520       3341 /lib64/libdl-2.17.so
nethogs    9135       root  mem       REG              202,1      134000       3646 /lib64/libtinfo.so.5.7
nethogs    9135       root  mem       REG              202,1     2112368       3335 /lib64/libc-2.17.so
nethogs    9135       root  mem       REG              202,1       89312       3327 /lib64/libgcc_s-4.8.3-20140911.so.1
nethogs    9135       root  mem       REG              202,1     1141560       3343 /lib64/libm-2.17.so
nethogs    9135       root  mem       REG              202,1      983552       3775 /usr/lib64/libstdc++.so.6.0.19
nethogs    9135       root  mem       REG              202,1      156024       3642 /lib64/libncurses.so.5.7
nethogs    9135       root  mem       REG              202,1      250920      30577 /usr/lib64/libpcap.so.1.4.0
nethogs    9135       root  mem       REG              202,1      164440       3328 /lib64/ld-2.17.so
nethogs    9135       root    0u      CHR              136,1         0t0          4 /dev/pts/1
nethogs    9135       root    1u      CHR              136,1         0t0          4 /dev/pts/1
nethogs    9135       root    2u      CHR              136,1         0t0          4 /dev/pts/1
nethogs    9135       root    3r     FIFO               0,10         0t0   10593868 pipe
nethogs    9135       root    4w     FIFO               0,10         0t0   10593868 pipe
nethogs    9135       root    5u     pack           10593870         0t0        ALL type=SOCK_RAW
nethogs    9135       root    6r      REG                0,4           0 4026532305 /proc/9135/net/tcp

[raboof]

Cool will try on AWS soon!

[raboof]

Hmm, I'm still failing to reproduce this problem. Tried:

• Creating a t2.nano in eu-west-1b based on amzn-ami-hvm-2016.09.1.20161221-x86_64-gp2 (ami-c51e3eb6)
• ssh into it
• sudo yum install git gcc gcc-c++ ncurses-devel.x86_64 libpcap-devel.x86_64
• git clone https://github.com/raboof/nethogs
• cd nethogs
• make
• sudo src/nethogs

Can you spot the difference?