943

I tried to close the tomcat using ./shutdown.sh from tomcat /bin directory. But found that the server was not closed properly. And thus I was unable to restart
My tomcat is running on port 8080.

I want to kill the tomcat process running on 8080. I first want to have the list of processes running on a specific port (8080) in order to select which process to kill.

Elrond_EGLDer
  • 47,430
  • 25
  • 189
  • 180
veer7
  • 14,540
  • 8
  • 37
  • 62

30 Answers30

1155

This fuser 8080/tcp will print you PID of process bound on that port.

And this fuser -k 8080/tcp will kill that process.

Works on Linux only. More universal is use of lsof -i4 (or 6 for IPv6).

Szymon
  • 41,313
  • 16
  • 90
  • 109
nudzo
  • 12,086
  • 2
  • 15
  • 18
  • 2
    does this close a possible connected socket to 8080 as well? – fer y Jan 28 '14 at 13:26
  • Of course, all file descriptors are closed when proces finish. – nudzo Jan 28 '14 at 22:34
  • 12
    It does not properly close the port. The port is put into TIME_WAIT state after the parent process is killed. The OS will then eventually completely close the port after about 60 seconds. It means that you can't reuse the port for at least 60 seconds (unless you give the reuse option to the socket). – Mark Lakata Sep 03 '15 at 22:44
  • 2
    On Darwin, must be using a different version of `fuser`. Only takes a file, doesn't support `-k`. – a p Nov 15 '16 at 19:04
  • 3
    'fuser -k -n tcp 8080' will kill the process too – Hesham Yassin Feb 09 '17 at 16:49
  • 8
    @dbliss fuser is part of psmisc. In case you get `fuser: command not found`, install psmisc. For CentOS/RHEL 7, run `sudo yum install psmisc` – Tom Jan 10 '19 at 17:12
866

To list any process listening to the port 8080:

lsof -i:8080

To kill any process listening to the port 8080:

kill $(lsof -t -i:8080)

or more violently:

kill -9 $(lsof -t -i:8080)

