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 32 · Accepted Answer · answered Aug 26 '20 at 16:57

32

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,098
11
16

1

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. – ppicom Jan 21 '21 at 09:14
1

I'm flabbergasted there is no shutdown command...this is an insane workflow. – Daniel Brotherston Apr 26 '21 at 12:06
This does not work for windows – Sourav Kannantha B May 17 '21 at 06:21

score 7 · Answer 2 · answered Nov 04 '20 at 05:27

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",
   ...
}

score 3 · Answer 3 · 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 1 · Answer 4 · answered Apr 28 '21 at 15:12

1

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

64
3

score 0 · Answer 5 · 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.

How can I shut down the local firebase emulators?

5 Answers5