Find (and kill) process locking port 3000 on Mac

Question

How do I find (and kill) processes that listen to/use my tcp ports? I'm on mac os x.

Sometimes, after a crash or some bug, my rails app is locking port 3000. I can't find it using ps -ef...

When doing

rails server

I get

Address already in use - bind(2) (Errno::EADDRINUSE)

2014 update:

To complete some of the answers below: After executing the kill commands, deleting the pid file might be necessary rm ~/mypath/myrailsapp/tmp/pids/server.pid

A very neat solution to kill a process on ANY user-specified port can be found in @Kevin Suttle's answer below. Reproduced here for posterity: `function killport() { lsof -i TCP:$1 | grep LISTEN | awk '{print $2}' | xargs kill -9 }` — user456584, Jan 17 '14 at 18:39
@user456584 's comment above should be the accepted answer ^^^ That function worked to kill the _many_ processes i had running on a port — Aneuway, Jun 19 '19 at 15:12
works after finding processes with netstat and killing the process with kill -9 command! — Gaurav, Apr 08 '21 at 15:39

score 3586 · Accepted Answer · edited Nov 06 '20 at 19:28

3586

You can try netstat
```
 netstat -vanp tcp | grep 3000
```
For macOS El Capitan and newer (or if your netstat doesn't support -p), use lsof
```
 lsof -i tcp:3000 
```
For Centos 7 use:
```
 netstat -vanp --tcp | grep 3000
```

edited Nov 06 '20 at 19:28

Frenchcooc

469
3
13

answered Oct 04 '10 at 12:48

ghostdog74

286,686
52
238
332

34

Thank you! Your answer gave birth to my "death_to 'port'" script. (#!/usr/bin/ruby `lsof -t -i tcp:#{ARGV.first} | xargs kill`) – Sv1 Oct 02 '13 at 18:40
243

The "terse" flag to lsof produces output suitable for piping to a subsequent kill: `lsof -t -i tcp:1234 | xargs kill` – Manav Jan 07 '14 at 04:58
If you want to know what the process is before you kill it, `ps xp `. It's always nice to find out the root cause of port conflicts. – Dave Ceddia Apr 15 '15 at 18:25
1

If you only want to look for/kill *listening* processes, use `lsof -n -i4TCP:8001 -sTCP:LISTEN -t | xargs kill`. I found that if I did it without the `LISTEN` it would often kill my browser as well as a locked development server process, as the browser was also using the development port. – awidgery Jul 15 '15 at 13:48
9

I have put this into my `~/.bash_profile`: `findandkill() { port=$(lsof -n -i4TCP:$1 | grep LISTEN | awk '{ print $2 }') kill -9 $port } alias killport=findandkill` So now I just have to type `killport 8080` and it saves me some seconds – Alfonso Pérez Nov 11 '15 at 13:51
7

Another tip is to add `-P` to the `lsof` command so that the raw port is visible in the output: `lsof -P -i:3000` – Jason Axelson Jul 22 '16 at 02:06
on mac `lsof` is on `/usr/sbin` directory which is not in `PATH` by default. – artronics Feb 14 '17 at 18:21
@oma if you run the netstat command without the grep, you'll get the column names. – Will Munn Apr 20 '17 at 15:53
1

netstat -tulpn | grep 3000 Then kill the process id kill -9 id – Jun 20 '19 at 11:27
Just curious but could `netstat -vanp tcp | grep 3000` sometimes return spurious results since `3000` could be present in a pid or ip? (sorry, not hugely knowledgable and hence not sure) – stevec Jan 14 '20 at 03:31
4

This post is only half the answer – png Mar 24 '20 at 17:10

score 2248 · Answer 2 · edited Nov 23 '19 at 17:22

2248

Find:

sudo lsof -i :3000

Kill:

kill -9 <PID>

edited Nov 23 '19 at 17:22

Zameer Ansari

23,672
19
120
191

answered Sep 09 '13 at 20:58

Filip Spiridonov

24,912
4
22
29

68

Sometimes **lsof -i :port** will show nothing. try **sudo lsof -i :port**. – kilik52 Jan 30 '14 at 12:05
40

Recommend trying `kill -15 ` before resorting to `-9` for safety. – Jamon Holmgren Aug 16 '15 at 23:55
8

@Jamon Holmgren why? what do both do? and why is a ```kill ``` not sufficient / dangerous / incomplete? – Michael Trouw Nov 24 '15 at 12:45
18

@MichaelTrouw almost a year later, but here's your answer. :-) http://unix.stackexchange.com/a/8918 TL;DR `kill -15` gives the process a chance to clean up after itself. – Jamon Holmgren Oct 12 '16 at 05:57
22

I think this answer should say what `-9` does. – Joseph Fraley Jan 17 '17 at 19:13
7

Please don't just use `kill -9` without thinking twice, and trying other signals first. It will cause a process to exit immediately, without cleaning up after itself, possibly leaving a mess behind or leaving databases in inconsistent state... Try a TERM (default for `kill`, no flag needed) or QUIT (`kill -3 pid`) first at least, and check what process you are dealing with before sending a KILL. – niels Jan 26 '17 at 11:58
1

That cleanup is important for Java processes, I just experienced. Restarting my machine fixed the problem after killing with -9. Will be trying -15 next. – Beez Sep 12 '18 at 19:18
1

@MichaelTrouw kill command's [Man page](https://ss64.com/osx/kill.html) says that "-15" means "Termination signal - allow an orderly shutdown", whereas "-9" means "Kill signal". – Sufian Oct 18 '18 at 09:12
When I use `kill -9 `, show error `kill: kill failed: operation not permitted`. solution is add sudo in the front. `sudo kill -9 ` – Zgpeace Jan 29 '20 at 01:39
Kill:sudo kill No need of -9 – Amisha Mar 31 '20 at 05:32
how come it is not marked as the right answer, it's the fastest way to do it – Dr. Freddy Dimethyltryptamine May 28 '20 at 10:23
Please edit the answer and add an explanation for what `-9` does. I see some comments suggest `-15`, and an explanation will definitely be benefit others. Thanks! – themthem Apr 16 '21 at 05:37

Abhijith Sasikumar · Answer 3 · 2021-04-21T16:37:47.997

291

Quick and easiest solution:

kill $(lsof -ti:3000,3001)

For single port:

kill $(lsof -ti:3000)

#3000 is the port to be freed

Kill multiple ports with single line command:

kill $(lsof -ti:3000,3001)

#here multiple ports 3000 and 3001 are the ports to be freed

lsof -ti:3000

82500 (Process ID)

lsof -ti:3001

82499

lsof -ti:3001,3000

82499 82500

kill $(lsof -ti:3001,3000)

Terminates both 82499 and 82500 processes in a single command.

For using this in package.json scripts:

"scripts": { "start": "kill $(lsof -ti:3000,3001) && npm start" }

edited Apr 21 '21 at 16:37

answered Mar 12 '19 at 07:02

Abhijith Sasikumar

4,490
4
24
37

3

Glad it helped. – Abhijith Sasikumar Dec 13 '19 at 15:07
4

This is truly simple and actually worked. Big thanks. – Tyler Bean Sep 29 '20 at 03:14

score 250 · Answer 4 · edited Oct 25 '16 at 05:45

250

Nothing above worked for me. Anyone else with my experience could try the following (worked for me):

Run:

lsof -i :3000 (where 3000 is your current port in use)

then check status of the reported PID :

ps ax | grep <PID>

finally, "begone with it":

kill -QUIT <PID>

edited Oct 25 '16 at 05:45

jmort253

32,054
10
92
114

answered Mar 07 '13 at 20:24

Austin

2,936
2
14
16

24

This actually seems a better answer than the one give much later by Filip Spiridonov, which has 277 upvotes against your 9. Yours was 6 months earlier, and has the same information with a bit more explanation. There is no justice... – Floris Dec 30 '15 at 22:15
Try `kill -TERM` (or just `kill`) before `kill -QUIT`. Not every process is going to do an orderly shutdown on SIGQUIT. – craig65535 Jan 21 '20 at 00:09

score 178 · Answer 5 · answered Aug 05 '16 at 21:03

178

A one-liner to extract the PID of the process using port 3000 and kill it.

lsof -ti:3000 | xargs kill

The -t flag removes everything but the PID from the lsof output, making it easy to kill it.

answered Aug 05 '16 at 21:03

Zlemini

3,835
2
15
19

13

You can filter out "listening" ports with: `lsof -ti:3000 -sTCP:LISTEN` – Zlemini May 22 '18 at 21:58
1

This method works best for me. Simple one liner that clears the busy port. Thanks! – Ryan Trainor Dec 03 '19 at 20:34

Bruno Lemos · Answer 6 · 2021-04-19T22:20:46.633

147

This single command line is easy to remember:

npx kill-port 3000

You can also kill multiple ports at once:

npx kill-port 3000 3001 3002

For a more powerful tool with search:

npx fkill-cli

PS: They use third party javascript packages. npx comes built in with Node.js.

Sources: tweet | github

edited Apr 19 '21 at 22:20

answered Jul 01 '18 at 22:03

Bruno Lemos

6,856
5
32
45

Can you share details on installing npx using brew? I tried installing it on my Mac High Sierra, 10.13.3 and it won't work. – realPK Oct 11 '18 at 22:44
@realPK `npx` comes with `npm` which comes with `node.js`, so it's not a separated package. Just upgrade your node.js and your npm versions. – Bruno Lemos Oct 12 '18 at 08:40
I do Java mostly, haven't exposed myself to Node yet. I found a different way of killing service running on port. TY for responding. – realPK Oct 13 '18 at 22:58
7

The need for NodeJS and JavaScript, to kill something running on port 3000 probably rails... seems like too much overhead to me. adding a simple line to your .bashrc or .zshrc with an alias would solve it without the need for the internet. alias kill3000='lsof -ti:3000 | xargs kill' then you can do: kill3000 – Khalil Gharbaoui Jan 09 '19 at 11:19
this works flawlessly Bruno! – Gaurav May 05 '21 at 15:30

score 120 · Answer 7 · edited Jul 01 '13 at 01:23

120

You can use lsof -i:3000.

That is "List Open Files". This gives you a list of the processes and which files and ports they use.

edited Jul 01 '13 at 01:23

alex

438,662
188
837
957

answered Oct 04 '10 at 12:36

DerMike

13,362
12
45
60

score 63 · Answer 8 · edited Jul 26 '13 at 01:20

63

In your .bash_profile, create a shortcut for terminate the 3000 process:

terminate(){
  lsof -P | grep ':3000' | awk '{print $2}' | xargs kill -9 
}

Then, call $terminate if it's blocked.

edited Jul 26 '13 at 01:20

alex

438,662
188
837
957

answered May 16 '13 at 09:17

alexzg

795
7
8

14

You can make this flexible enough for any port: https://github.com/kevinSuttle/dotfiles/commit/9458141f40094d96952adc7c423cbdddeb909a81 – Kevin Suttle Dec 30 '13 at 02:53
And such a descriptive name =p – Michael Peterson Mar 06 '17 at 13:19
I have something similar to this but I pass in the port. I named my function KP for kill port. – Joseph Chambers Jul 26 '18 at 08:22

Tadele Ayelegn · Answer 9 · 2021-03-11T23:59:11.857

63

To forcefully kill a process like that, use the following command

lsof -n -i4TCP:3000  

OR lsof -i:3000

Where 3000 is the port number the process is running at

this returns the process id(PID) and run

kill -9 "PID"

Replace PID with the number you get after running the first command

edited Mar 11 '21 at 23:59

answered Dec 28 '17 at 04:21

Tadele Ayelegn

3,228
1
25
24

I tried creating an alias in ZSH: alias port="lsof -n -i4TCP:$1" and got the following error... How to achieve this? $ port 8080 lsof: unacceptable port specification in: -i 4TCP: – fotoflo Dec 14 '20 at 10:43

score 45 · Answer 10 · answered Mar 17 '20 at 08:57

45

To kill multi ports.

$ npx kill-port 3000 8080 8081

Process on port 3000 killed
Process on port 8080 killed
Process on port 8081 killed

Hope this help!

answered Mar 17 '20 at 08:57

Binh Ho

1,260
1
9
13

score 44 · Answer 11 · answered Aug 03 '12 at 21:14

44

lsof -P | grep ':3000' | awk '{print $2}'

This will give you just the pid, tested on MacOS.

answered Aug 03 '12 at 21:14

Kris

16,882
6
79
99

12

on MAC kill all pids on port 3000: lsof -P | grep ':3000' | awk '{print $2}' | xargs kill -9 – mike clagg May 13 '13 at 21:18
1

can more than one process listen to the same port? – Kris May 15 '13 at 16:16
Our rails app spawns workers which are child processes, and I have to use this to kill orphaned workers – mike clagg May 15 '13 at 18:19
2

this also kills webbrowsers connecting to port – fjsj Apr 27 '15 at 15:06
6

Here is working one: `lsof -n -iTCP:3407 -sTCP:LISTEN -n -l -P | grep 'LISTEN' | awk '{print $2}' | xargs kill -9` – bob May 23 '16 at 11:19

score 32 · Answer 12 · answered Jun 23 '16 at 18:15

32

Execute in command line on OS-X El Captain:

kill -kill `lsof -t -i tcp:3000`

Terse option of lsof returns just the PID.

answered Jun 23 '16 at 18:15

JE42

4,152
4
36
48

YBathia · Answer 13 · 2017-07-25T22:59:08.190

31

One of the ways to kill a process on a port is to use the python library: freeport (https://pypi.python.org/pypi/freeport/0.1.9) . Once installed, simply:

# install freeport
pip install freeport

# Once freeport is installed, use it as follows
$ freeport 3000
Port 3000 is free. Process 16130 killed successfully

edited Jul 25 '17 at 22:59

answered Feb 12 '16 at 22:14

YBathia

832
7
17

7

That's, by far, NOT the simplest way. The upvoted replies don't require you to download and install anything. – Greg Pasquariello May 25 '16 at 19:20
4

When the prerequisites are met this is so simple and easy to remember. We have a different definition of "simplest" and this answer is perfectly valid and appropriate. Maybe it's just missing the instructions to install freeport with pip. – Cyril Duchon-Doris Jul 19 '17 at 15:18
under the hood, freeport is just a wrapper that calls `lsof -t -i:3000`.. seems unnecessary. – Corey Goldberg Nov 16 '18 at 17:01
This solution is not the easiest, but it complies 100% with what the OP asked... So it is in deed valid AF – danielrvt Nov 21 '18 at 15:11

score 28 · Answer 14 · answered Sep 12 '18 at 04:36

28

To view the processes blocking the port:

netstat -vanp tcp | grep 3000

To Kill the processes blocking the port:

kill $(lsof -t -i :3000)

answered Sep 12 '18 at 04:36

Henry

16,294
7
56
86

This won't work on a Mac machine, returns the following: `kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]` It will, however, work in most linux distros – Milan Velebit Sep 19 '18 at 12:08
1

@MilanVelebit Actually it works perfectly in my Mac machine (Sierra). It works fine if your port `3000` is occupied. However if no processes is blocking the port, then you will get `kill: not enough arguments` error. – Henry Sep 19 '18 at 14:24
That's just weird, I've two Macs (both High Sierra tho), I remember running those commands on both of them (old habits) and I know for certain that they don't run. I've just tried it again on my machine, knowing that the port is occupied, same error. :/ – Milan Velebit Sep 19 '18 at 14:33
Did you get a valid PID on running `netstat -vanp tcp | grep 3000`, for your port that's occupied? – Henry Sep 19 '18 at 14:46
I ran a `lsof -i :portname`, returned the process. Same goes for the `netstat` command, both output the process occupying the port correctly. – Milan Velebit Sep 19 '18 at 14:49
1

I tried it in both `bash` and `zsh` shell. Works fine for me. Not sure why it's not working for you. May be some thing to with High Sierra? I have no idea :/ – Henry Sep 19 '18 at 15:27

score 24 · Answer 15 · answered Jul 17 '16 at 11:10

24

Find the open connection

lsof -i -P | grep -i "listen"

Kill by process ID

kill -9 'PID'

answered Jul 17 '16 at 11:10

Sourabh Bhagat

1,556
12
20

score 24 · Answer 16 · answered Aug 28 '18 at 06:26

24

Find and kill:

This single command line is easy and works correctly.

kill -9 $(lsof -ti tcp:3000)

answered Aug 28 '18 at 06:26

Dylan Breugne

417
3
6

score 15 · Answer 17 · answered Jan 29 '17 at 11:34

Possible ways to achieve this:

top

The top command is the traditional way to view your system’s resource usage and see the processes that are taking up the most system resources. Top displays a list of processes, with the ones using the most CPU at the top.

ps

The ps command lists running processes. The following command lists all processes running on your system:

ps -A

You could also pipe the output through grep to search for a specific process without using any other commands. The following command would search for the Firefox process:

ps -A | grep firefox

The most common way of passing signals to a program is with the kill command.

kill PID_of_target_process

lsof

List of all open files and the processes that opened them.

lsof -i -P | grep -i "listen"
kill -9 PID

or

 lsof -i tcp:3000

score 12 · Answer 18 · answered May 16 '19 at 10:48

12

lsof -i tcp:port_number - will list the process running on that port

kill -9 PID - will kill the process

in your case, it will be

lsof -i tcp:3000 from your terminal find the PID of process

kill -9 PID

answered May 16 '19 at 10:48

Shan

501
5
19

score 12 · Answer 19 · edited Aug 23 '19 at 12:10

12

These two commands will help you find and kill server process

lsof -wni tcp:3000

kill -9 pid

edited Aug 23 '19 at 12:10

Akj

6,086
3
23
33

answered Aug 23 '19 at 09:42

Saif chaudhry

368
2
9

My pleasure, Aashiah – Saif chaudhry Aug 24 '19 at 15:16

Caleb Keene · Answer 20 · 2018-06-20T03:26:01.393

10

I made a little function for this, add it to your rc file (.bashrc, .zshrc or whatever)

function kill-by-port {
  if [ "$1" != "" ]
  then
    kill -9 $(lsof -ni tcp:"$1" | awk 'FNR==2{print $2}')
  else
    echo "Missing argument! Usage: kill-by-port $PORT"
  fi
}

then you can just type kill-by-port 3000 to kill your rails server (substituting 3000 for whatever port it's running on)

failing that, you could always just type kill -9 $(cat tmp/pids/server.pid) from the rails root directory

edited Jun 20 '18 at 03:26

answered Jun 05 '18 at 05:04

Caleb Keene

360
2
7

1

I had to backslash `\$PORT` to get the message to display correctly. Otherwise, works great! – ashwood Mar 17 '19 at 20:24

score 6 · Answer 21 · answered Mar 31 '18 at 12:17

6

Add to ~/.bash_profile:

function killTcpListen () {
  kill -QUIT $(sudo lsof -sTCP:LISTEN -i tcp:$1 -t)
}

Then source ~/.bash_profile and run

killTcpListen 8080

answered Mar 31 '18 at 12:17

rofrol

12,038
7
62
63

score 6 · Answer 22 · answered Apr 18 '18 at 18:31

6

Using sindresorhus's fkill tool, you can do this:

$ fkill :3000

answered Apr 18 '18 at 18:31

Kodie Grantham

1,708
2
12
23

score 5 · Answer 23 · answered Dec 01 '20 at 22:09

5

Works for me for terminating node (Mac OS Catalina)

killall -9 node

answered Dec 01 '20 at 22:09

Abdul Saleem

7,999
4
35
37

score 4 · Answer 24 · answered May 08 '18 at 16:17

TL;DR:

lsof -ti tcp:3000 -sTCP:LISTEN | xargs kill

If you're in a situation where there are both clients and servers using the port, e.g.:

$ lsof -i tcp:3000
COMMAND     PID         USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME
node       2043 benjiegillam   21u  IPv4 0xb1b4330c68e5ad61      0t0  TCP localhost:3000->localhost:52557 (ESTABLISHED)
node       2043 benjiegillam   22u  IPv4 0xb1b4330c8d393021      0t0  TCP localhost:3000->localhost:52344 (ESTABLISHED)
node       2043 benjiegillam   25u  IPv4 0xb1b4330c8eaf16c1      0t0  TCP localhost:3000 (LISTEN)
Google    99004 benjiegillam  125u  IPv4 0xb1b4330c8bb05021      0t0  TCP localhost:52557->localhost:3000 (ESTABLISHED)
Google    99004 benjiegillam  216u  IPv4 0xb1b4330c8e5ea6c1      0t0  TCP localhost:52344->localhost:3000 (ESTABLISHED)

then you probably don't want to kill both.

In this situation you can use -sTCP:LISTEN to only show the pid of processes that are listening. Combining this with the -t terse format you can automatically kill the process:

lsof -ti tcp:3000 -sTCP:LISTEN | xargs kill

score 2 · Answer 25 · answered Aug 12 '18 at 14:02

You should try this, This technique is OS Independent.

In side your application there is a folder called tmp, inside that there is an another folder called pids. That file contains the server pid file. Simply delete that file. port automatically kill itself.

I think this is the easy way.

score 2 · Answer 26 · answered Aug 30 '18 at 19:51

Here's a helper bash function to kill multiple processes by name or port

fkill() {
  for i in $@;do export q=$i;if [[ $i == :* ]];then lsof -i$i|sed -n '1!p';
  else ps aux|grep -i $i|grep -v grep;fi|awk '{print $2}'|\
  xargs -I@ sh -c 'kill -9 @&&printf "X %s->%s\n" $q @';done
}

Usage:

$ fkill [process name] [process port]

Example:

$ fkill someapp :8080 node :3333 :9000

score 2 · Answer 27 · answered Jun 04 '19 at 04:20

2

You can try this

netstat -vanp tcp | grep 3000

answered Jun 04 '19 at 04:20

Foram

345
4
8

score 2 · Answer 28 · edited Apr 21 '21 at 08:54

2

my fav one-liner: sudo kill `sudo lsof -t -i:3000`

edited Apr 21 '21 at 08:54

inexcitus

2,071
2
21
34

answered Apr 20 '21 at 16:37

LowFieldTheory

1,554
1
23
35

score 1 · Answer 29 · answered Feb 10 '19 at 14:13

1

If you want a code free way - open activity manager and force kill node :)

answered Feb 10 '19 at 14:13

HannahCarney

3,128
1
24
29

score 1 · Answer 30 · answered Oct 16 '19 at 07:52

1

I use this:

cat tmp/pids/server.pid | pbcopy

Then kill -9 'paste'

answered Oct 16 '19 at 07:52

Mihail hidr0 Kirilov

85
7

score 0 · Answer 31 · answered Mar 11 '21 at 22:52

0

I use:

lsof -wni tcp:3000

Get the PID, and:

kill -9 <PID>

answered Mar 11 '21 at 22:52

Sahu

91
1
7

score -1 · Answer 32 · answered Sep 08 '18 at 08:45

-1

Step 1: Find server which are running: ps aux | grep puma Step 2: Kill those server Kill -9 [server number]

answered Sep 08 '18 at 08:45

Thiện Nguyễn

11

score -2 · Answer 33 · answered Apr 20 '19 at 09:50

-2

In mac OS

kill -9 $(lsof -i TCP:3000 | grep LISTEN | awk '{print $2}')

answered Apr 20 '19 at 09:50

NoughT

639
3
17
35

1

This was posted as a comment 5 years ago, and simular answers were posted multiple times. – Gilles Gouaillardet Apr 20 '19 at 14:40

score -10 · Answer 34 · edited Oct 30 '17 at 08:41

-10

You should try this code using the terminal:

$ killall -9 ruby

edited Oct 30 '17 at 08:41

Murmel

4,141
38
45

answered Oct 30 '17 at 08:03

shakeel rauf

17
3

Find (and kill) process locking port 3000 on Mac

34 Answers34

Linked

Related