nitin
June 10, 2010, 11:24am
1
Hi All,
I want to know which process is opening these ports. So far I've ran these commands, and got nothing :
tcp 0 0 *:38862 *:* LISTEN -
udp 0 0 *:45468 *:* -
[root@WAR47 ~]#lsof -w -n -i tcp:38862
[root@WAR47 ~]#
[root@WAR47 ~]#netstat -ap | grep 38862
tcp 0 0 *:38862 *:* LISTEN -
lsof does not give me anything for port 38862. BTW, I do have NFS enabled on this box, so I can see the RPC ports like:
[root@WAR47 ~]#netstat -ap | grep rpc
tcp 0 0 *:38444 *:* LISTEN 2727/rpc.statd
tcp 0 0 *:sunrpc *:* LISTEN 22734/portmap
tcp 0 0 *:34384 *:* LISTEN 2784/rpc.mountd
udp 0 0 *:783 *:* 2727/rpc.statd
udp 0 0 *:50763 *:* 2784/rpc.mountd
udp 0 0 *:sunrpc *:* 22734/portmap
udp 0 0 *:48637 *:*
Is 38862 related to RPC is some way?
Thanks,
Nitin
What's the output of fuser (you appear to be using Linux, so the bellow command should work):
fuser 38862/tcp
nitin
June 10, 2010, 12:05pm
3
Yep, I'm on an Ubuntu system.
I ran fuser, and got nothing :
[root@WAR47 ~]#fuser 38862/tcp
[root@WAR47 ~]#
Strangely, I ran top too, and it says 0 zombie processes. Hmm..
Thanks,
Nitin
... and you're sure that that port is still present in the netstat output?
nitin
June 10, 2010, 12:12pm
5
I think so.
[root@WAR47 ~]# date
10 12:08:47 EDT 2010
[root@WAR47 ~]#netstat -ap | grep 38862
tcp 0 0 *:38862 *:* LISTEN -
[root@WAR47 ~]#netstat -apn | grep 38862
tcp 0 0 0.0.0.0:38862 0.0.0.0:* LISTEN -
I just checked it again.
/etc/services?
grep -F 38862 /etc/services
I suppose it's serviced by xinetd.
nitin
June 10, 2010, 12:23pm
7
Nada.
[root@WAR47 ~]#grep -F 38862 /etc/services
[root@WAR47 ~]#
---------- Post updated at 09:19 PM ---------- Previous update was at 09:18 PM ----------
Don't know if this helps:
[root@WAR47 ~]#xinetd
The program 'xinetd' is currently not installed. You can install it by typing:
sudo apt-get install xinetd
bash: xinetd: command not found
[root@WAR47 ~]#
---------- Post updated at 09:23 PM ---------- Previous update was at 09:19 PM ----------
BTW thanks for quick replies.
As far as I know, for established connections, this should happen only for connections that are initiated from kernel space (like NFS ...).
You could try rpcinfo -p to see it its output helps.
nitin
June 10, 2010, 5:08pm
9
That was it.
[root@WAR47 ~]#rpcinfo -p
.... snip
100021 1 tcp 38862 nlockmgr
100021 3 tcp 38862 nlockmgr
100021 4 tcp 38862 nlockmgr
Thanks a lot. I was really worried there!