results from 'netstat -tlpn' gives me a line...
tcp 0 0 0.0.0.0:46929 0.0.0.0:* LISTEN -
googling for port 46929 doesn't turn up anything and so I don't have a clue what process this belongs to.
Do I have to start capturing activity on this port or is there a better way to find out what this port is about?
On Mon, Aug 20, 2007 at 09:46:21AM -0700, Craig White wrote:
results from 'netstat -tlpn' gives me a line...
tcp 0 0 0.0.0.0:46929 0.0.0.0:* LISTEN -
Rerun the command as root (eg under sudo). Then the "p" option will tell you what process is listening.
eg % netstat -anp | grep -w 22 | grep LISTEN (Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.) tcp 0 0 :::22 :::* LISTEN -
% sudo netstat -anp | grep -w 22 | grep LISTEN tcp 0 0 :::22 :::* LISTEN 3742/sshd
If you run that netstat command as root, then the last column should show which process/PID is listening on that port. (that is what the '-p' option to netstat tells you)
lsof is handy for this as well.
Mike
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Craig White Sent: August 20, 2007 12:46 PM To: CentOS mailing list Subject: [CentOS] open port 46929
results from 'netstat -tlpn' gives me a line...
tcp 0 0 0.0.0.0:46929 0.0.0.0:* LISTEN -
googling for port 46929 doesn't turn up anything and so I don't have a clue what process this belongs to.
Do I have to start capturing activity on this port or is there a better way to find out what this port is about?
-- Craig White craig@tobyhouse.com
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I have been running as root and if you notice, I did have a 'p' option....
# netstat -tlpn |grep 46929 tcp 0 0 0.0.0.0:46929 0.0.0.0:* LISTEN -
and thus the process isn't displayed.
Likewise (and I tried this with lsof before posting to the list)...
# lsof |grep 46929 #
but I can see that only the Fedora systems are connecting to this port, not the Macs or Windows systems and I'm wondering if this isn't relating to NFS mount since each of the Fedora systems have 2 NFS mounts off the server.
Craig
On Mon, 2007-08-20 at 12:52 -0400, mike.redan@bell.ca wrote:
If you run that netstat command as root, then the last column should show which process/PID is listening on that port. (that is what the '-p' option to netstat tells you)
lsof is handy for this as well.
Mike
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Craig White Sent: August 20, 2007 12:46 PM To: CentOS mailing list Subject: [CentOS] open port 46929
results from 'netstat -tlpn' gives me a line...
tcp 0 0 0.0.0.0:46929 0.0.0.0:* LISTEN -
googling for port 46929 doesn't turn up anything and so I don't have a clue what process this belongs to.
Do I have to start capturing activity on this port or is there a better way to find out what this port is about?
On Mon, Aug 20, 2007 at 10:05:54AM -0700, Craig White wrote:
I have been running as root and if you notice, I did have a 'p'
That you were running as root wasn't clear from your message (different people use different prompts). I knew you used a "p" which is why I said _rerun_ the command.
# netstat -tlpn |grep 46929 tcp 0 0 0.0.0.0:46929 0.0.0.0:* LISTEN -
and thus the process isn't displayed.
In this case it might then be an RPC process. So try "rpcinfo -p" eg on my machine (as root): % netstat -anp | grep LIST | head -1 tcp 0 0 0.0.0.0:32769 0.0.0.0:* LISTEN -
% rpcinfo -p | grep -w 32769 100021 1 tcp 32769 nlockmgr 100021 3 tcp 32769 nlockmgr 100021 4 tcp 32769 nlockmgr
On Mon, 2007-08-20 at 13:21 -0400, Stephen Harris wrote:
On Mon, Aug 20, 2007 at 10:05:54AM -0700, Craig White wrote:
I have been running as root and if you notice, I did have a 'p'
That you were running as root wasn't clear from your message (different people use different prompts). I knew you used a "p" which is why I said _rerun_ the command.
# netstat -tlpn |grep 46929 tcp 0 0 0.0.0.0:46929 0.0.0.0:* LISTEN -
and thus the process isn't displayed.
In this case it might then be an RPC process. So try "rpcinfo -p" eg on my machine (as root): % netstat -anp | grep LIST | head -1 tcp 0 0 0.0.0.0:32769 0.0.0.0:* LISTEN -
% rpcinfo -p | grep -w 32769 100021 1 tcp 32769 nlockmgr 100021 3 tcp 32769 nlockmgr 100021 4 tcp 32769 nlockmgr
---- indeed - that was it...nlockmgr
# rpcinfo -p|grep 46929 100021 1 tcp 46929 nlockmgr 100021 3 tcp 46929 nlockmgr 100021 4 tcp 46929 nlockmgr
Thanks
-
Craig White -
mike.redan＠bell.ca -
Stephen Harris