How can I shut down the local firebase emulators?

Question

Currently I initialise the firebase emulators with:

$ firebase emulators:start

After some time working on it I want to stop it. How can I then stop the emulators?

score 69 · Accepted Answer · answered Aug 26 '20 at 16:57

69

Check which process is occupying the port sudo lsof -i tcp:<port>
Kill the process kill -9 <process id>

answered Aug 26 '20 at 16:57

xmkevinchen

1,506
1
14
17

5

I have found that if you exit VSCode without shutting down the emulators first it can remain running and without the above commands, you will need to restart the computer to be able to restart the emulators. Thank you for sharing @xmkevinchen – ra9r Sep 19 '20 at 20:45
3

For windows: https://stackoverflow.com/a/39633428/681803 – ThdK Sep 21 '20 at 17:12
@ra9r on linux the process is called _java_. If you kill it you won't need to restart your computer. – perepm Jan 21 '21 at 09:14
15

I'm flabbergasted there is no shutdown command...this is an insane workflow. – Daniel Brotherston Apr 26 '21 at 12:06
4

This seems like such an obvious feature to include in a command `firebase emulators:stop` or similar, it makes me think I'm using the tool wrong. Is the normal workflow to start up the emulators and leave them running in the background while developing for long periods of time? – Jeff Neet Dec 14 '21 at 20:20
@JeffNeet that's the way I use it. I fire up the function/firestore emulators and work on event functions and db triggers. Sometimes it completely blows out and stops with an error leaving the process running which is when I need the answer below by user kazuwombat. Generally tho, 2x Ctrl-C is enough. – monsto Apr 19 '22 at 13:25
Using `kill -2` might be better as it will send `SIGINT` instead of `SIGKILL`. It will have the same effect as pressing `Ctrl + C` in the emulator terminal and will allow for a clean shutdown. – Renaud Aug 15 '22 at 12:37

score 27 · Answer 2 · answered Apr 28 '21 at 15:12

27

according to this: https://github.com/firebase/firebase-tools/issues/1367 Ctrl+C kills the emulators

answered Apr 28 '21 at 15:12

Joaquin Hoffmann

440
4
4

4

Nope. Doesn't work on a MacBook. – Johann Apr 01 '22 at 13:13
Not possible if there isn't one visually running. – tazboy Jul 28 '22 at 18:46
2

Doesn't kill the java console with Ctrl+C in windows also – Shankaja Aroshana Mar 20 '23 at 18:14

score 26 · Answer 3 · edited Aug 03 '23 at 20:44

26

One cross-platform solution is to just run kill-port :

npx kill-port 4000 8080 8085

edited Aug 03 '23 at 20:44

Sebastien F.

1,613
2
23
40

answered Jun 22 '21 at 22:32

GorvGoyl

42,508
29
229
225

2

Faster option, and work in windows and Linux – Alberto Oliveira Feb 18 '22 at 17:58
3

The command should be: `npx kill-port 4000 8080 8085`. Spaces between port numbers instead of commas. – wonderingdev Nov 18 '22 at 12:17

score 20 · Answer 4 · answered Dec 10 '21 at 20:22

If you wanna kill all firebase emulators you can easily do that by firing this command

$ lsof -t -i:8080 -i:9000 -i:9099 -i:9199 -i:9090 | xargs kill -9

When you don't want to type this long command each time I advise you to use a script in the package.json file

 "scripts": {
   "emulators:start": "firebase emulators:start",
   "emulators:stop": "lsof -t -i:5001 -i:5002 -i:8080 -i:9000 -i:9099 -i:9199 -i:9090 | xargs kill -9"
  }

One for starting your emulators and one for stopping, in case Ctr+C didn't stop the processes in the background.

Those are the default PORTS from the documentation page in firebase. You should also check your firebase.json file and replace the PORTS in the previous command if they are different.

Thanks, there are multiple emulators you can check the [documentation](https://firebase.google.com/docs/emulator-suite/install_and_configure#port_configuration) and add what you need — Alaeddine, Dec 28 '22 at 16:00

score 18 · Answer 5 · answered Nov 04 '20 at 05:27

18

If you don't want to have to check the port every time, you can stop command with below

kill -9 (lsof -t -i:5002 -i:5001)

(-i:xxxx are your running emulator ports in firebase.json.)

Moreover, I don't want to memorize this long command. So I made package.json script below.

"scripts": {
   ...
   "stop": "lsof -t -i :5001 -i:5002 | xargs kill -9",
   ...
}

answered Nov 04 '20 at 05:27

kazuwombat

1,515
1
16
19

4

Nothing like a little automation to simplify your day. – monsto Apr 19 '22 at 13:21

OhNoNotScott · Answer 6 · 2021-10-27T04:24:34.853

So here's a bit of fun I just discovered. Double tap CTRL-C (hold down CTRL and double tap C) in the terminal running the emulator when you want to shut down the emulator and clear all the ports and processes.

I've checked it a couple of times and looked to see if the ports are free, they all are.

Just using CTRL-C once leaves you with all those ports still being used. Hope it solves the problem for others and not just me.

Edit: Looks to me now like the problem only persists until first shutdown of the computer after setting up the emulators. I now have no problems with the emulators shutting down properly with a single CTRL-C.

score 5 · Answer 7 · answered Jan 21 '21 at 09:40

I've tried all the answers above, and none does what I was expecting: to gracefully end the emulator suite as a whole without having to ctrl+c, leaving no ports occupied. Here is how I've solved it.

TLDR: lsof -ti :4400 | xargs --no-run-if-empty kill

The port being 4400, as it's the default port for the Emulator Hub. Although with this command you'll end the emulator regardless of the process you kill.

The"-9" flag used in the other answers does not send the SIGTERM signal to the process, but forcefully kills it instead. This prevents the emulator from ending gracefully.

this was it for me, though --no-run-if-empty is bogus on macOS — user3875913, Feb 17 '21 at 16:45

score 5 · Answer 8 · answered May 30 '21 at 02:18

An alternative is to use firebase emulators:exec, which, according to the CLI documentation, does this:

start the local Firebase emulators, run a test script, then shut down the emulators

Since I put my test running command in a Makefile, I use the following command to test firestore from a Python firebase_admin SDK:

firebase emulators:exec "make test" --only firestore

The set-up and tear-down of the port is handled by firebase directly.

score 2 · Answer 9 · answered Dec 29 '22 at 11:33

2

If you're using Node in your project you can call

npx kill-port 3000 8080 9000 5001 5000 9199

You can put this into a script in your package.json to easily call with npm run kill.

"scripts": {
  "kill": "npx kill-port 3000 8080 9000 5001 5000 9199"
}

answered Dec 29 '22 at 11:33

Soviut

88,194
49
192
260

score 1 · Answer 10 · answered Oct 11 '21 at 08:16

1

For Windows, first find PID of the process using port 8080 by typing this in cmd.

netstat -a -n -o | find "8080"

Next, kill that process by:

taskkill /PID <type PID here>

answered Oct 11 '21 at 08:16

deZak

109
2
2

touch my body · Answer 11 · 2023-03-01T06:13:00.437

Here's one way you can stop the emulators:

pkill -f "firebase/emulators"

According to the Firebase Emulators SDK documentation (link):

Calling emulators:start will download the emulators to ~/.cache/firebase/emulators/ if they are not already installed.

So, this solution works because:

The emulator process is provided a .jar file, located in this directory
Since this jar path is in the process name, pkill -f can find it by name

This is more robust than solutions that make assumptions about what ports the emulator is running on, and it works if you have multiple instances of a specific emulator running.

How can I shut down the local firebase emulators?

11 Answers11

Linked