(-9 corresponds to the SIGKILL - terminate immediately/hard kill signal: see List of Kill Signals and What is the purpose of the -9 option in the kill command?. If no signal is specified to kill, the TERM signal a.k.a. -15 or soft kill is sent, which sometimes isn't enough to kill a process.).

Franck Dernoncourt
  • 62,576
  • 61
  • 286
  • 446
  • 10
    kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] This is what I am getting when I Execute your commands – Sudhir Belagali Apr 05 '17 at 06:49
  • 2
    @SudhirBelagali did you it with super user `sudo` – Marcel Djaman May 11 '17 at 14:43
  • 8
    Worked on my Mac as well – asherbar Jan 07 '18 at 09:48
  • 2
    I would like to add that sometimes you do not have permissions to see the process id, in that case you need to do `sudo lsof -i:8080`. – Akavall Aug 19 '18 at 16:21
  • 1
    why the second tips is more violent ? – Webwoman Sep 17 '18 at 12:11
  • @Webman more violently means it kills my web browser at well :( Here is the best solution from Gal Bracha: kill -9 $(lsof -t -i:3000 -sTCP:LISTEN) – Russo Sep 20 '18 at 11:34
  • @Webman `-9` corresponds to `SIGKILL - terminate immediately/hard kill`: see [List of Kill Signals](https://unix.stackexchange.com/q/317492/16704) and [What is the purpose of the -9 option in the kill command?](https://askubuntu.com/q/184071/44876)) – Franck Dernoncourt Sep 20 '18 at 11:44
  • based on this, with sudo: `killport() {sudo kill -9 $(sudo lsof -t -i:${1} -sTCP:LISTEN)}` and then killport 8080 – Nicolas Marshall Jan 07 '19 at 21:53
311

Use the command

 sudo netstat -plten |grep java

used grep java as tomcat uses java as their processes.

It will show the list of processes with port number and process id

tcp6       0      0 :::8080                 :::*                    LISTEN      
1000       30070621    16085/java

the number before /java is a process id. Now use kill command to kill the process

kill -9 16085

-9 implies the process will be killed forcefully.

veer7
  • 14,540
  • 8
  • 37
  • 62
  • 11
    You might want to add that one might need root privilegues to get process names via `netstat`. – Jonas Schäfer Jul 20 '12 at 16:46
  • 2
    @JonasWielicki you can see the ones you own w/out root privileges. – dbliss Aug 09 '16 at 04:27
  • I needed root privileges for netstat. Is there a way to actually know what the process came from? As far as I could tell I had closed all applications but it may have been from a terminal window where I inadvertently pushed the processes to a background task. Maybe I should have ran the terminal command 'ps' to see all processes first... – JesseBoyd Oct 12 '17 at 02:00
  • `sudo netstat -plten | grep :8080` will work even when you do not know the application. This found a ruby process that `lsof -i` did not find for me. – MikeF Oct 01 '20 at 17:04
202

A One-liner to kill only LISTEN on specific port:

kill -9 $(lsof -t -i:3000 -sTCP:LISTEN)

Gal Bracha
  • 14,231
  • 9
  • 61
  • 77
  • 10
    I think this should be the best answer. Thanks @Gal Bracha – Sam Kah Chiin Feb 22 '18 at 08:46
  • 3
    This is the best solution because it does not kill my browser as well! – Russo Sep 20 '18 at 11:31
  • Based on this answer I created a function into `~/.bashrc`: `killp() { kill -9 $(lsof -t -i:"$1" -sTCP:LISTEN) }` in order to be able to use it like this `killp 3000`. (Do not forget to add new lines for `{ }`) – Arthur Aug 06 '20 at 18:11
129

You can use the lsof command. Let port number like here is 8090

lsof -i:8090

This command returns a list of open processes on this port.

Something like…

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
ssh 75782 eoin 5u IPv6 0x01c1c234 0t0 TCP localhost:8090 (LISTEN)

To free the port, kill the process using it(the process id is 75782)…

kill -9 75782

This one worked for me. here is the link from the original post: link

Kop4lyf
  • 4,192
  • 1
  • 22
  • 30
  • 1
    to kill process forcefully you will need to use -9 like kill -9 75782; as sometimes few processes aren't kill with just kill – veer7 Feb 25 '15 at 09:58
111

One liner

kill -9 $(lsof -t -i tcp:8080)

explanation here: use a combination of lsof and kill

root@localhost:~# lsof -i tcp:8080
COMMAND   PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
java    23672 sine  238u  IPv6 3028222      0t0  TCP localhost:http-alt (LISTEN)

select pid and use kill

kill 23672
dlmeetei
  • 7,297
  • 3
  • 25
  • 34
82

If you want to kill a process running on port number 8080 then first you need to find the 8080 port process identification number(PID) and then kill it. Run the following command to find 8080 port number PID:

sudo lsof -t -i:8080

Here,

  • sudo - command to ask admin privilege(user id and password).
  • lsof - list of files(Also used for to list related processes)
  • -t - show only process ID
  • -i - show only internet connections related process
  • :8080 - show only processes in this port number

So you can now easily kill your PID using following command:

sudo kill -9 <PID>

Here,

  • kill - command to kill the process
  • -9 - forcefully

You can use one command to to kill a process on a specific port using the following command:

sudo kill -9 $(sudo lsof -t -i:8080)

For more you can see the following link How to kill a process on a specific port on linux

Mahfuz
  • 1,115
  • 1
  • 12
  • 15
75

Best way to kill all processes on a specific port;

kill -9 $(sudo lsof -t -i:8080)
45

This prints to stdout the process ids of everything running on <port_number>:

fuser -n tcp <port_number> 

It also prints some stuff to stderr, so:

fuser -n tcp <port_number> 2> /dev/null

We can then supply these process ids to the kill command:

sudo kill $(fuser -n tcp <port_number> 2> /dev/null)

You could also put this in a function if you do it a lot:

function killport() {
    sudo kill $(fuser -n tcp $1 2> /dev/null)
}
Brian Peterson
  • 2,676
  • 5
  • 25
  • 33
38

To know the pid of service running on particular port :

netstat -tulnap | grep :*port_num*

you will get the description of that process. Now use kill or kill -9 pid. Easily killed.

e.g

netstat -ap | grep :8080

tcp6       0      0 :::8080       :::*    LISTEN      1880/java 

Now:

kill -9 1880

Remember to run all commands as root

Ritesh Sinha
  • 791
  • 3
  • 18
  • 47
Sanjay s.
  • 481
  • 4
  • 6
37

Get the PID of the task and kill it.

lsof -ti:8080 | xargs kill
Rahul Garg
  • 3,385
  • 29
  • 29
26

try like this,

 sudo fuser -n tcp -k 8080
Adil Abbasi
  • 2,857
  • 1
  • 35
  • 32
22

First you need to do is run (replace with your port number):

fuser -k 3000/tcp

This will release the port. After you run the above command run:

service docker restart

And your problem is resolved.

arximughal
  • 273
  • 3
  • 16
19

Choose the port number and apply the grep in netstat command as shown below

netstat -ap | grep :7070

Console Output

tcp 0 0 :::7070 :::* LISTEN 3332/java

Kill the service based on PID ( Process Identification Number )

kill -9 3332
albert
  • 7,915
  • 3
  • 42
  • 62
Lova Chittumuri
  • 2,014
  • 1
  • 20
  • 25
14
  1. lsof -i tcp:8000 This command lists the information about process running in port 8000

  2. kill -9 [PID] This command kills the process

AboulEinein
  • 1,020
  • 3
  • 13
  • 26
  • I just noticed that I downvoted this by accident a few weeks ago, if you edit your anwer slightly I should be able to remove it – Robin-Hoodie Jan 11 '18 at 09:26
13

Linux: You can use this command if you know the port :

netstat -plten | grep LISTEN | grep 8080

AIX:

netstat -Aan | grep LISTEN | grep 8080

You then take the first column (example: f100050000b05bb8) and run the following command:

rmsock f100050000b05bb8 tcpcb

kill process.

ben rhouma moez
  • 658
  • 9
  • 15
13

Linux: First you can find PID of this command if you know the port :

netstat -tulpn 

example:-

 Local Address  Foreign Address  State    PID/Program name

  :::3000       :::*             LISTEN    15986/node 

You then take the kill process. run the following command:

kill -9 PID

Expample: -

kill -9 15986

Kundan Kumar
  • 131
  • 1
  • 3
12

You can know list of all ports running in system along with its details (pid, address etc.) :

netstat -tulpn

You can know details of a particular port number by providing port number in following command :

sudo netstat -lutnp | grep -w '{port_number}'

ex: sudo netstat -lutnp | grep -w '8080' Details will be provided like this :

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name

if you want to kill a process using pid then : kill -9 {PID}

if you want to kill a process using port number : fuser -n tcp {port_number}

use sudo if you are not able to access any.

YAP
  • 306
  • 3
  • 5
9

Run the following command to find 8080 port number PID:

sudo lsof -t -i:8080

You can now easily kill your PID using following command:

sudo kill -9

You can use one command to to kill a process on a specific port using the following command:

sudo kill -9 $(sudo lsof -t -i:8000)

RajuS
  • 101
  • 1
  • 2
6

kill -9 `fuser 8080/tcp|xargs -n 1`, this commands also kills the process that listens on port 8080 with TCP connection

Harshit Garg
  • 1,489
  • 17
  • 19
6

Simply run this command. Don't forget to replace portnumber, with your port ;)

  kill -9 $(sudo lsof -t -i:portnumber)
monica
  • 1,446
  • 12
  • 25
4
sudo apt-get install psmisc (or sudo yum install psmisc)
sudo fuser 80/tcp

Result: 80/tcp: 1858 1867 1868 1869 1871

Kill process one by one

kill -9 1858

Fadid
  • 1,092
  • 13
  • 15
4

This is the solution for Windows:

C:\Users\Niroshan>netstat -ano|findstr "PID :8080"

Proto Local Address Foreign Address State PID
TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING 18264

taskkill /pid 18264 /f
Michael
  • 2,758
  • 6
  • 28
  • 55
Niroshan Ratnayake
  • 932
  • 1
  • 7
  • 13
3

I'm working on a Yocto Linux system that has a limited set of available Linux tools. I wanted to kill the process that was using a particular port (1883).

First, to see what ports we are listening to I used the following command:

root@root:~# netstat -lt
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       
tcp        0      0 0.0.0.0:hostmon         0.0.0.0:*               LISTEN      
tcp        0      0 localhost.localdomain:domain 0.0.0.0:*               LISTEN      
tcp        0      0 0.0.0.0:9080            0.0.0.0:*               LISTEN      
tcp        0      0 0.0.0.0:1883            0.0.0.0:*               LISTEN      
tcp        0      0 :::hostmon              :::*                    LISTEN      
tcp        0      0 localhost:domain        :::*                    LISTEN      
tcp        0      0 :::ssh                  :::*                    LISTEN      
tcp        0      0 :::1883                 :::*                    LISTEN      

Next, I found the name of the process using port 1883 in the following way:

root@root:~# fuser 1883/tcp
290 
root@root:~# ps | grep 290
  290 mosquitt 25508 S    /usr/sbin/mosquitto -c /etc/mosquitto/mosquitto.conf
12141 root      8444 S    grep 290

As we can see above, it's the program /usr/sbin/mosquitto that's using port 1883.

Lastly, I killed the process:

root@root:~# systemctl stop mosquitto

I used systemctl becuase in this case it was a systemd service.

Daniel Jonsson
  • 2,483
  • 3
  • 36
  • 58
2

Other way with Git Bash:

stopProcessByPortNumber() {
port=":${1}"
portStrLine="$(netstat -ano | findstr LISTENING | findstr $port)"
processId="$(grep -oP '(\d+)(?!.*\d)' <<< $portStrLine)"
echo $processId
taskkill -PID $processId -F
}
2

In my case cent os has some issue in suggested answer. So I used following solution :

  ss -tanp | grep 65432 | head -1 | grep -Po "(?<=pid=).*(?=,)" | xargs kill
Kamesh Jungi
  • 5,684
  • 5
  • 35
  • 48
2
  1. first check the process netstat -lt
  2. check process id fuser <port number>/tcp
  3. kill the process running on the port kill <process id>
Gunjan Paul
  • 315
  • 2
  • 9
1

to build on what @veer7 said:

if you want to know what was on the port, do this before you kill it.

$ sudo netstat -plten |grep java
tcp6       0      0 127.0.0.1:8005          :::*                    LISTEN      1000       906726      25296/java      
tcp6       0      0 :::8009                 :::*                    LISTEN      1000       907503      25296/java      
tcp6       0      0 :::8080                 :::*                    LISTEN      1000       907499      25296/java      
$ ps 25296
  PID TTY      STAT   TIME COMMAND
25296 ?        Sl     0:16 /usr/lib/jvm/java-8-openjdk-amd64/bin/java -Dcatalina.base=/hom

Use 'ps' and the number of the process that netstat reported back

JesseBoyd
  • 756
  • 1
  • 9
  • 17
0

How to kill process if the service on the port is not responding

timeout 1 telnet localhost 8080 2>&1 | if grep -q 'Unable'; then sudo kill -9 $(sudo lsof -t -i:8080); fi

What it does

  1. Start 'timeout' with one second, to make telnet exit
  2. ' 2>&1 | ' pipe error-message without exiting
  3. If error-message contains 'Unable', then run the kode to kill process locking port 8080

This can ble placed in a file and run regulary from 'sudo crontab'

Punnerud
  • 3,630
  • 1
  • 36
  • 32
-2

In Windows, it will be netstat -ano | grep "8080" and we get the following message TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING 10076

WE can kill the PID using taskkill /F /PID 10076

nifCody
  • 2,061
  • 3
  • 22
  • 48
Chaklader
  • 149
  • 1
  • 2
  • 15