Support bug with process detection about gonetstat HOT 2 CLOSED

Hi Pavel, thanks for the report!

Now may I ask you if you are running this machine on vmware ?
I'm asking because I notice the acpid process was connected on port 903 and now all the connection on this port are closed in TIME_WAIT, usually the port 903 is use by vcenter and I don't know why but these connection do not appear on netstat output like this guy have described on this post.

I notice that all ocurrences of the acpid process has the local (127.0.0.1:2003) foreign ip with is running a python process with I assume is graphite (carbon) that are running given the port and the language with makes more weird to me since the port 903 is involved.

My library parses the /proc/net/tcp and the tcp file descriptors from the process so the tcp event for acpid exist.
Now I'm not saying that this is not a bug I am just trying to understand your environment and reproduce the problem.

Also if you want get only the listened ports I think you should filter the output of your pogram by checking the state of the process

    tcp_listeners := GOnetstat.Tcp()
        for _, process := range tcp_listeners {
            if process.State == "LISTEN" {
                file_logger.Printf("Port %d listened by %v", process.Port, process)
            }
        }

from gonetstat.

Hello!

I'm using VirtualBOX isolation. Thanks for advice for state check! Will try
it!

On Thursday, 23 June 2016, Rafael Santos [email protected] wrote:

Hi Pavel, thanks for the report!

Now may I ask you if you are running this machine on vmware ?
I'm asking because I notice the acpid process was connected on port 903
and now all the connection on this port are closed in TIME_WAIT, usually
the port 903 is use by vcenter and I don't know why but these connection do
not appear on netstat output like this guy have described on this post
http://www.v-front.de/2011/07/mysterious-port-903.html.

I notice that all ocurrences of the acpid process has the local (
127.0.0.1:2003) foreign ip with is running a python process with I assume
is graphite (carbon) that are running given the port and the language with
makes more weird to me since the port 903 is involved.

My library parses the /proc/net/tcp and the tcp file descriptors from the
process so the tcp event for acpid exist.
Now I'm not saying that this is not a bug I am just trying to understand
your environment and reproduce the problem.

Also if you want get only the listened ports I think you should filter the
output of your pogram by checking the state of the process

tcp_listeners := GOnetstat.Tcp()
    for _, process := range tcp_listeners {
        if process.State == "LISTEN" {
            file_logger.Printf("Port %d listened by %v", process.Port, process)
        }
    }

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#3 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/ACnfZhx5Z3lSfcUBvjfcG8l6JgoWBKFVks5qOpwVgaJpZM4I8h7V
.

Sincerely yours, Pavel Odintsov

from gonetstat.