Port open/listen but no associated process
In the output of nmap -p- localhost I get an unknown open tcp port, that's different at each reboot. How can I determine which process opened it and listens through it. I tried many of the usual tools (netstat, ss, lsof) but I cannot find the culprit. Eg. sudo netstat -pan -Ainet | grep <PORT> gives no PID/Program name:
tcp 0 0 0.0.0.0:<PORT> 0.0.0.0:* LISTEN -
Maybe I should analyze the startup sequence? But how so?
Could anyone help?
linux networking process port
asked May 29 '18 at 16:57
tofcutetofcute
184
add a comment |
In the output of nmap -p- localhost I get an unknown open tcp port, that's different at each reboot. How can I determine which process opened it and listens through it. I tried many of the usual tools (netstat, ss, lsof) but I cannot find the culprit. Eg. sudo netstat -pan -Ainet | grep <PORT> gives no PID/Program name:
tcp 0 0 0.0.0.0:<PORT> 0.0.0.0:* LISTEN -
Maybe I should analyze the startup sequence? But how so?
Could anyone help?
linux networking process port
asked May 29 '18 at 16:57
tofcutetofcute
184
Could it potentially be that you've got malware, which masks itself with-as name ? Consider tryingpgrep "-". Also, trylsofstackoverflow.com/a/319997/3701431
– Sergiy Kolodyazhnyy
May 30 '18 at 0:28
If any of the answers solved your problem, please accept it by clicking the checkmark next to it. Thank you!
– Jeff Schaller
Jun 3 '18 at 11:24
add a comment |
In the output of nmap -p- localhost I get an unknown open tcp port, that's different at each reboot. How can I determine which process opened it and listens through it. I tried many of the usual tools (netstat, ss, lsof) but I cannot find the culprit. Eg. sudo netstat -pan -Ainet | grep <PORT> gives no PID/Program name:
tcp 0 0 0.0.0.0:<PORT> 0.0.0.0:* LISTEN -
Maybe I should analyze the startup sequence? But how so?
Could anyone help?
linux networking process port
asked May 29 '18 at 16:57
tofcutetofcute
184
In the output of nmap -p- localhost I get an unknown open tcp port, that's different at each reboot. How can I determine which process opened it and listens through it. I tried many of the usual tools (netstat, ss, lsof) but I cannot find the culprit. Eg. sudo netstat -pan -Ainet | grep <PORT> gives no PID/Program name:
tcp 0 0 0.0.0.0:<PORT> 0.0.0.0:* LISTEN -
Maybe I should analyze the startup sequence? But how so?
Could anyone help?
linux networking process port
linux networking process port
asked May 29 '18 at 16:57
tofcutetofcute
184
asked May 29 '18 at 16:57
tofcutetofcute
184
edited May 30 '18 at 17:43
tofcute
asked May 29 '18 at 16:57
tofcutetofcute
184
asked May 29 '18 at 16:57
tofcutetofcute
184
asked May 29 '18 at 16:57
tofcutetofcute
184
184
Could it potentially be that you've got malware, which masks itself with-as name ? Consider tryingpgrep "-". Also, trylsofstackoverflow.com/a/319997/3701431
– Sergiy Kolodyazhnyy
May 30 '18 at 0:28
If any of the answers solved your problem, please accept it by clicking the checkmark next to it. Thank you!
– Jeff Schaller
Jun 3 '18 at 11:24
add a comment |
Could it potentially be that you've got malware, which masks itself with-as name ? Consider tryingpgrep "-". Also, trylsofstackoverflow.com/a/319997/3701431
– Sergiy Kolodyazhnyy
May 30 '18 at 0:28
If any of the answers solved your problem, please accept it by clicking the checkmark next to it. Thank you!
– Jeff Schaller
Jun 3 '18 at 11:24
Could it potentially be that you've got malware, which masks itself with
- as name ? Consider trying pgrep "-". Also, try lsof stackoverflow.com/a/319997/3701431– Sergiy Kolodyazhnyy
May 30 '18 at 0:28
Could it potentially be that you've got malware, which masks itself with
- as name ? Consider trying pgrep "-". Also, try lsof stackoverflow.com/a/319997/3701431– Sergiy Kolodyazhnyy
May 30 '18 at 0:28
If any of the answers solved your problem, please accept it by clicking the checkmark next to it. Thank you!
– Jeff Schaller
Jun 3 '18 at 11:24
If any of the answers solved your problem, please accept it by clicking the checkmark next to it. Thank you!
– Jeff Schaller
Jun 3 '18 at 11:24
add a comment |
4 Answers
4
active
oldest
votes
Netstat does exactly what you ask, when run as root and with the correct flags:
sudo netstat -tnlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.1.1:53 0.0.0.0:* LISTEN 1931/dnsmasq
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 32296/cupsd
tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN 1550/postgres
tcp6 0 0 :::80 :::* LISTEN 3198/docker-proxy
Also, ss is the replacement of netstat and takes mostly the same flags, but has a differently formatted output
answered May 29 '18 at 17:37
Bruno9779Bruno9779
1,138515
Did a similar command (netstat -pan -Ainet) that gets the same result:tcp 0 0 0.0.0.0:41673 0.0.0.0:* LISTEN -This does not give any process name nor PID as I get-instead.
– tofcute
May 29 '18 at 21:18
Without sudo it is not similar. You can only see the PID of processes started by your user/groups
– Bruno9779
May 30 '18 at 13:30
Sorry, I forgot thesudoin my comment but I used it on my computer, as well as when usingssandlsof.
– tofcute
May 30 '18 at 17:43
add a comment |
As hinted at, ss can provide the answer as well; the syntax is:
sudo ss --tcp --listening --processes 'sport = 1234'
Where 1234 is the port-of-the-day from your nmap scan. This limits the output to TCP ports and shows the process name and PID that is listening on that port. sudo is only needed if you want the --process flag, which provides the process name and PID.
answered May 29 '18 at 18:40
Jeff SchallerJeff Schaller
43.1k1159137
I din't know the 'sport = <PORT>' trick, I used agrepinstead. Either way, here is what I get:LISTEN 0 64 *:41673 *:*No PID nor Program Name :-(
– tofcute
May 29 '18 at 21:28
Did you run it as root, or with sudo?
– Jeff Schaller
May 29 '18 at 21:53
I ran your command exactly as you gave it, from a user account, using sudo. Why?
– tofcute
May 30 '18 at 10:46
If you ran it without root privileges, you wouldn't be able to see the process name/pid; that could have explained the behavior.
– Jeff Schaller
May 30 '18 at 11:12
add a comment |
Some ports opened by the kernel and by some specific services (NFS, OCFS, ssh tunnels) are not visible with netstat nor ss
answered May 30 '18 at 14:33
Bruno9779Bruno9779
1,138515
add a comment |
I do have same problem for application , port is in listening state but process id is not showing up. please help me. used below commands. this is cloud aws server redhat linux.
netstat -tulpn
tcp 0 0 0.0.0.0:8008 0.0.0.0:* LISTEN -
netstat -ltpnae | awk 'NR==2 || /:8008/'
Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
tcp 0 0 0.0.0.0:8008 0.0.0.0:* LISTEN 0 142518 -
lsof | awk 'NR==1 || /142518/'
COMMAND PID TID USER FD TYPE DEVICE SIZE/OFF NODE NAME
answered 6 mins ago
vamshivamshi
1
New contributor
vamshi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f446745%2fport-open-listen-but-no-associated-process%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
Netstat does exactly what you ask, when run as root and with the correct flags:
sudo netstat -tnlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.1.1:53 0.0.0.0:* LISTEN 1931/dnsmasq
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 32296/cupsd
tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN 1550/postgres
tcp6 0 0 :::80 :::* LISTEN 3198/docker-proxy
Also, ss is the replacement of netstat and takes mostly the same flags, but has a differently formatted output
answered May 29 '18 at 17:37
Bruno9779Bruno9779
1,138515
Did a similar command (netstat -pan -Ainet) that gets the same result:tcp 0 0 0.0.0.0:41673 0.0.0.0:* LISTEN -This does not give any process name nor PID as I get-instead.
– tofcute
May 29 '18 at 21:18
Without sudo it is not similar. You can only see the PID of processes started by your user/groups
– Bruno9779
May 30 '18 at 13:30
Sorry, I forgot thesudoin my comment but I used it on my computer, as well as when usingssandlsof.
– tofcute
May 30 '18 at 17:43
add a comment |
Netstat does exactly what you ask, when run as root and with the correct flags:
sudo netstat -tnlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.1.1:53 0.0.0.0:* LISTEN 1931/dnsmasq
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 32296/cupsd
tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN 1550/postgres
tcp6 0 0 :::80 :::* LISTEN 3198/docker-proxy
Also, ss is the replacement of netstat and takes mostly the same flags, but has a differently formatted output
answered May 29 '18 at 17:37
Bruno9779Bruno9779
1,138515
Did a similar command (netstat -pan -Ainet) that gets the same result:tcp 0 0 0.0.0.0:41673 0.0.0.0:* LISTEN -This does not give any process name nor PID as I get-instead.
– tofcute
May 29 '18 at 21:18
Without sudo it is not similar. You can only see the PID of processes started by your user/groups
– Bruno9779
May 30 '18 at 13:30
Sorry, I forgot thesudoin my comment but I used it on my computer, as well as when usingssandlsof.
– tofcute
May 30 '18 at 17:43
add a comment |
Netstat does exactly what you ask, when run as root and with the correct flags:
sudo netstat -tnlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.1.1:53 0.0.0.0:* LISTEN 1931/dnsmasq
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 32296/cupsd
tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN 1550/postgres
tcp6 0 0 :::80 :::* LISTEN 3198/docker-proxy
Also, ss is the replacement of netstat and takes mostly the same flags, but has a differently formatted output
answered May 29 '18 at 17:37
Bruno9779Bruno9779
1,138515
Netstat does exactly what you ask, when run as root and with the correct flags:
sudo netstat -tnlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.1.1:53 0.0.0.0:* LISTEN 1931/dnsmasq
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 32296/cupsd
tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN 1550/postgres
tcp6 0 0 :::80 :::* LISTEN 3198/docker-proxy
Also, ss is the replacement of netstat and takes mostly the same flags, but has a differently formatted output
answered May 29 '18 at 17:37
Bruno9779Bruno9779
1,138515
edited May 29 '18 at 18:21
answered May 29 '18 at 17:37
Bruno9779Bruno9779
1,138515
answered May 29 '18 at 17:37
Bruno9779Bruno9779
1,138515
answered May 29 '18 at 17:37
Bruno9779Bruno9779
1,138515
1,138515
Did a similar command (netstat -pan -Ainet) that gets the same result:tcp 0 0 0.0.0.0:41673 0.0.0.0:* LISTEN -This does not give any process name nor PID as I get-instead.
– tofcute
May 29 '18 at 21:18
Without sudo it is not similar. You can only see the PID of processes started by your user/groups
– Bruno9779
May 30 '18 at 13:30
Sorry, I forgot thesudoin my comment but I used it on my computer, as well as when usingssandlsof.
– tofcute
May 30 '18 at 17:43
add a comment |
Did a similar command (netstat -pan -Ainet) that gets the same result:tcp 0 0 0.0.0.0:41673 0.0.0.0:* LISTEN -This does not give any process name nor PID as I get-instead.
– tofcute
May 29 '18 at 21:18
Without sudo it is not similar. You can only see the PID of processes started by your user/groups
– Bruno9779
May 30 '18 at 13:30
Sorry, I forgot thesudoin my comment but I used it on my computer, as well as when usingssandlsof.
– tofcute
May 30 '18 at 17:43
Did a similar command (
netstat -pan -Ainet) that gets the same result: tcp 0 0 0.0.0.0:41673 0.0.0.0:* LISTEN - This does not give any process name nor PID as I get - instead.– tofcute
May 29 '18 at 21:18
Did a similar command (
netstat -pan -Ainet) that gets the same result: tcp 0 0 0.0.0.0:41673 0.0.0.0:* LISTEN - This does not give any process name nor PID as I get - instead.– tofcute
May 29 '18 at 21:18
Without sudo it is not similar. You can only see the PID of processes started by your user/groups
– Bruno9779
May 30 '18 at 13:30
Without sudo it is not similar. You can only see the PID of processes started by your user/groups
– Bruno9779
May 30 '18 at 13:30
Sorry, I forgot the
sudo in my comment but I used it on my computer, as well as when using ss and lsof.– tofcute
May 30 '18 at 17:43
Sorry, I forgot the
sudo in my comment but I used it on my computer, as well as when using ss and lsof.– tofcute
May 30 '18 at 17:43
add a comment |
As hinted at, ss can provide the answer as well; the syntax is:
sudo ss --tcp --listening --processes 'sport = 1234'
Where 1234 is the port-of-the-day from your nmap scan. This limits the output to TCP ports and shows the process name and PID that is listening on that port. sudo is only needed if you want the --process flag, which provides the process name and PID.
answered May 29 '18 at 18:40
Jeff SchallerJeff Schaller
43.1k1159137
I din't know the 'sport = <PORT>' trick, I used agrepinstead. Either way, here is what I get:LISTEN 0 64 *:41673 *:*No PID nor Program Name :-(
– tofcute
May 29 '18 at 21:28
Did you run it as root, or with sudo?
– Jeff Schaller
May 29 '18 at 21:53
I ran your command exactly as you gave it, from a user account, using sudo. Why?
– tofcute
May 30 '18 at 10:46
If you ran it without root privileges, you wouldn't be able to see the process name/pid; that could have explained the behavior.
– Jeff Schaller
May 30 '18 at 11:12
add a comment |
As hinted at, ss can provide the answer as well; the syntax is:
sudo ss --tcp --listening --processes 'sport = 1234'
Where 1234 is the port-of-the-day from your nmap scan. This limits the output to TCP ports and shows the process name and PID that is listening on that port. sudo is only needed if you want the --process flag, which provides the process name and PID.
answered May 29 '18 at 18:40
Jeff SchallerJeff Schaller
43.1k1159137
I din't know the 'sport = <PORT>' trick, I used agrepinstead. Either way, here is what I get:LISTEN 0 64 *:41673 *:*No PID nor Program Name :-(
– tofcute
May 29 '18 at 21:28
Did you run it as root, or with sudo?
– Jeff Schaller
May 29 '18 at 21:53
I ran your command exactly as you gave it, from a user account, using sudo. Why?
– tofcute
May 30 '18 at 10:46
If you ran it without root privileges, you wouldn't be able to see the process name/pid; that could have explained the behavior.
– Jeff Schaller
May 30 '18 at 11:12
add a comment |
As hinted at, ss can provide the answer as well; the syntax is:
sudo ss --tcp --listening --processes 'sport = 1234'
Where 1234 is the port-of-the-day from your nmap scan. This limits the output to TCP ports and shows the process name and PID that is listening on that port. sudo is only needed if you want the --process flag, which provides the process name and PID.
answered May 29 '18 at 18:40
Jeff SchallerJeff Schaller
43.1k1159137
As hinted at, ss can provide the answer as well; the syntax is:
sudo ss --tcp --listening --processes 'sport = 1234'
Where 1234 is the port-of-the-day from your nmap scan. This limits the output to TCP ports and shows the process name and PID that is listening on that port. sudo is only needed if you want the --process flag, which provides the process name and PID.
answered May 29 '18 at 18:40
Jeff SchallerJeff Schaller
43.1k1159137
answered May 29 '18 at 18:40
Jeff SchallerJeff Schaller
43.1k1159137
answered May 29 '18 at 18:40
Jeff SchallerJeff Schaller
43.1k1159137
answered May 29 '18 at 18:40
Jeff SchallerJeff Schaller
43.1k1159137
43.1k1159137
I din't know the 'sport = <PORT>' trick, I used agrepinstead. Either way, here is what I get:LISTEN 0 64 *:41673 *:*No PID nor Program Name :-(
– tofcute
May 29 '18 at 21:28
Did you run it as root, or with sudo?
– Jeff Schaller
May 29 '18 at 21:53
I ran your command exactly as you gave it, from a user account, using sudo. Why?
– tofcute
May 30 '18 at 10:46
If you ran it without root privileges, you wouldn't be able to see the process name/pid; that could have explained the behavior.
– Jeff Schaller
May 30 '18 at 11:12
add a comment |
I din't know the 'sport = <PORT>' trick, I used agrepinstead. Either way, here is what I get:LISTEN 0 64 *:41673 *:*No PID nor Program Name :-(
– tofcute
May 29 '18 at 21:28
Did you run it as root, or with sudo?
– Jeff Schaller
May 29 '18 at 21:53
I ran your command exactly as you gave it, from a user account, using sudo. Why?
– tofcute
May 30 '18 at 10:46
If you ran it without root privileges, you wouldn't be able to see the process name/pid; that could have explained the behavior.
– Jeff Schaller
May 30 '18 at 11:12
I din't know the 'sport = <PORT>' trick, I used a
grep instead. Either way, here is what I get: LISTEN 0 64 *:41673 *:* No PID nor Program Name :-(– tofcute
May 29 '18 at 21:28
I din't know the 'sport = <PORT>' trick, I used a
grep instead. Either way, here is what I get: LISTEN 0 64 *:41673 *:* No PID nor Program Name :-(– tofcute
May 29 '18 at 21:28
Did you run it as root, or with sudo?
– Jeff Schaller
May 29 '18 at 21:53
Did you run it as root, or with sudo?
– Jeff Schaller
May 29 '18 at 21:53
I ran your command exactly as you gave it, from a user account, using sudo. Why?
– tofcute
May 30 '18 at 10:46
I ran your command exactly as you gave it, from a user account, using sudo. Why?
– tofcute
May 30 '18 at 10:46
If you ran it without root privileges, you wouldn't be able to see the process name/pid; that could have explained the behavior.
– Jeff Schaller
May 30 '18 at 11:12
If you ran it without root privileges, you wouldn't be able to see the process name/pid; that could have explained the behavior.
– Jeff Schaller
May 30 '18 at 11:12
add a comment |
Some ports opened by the kernel and by some specific services (NFS, OCFS, ssh tunnels) are not visible with netstat nor ss
answered May 30 '18 at 14:33
Bruno9779Bruno9779
1,138515
add a comment |
Some ports opened by the kernel and by some specific services (NFS, OCFS, ssh tunnels) are not visible with netstat nor ss
answered May 30 '18 at 14:33
Bruno9779Bruno9779
1,138515
add a comment |
Some ports opened by the kernel and by some specific services (NFS, OCFS, ssh tunnels) are not visible with netstat nor ss
answered May 30 '18 at 14:33
Bruno9779Bruno9779
1,138515
Some ports opened by the kernel and by some specific services (NFS, OCFS, ssh tunnels) are not visible with netstat nor ss
answered May 30 '18 at 14:33
Bruno9779Bruno9779
1,138515
answered May 30 '18 at 14:33
Bruno9779Bruno9779
1,138515
answered May 30 '18 at 14:33
Bruno9779Bruno9779
1,138515
answered May 30 '18 at 14:33
Bruno9779Bruno9779
1,138515
1,138515
add a comment |
add a comment |
I do have same problem for application , port is in listening state but process id is not showing up. please help me. used below commands. this is cloud aws server redhat linux.
netstat -tulpn
tcp 0 0 0.0.0.0:8008 0.0.0.0:* LISTEN -
netstat -ltpnae | awk 'NR==2 || /:8008/'
Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
tcp 0 0 0.0.0.0:8008 0.0.0.0:* LISTEN 0 142518 -
lsof | awk 'NR==1 || /142518/'
COMMAND PID TID USER FD TYPE DEVICE SIZE/OFF NODE NAME
answered 6 mins ago
vamshivamshi
1
New contributor
vamshi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I do have same problem for application , port is in listening state but process id is not showing up. please help me. used below commands. this is cloud aws server redhat linux.
netstat -tulpn
tcp 0 0 0.0.0.0:8008 0.0.0.0:* LISTEN -
netstat -ltpnae | awk 'NR==2 || /:8008/'
Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
tcp 0 0 0.0.0.0:8008 0.0.0.0:* LISTEN 0 142518 -
lsof | awk 'NR==1 || /142518/'
COMMAND PID TID USER FD TYPE DEVICE SIZE/OFF NODE NAME
answered 6 mins ago
vamshivamshi
1
New contributor
vamshi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I do have same problem for application , port is in listening state but process id is not showing up. please help me. used below commands. this is cloud aws server redhat linux.
netstat -tulpn
tcp 0 0 0.0.0.0:8008 0.0.0.0:* LISTEN -
netstat -ltpnae | awk 'NR==2 || /:8008/'
Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
tcp 0 0 0.0.0.0:8008 0.0.0.0:* LISTEN 0 142518 -
lsof | awk 'NR==1 || /142518/'
COMMAND PID TID USER FD TYPE DEVICE SIZE/OFF NODE NAME
answered 6 mins ago
vamshivamshi
1
New contributor
vamshi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I do have same problem for application , port is in listening state but process id is not showing up. please help me. used below commands. this is cloud aws server redhat linux.
netstat -tulpn
tcp 0 0 0.0.0.0:8008 0.0.0.0:* LISTEN -
netstat -ltpnae | awk 'NR==2 || /:8008/'
Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
tcp 0 0 0.0.0.0:8008 0.0.0.0:* LISTEN 0 142518 -
lsof | awk 'NR==1 || /142518/'
COMMAND PID TID USER FD TYPE DEVICE SIZE/OFF NODE NAME
answered 6 mins ago
vamshivamshi
1
New contributor
vamshi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 6 mins ago
vamshivamshi
1
New contributor
vamshi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 6 mins ago
vamshivamshi
1
answered 6 mins ago
vamshivamshi
1
1
New contributor
vamshi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
vamshi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
vamshi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f446745%2fport-open-listen-but-no-associated-process%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Could it potentially be that you've got malware, which masks itself with
-as name ? Consider tryingpgrep "-". Also, trylsofstackoverflow.com/a/319997/3701431– Sergiy Kolodyazhnyy
May 30 '18 at 0:28
If any of the answers solved your problem, please accept it by clicking the checkmark next to it. Thank you!
– Jeff Schaller
Jun 3 '18 at 11:24