Find (and kill) process locking port 3000 on Mac
node.jsMacosProcessnode.js Problem Overview
How do I find (and kill) processes that listen to/use my TCP ports? I'm on macOS.
Sometimes, after a crash or some bug, my Rails app is locking port 3000. I can't find it using ps -ef
...
When running
rails server
I get
Address already in use - bind(2) (Errno::EADDRINUSE)
The same issue happens when stopping Node.js process. Even after the process is stopped and the app stops running, port 3000
is locked. When starting the app again, getting
Address already in use (Errno::EADDRINUSE)
node.js Solutions
Solution 1 - node.js
-
You can try
netstat
netstat -vanp tcp | grep 3000
-
For macOS El Capitan and newer (or if your netstat doesn't support
-p
), uselsof
lsof -i tcp:3000
-
For Centos 7 use:
netstat -vanp --tcp | grep 3000
Solution 2 - node.js
Find:
sudo lsof -i :3000
Kill:
kill -9 <PID>
PLEASE NOTE: -9
kills the process immediately, and gives it no chance of cleaning up after itself. This may cause problems. Consider using -15
(TERM) or -3
(QUIT) for a softer termination which allows the process to clean up after itself.
Solution 3 - node.js
Quick and easiest solution:
kill -9 $(lsof -ti:3000)
For multiple ports:
kill -9 $(lsof -ti:3000,3001)
#3000 is the port to be freed
Kill multiple ports with single line command:
kill -9 $(lsof -ti:3000,3001)
#Here multiple ports 3000 and 3001 are the ports to be freed
> lsof -ti:3000
If the prot is occupied, thie above command will return something like this: 82500 (Process ID)
> lsof -ti:3001
82499
> lsof -ti:3001,3000
82499 82500
> kill -9 $(lsof -ti:3001,3000)
Terminates both 82499 and 82500 processes in a single command.
For using this in package.json
scripts:
"scripts": {
"start": "kill -9 $(lsof -ti:3000,3001) && npm start"
}
In terminal you can use:
npm run start
Solution 4 - node.js
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>
Solution 5 - node.js
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.
Solution 6 - node.js
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.
Solution 7 - node.js
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.
Solution 8 - node.js
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
Why kill -9 PID
does not work?
If you trying to kill a process with its PID and it still runs on another PID, it looks like you have started that process in a different account most probably root account. so Login in with sudo su
and kill it
Solution 9 - node.js
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.
Solution 10 - node.js
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!
Solution 11 - node.js
lsof -P | grep ':3000' | awk '{print $2}'
This will give you just the pid, tested on MacOS.
Solution 12 - node.js
Execute in command line on OS-X El Captain:
kill -kill `lsof -t -i tcp:3000`
Terse option of lsof returns just the PID.
Solution 13 - node.js
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
Solution 14 - node.js
To view the processes blocking the port:
netstat -vanp tcp | grep 3000
To Kill the processes blocking the port:
kill $(lsof -t -i :3000)
Solution 15 - node.js
Find and kill:
This single command line is easy and works correctly.
kill -9 $(lsof -ti tcp:3000)
Solution 16 - node.js
Find the open connection
> lsof -i -P | grep -i "listen"
Kill by process ID
> kill -9 'PID'
Solution 17 - node.js
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
Solution 18 - node.js
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
Solution 19 - node.js
These two commands will help you find and kill server process
> 1. lsof -wni tcp:3000 > 2. kill -9 pid
Solution 20 - node.js
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
Solution 21 - node.js
kill -9 $(lsof -ti:3000)
works for me on macOS always.
If you're working on a node.js project, you can add it to package.json scripts like;
"scripts": {
...
"killme": "kill -9 $(lsof -ti:3000)",
...
},
then
npm run killme
--
Also if you want to add system wide alias for your macOS, follow these steps;
Navigate to your home directory:
cd ~
Open up .bash_profile or zsh profile using nano or vim:
vi .bash_profile
Add an alias (press i):
alias killme="kill -9 $(lsof -ti:3000)"
save file
restart terminal
type killme
to the terminal
Of course you can change port 3000 to what you want.
Solution 22 - node.js
Add to ~/.bash_profile
:
function killTcpListen () {
kill -QUIT $(sudo lsof -sTCP:LISTEN -i tcp:$1 -t)
}
Then source ~/.bash_profile
and run
killTcpListen 8080
Solution 23 - node.js
Using sindresorhus's fkill tool, you can do this:
$ fkill :3000
Solution 24 - node.js
Works for me for terminating node (Mac OS Catalina)
killall -9 node
Solution 25 - node.js
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
Solution 26 - node.js
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
Solution 27 - node.js
You can try this
netstat -vanp tcp | grep 3000
Solution 28 - node.js
To kill port 3000 on mac, run the below command
kill -9 $(lsof -t -i:3000 -sTCP:LISTEN)
Solution 29 - node.js
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.
Solution 30 - node.js
my fav one-liner:
sudo kill `sudo lsof -t -i:3000`
Solution 31 - node.js
If you want a code free way - open activity manager and force kill node :)
Solution 32 - node.js
I use this:
cat tmp/pids/server.pid | pbcopy
Then
kill -9 'paste'
Solution 33 - node.js
I use:
lsof -wni tcp:3000
Get the PID, and:
kill -9 <PID>
Solution 34 - node.js
Explanation of steps with terminal o/p
I have Macbook Pro (Catalina), 1 day I found the below issue while running the Django server (which runs on port 8000 by default):
> python manage.py runserver 3000
(venv) Rishikeshs-MacBook-Pro:learn-django hygull$ python manage.py runserver 3000
Watching for file changes with StatReloader
Performing system checks...
System check identified no issues (0 silenced).
July 27, 2021 - 23:54:05
Django version 3.2.3, using settings 'automated_classification.settings'
Starting development server at http://127.0.0.1:3000/
Quit the server with CONTROL-C.
Error: That port is already in use.
I tried to use the provided and executed but running only 1 of them was not solving my problem (I know there were some other answers too but somehow I solved my problem). E.g. I tried to rerun the above command but that too did not work (still the processes were active).
So I finally I used answer of @Cris with 1 more additional step as he & others have suggested. So my answer is just using their commands with Terminal output to make the executions more clearer to you.
> lsof -P | grep ':3000' | awk '{print $2}'
(venv) Rishikeshs-MacBook-Pro:learn-django hygull$ lsof -P | grep ':3000' | awk '{print $2}'
36239
38272
Now I got the list of ids to kill, let's do.
> kill -9 <PID>
(venv) Rishikeshs-MacBook-Pro:learn-django hygull$ kill -9 36239
(venv) Rishikeshs-MacBook-Pro:learn-django hygull$ kill -9 36239
-bash: kill: (36239) - No such process
(venv) Rishikeshs-MacBook-Pro:learn-django hygull$ kill -9 38272
(venv) Rishikeshs-MacBook-Pro:learn-django hygull$ kill -9 38272
-bash: kill: (38272) - No such process
And now, let's try to rerun the command.
> python manage.py runserver 3000
(venv) Rishikeshs-MacBook-Pro:learn-django hygull$ python manage.py runserver 3000
Watching for file changes with StatReloader
Performing system checks...
System check identified no issues (0 silenced).
July 27, 2021 - 23:55:53
Django version 3.2.3, using settings 'project.settings'
Starting development server at http://127.0.0.1:3000/
Quit the server with CONTROL-C.
FINAL
> kill -9 $(lsof -P | grep ':3000' | awk '{print $2}')
You can combine the above 2 steps in 1 line & execute to kill process listening on port 3000.
Solution 35 - node.js
After executing the kill commands, deleting the pid file might be necessary:
rm ~/mypath/myrailsapp/tmp/pids/server.pid
Solution 36 - node.js
If you're using Zsh, and don't want to remember multi-pipe commands, just add next lines of code to ~/.zshrc
:
function murder() {
lsof -nti:$1 | xargs kill -9
}
And then any time you need to kill a process on a specific port, just use:
murder 3000
P.S feel free to rename the command and improve it :)
Solution 37 - node.js
just write on terminal
sudo kill -9 $(lsof -i :3000 -t)
hope , it's work.
Solution 38 - node.js
Step 1: Find server which are running:
ps aux | grep puma
Step 2: Kill those server
Kill -9 [server number]
Solution 39 - node.js
In mac OS
kill -9 $(lsof -i TCP:3000 | grep LISTEN | awk '{print $2}')
Solution 40 - node.js
You should try this code using the terminal:
$ killall -9 ruby