Server is already running in Rails

Question

When I am starting rails server using rails s command it is showing A server is already running. Check C:/Sites/folder/Pids/Server.pids

When I open the file it is outputting a 4 digit number only so how could I resolve this issue ?

FYI

No other instance of Rails cmd is running this time.
Checked Task manager but only cmd.exe is showing no else process is running. (using Windows).

I remover server.pid from \tmp\pids – user6746262 Jun 06 '17 at 09:55 — user6746262, Jun 06 '17 at 09:55

Taimoor Changaiz · Answer 1 · 2020-04-22T07:57:22.213

TL;DR Just Run this command to Kill it

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

Root Cause: Because PID is locked in a file and web server thinks that if that file exists then it means it is already running. Normally when a web server is closed that file is deleted, but in some cases, proper deletion doesn't happen so you have to remove the file manually New Solutions

when you run rails s

=> Booting WEBrick

=> Rails 4.0.4 application starting in development on http://0.0.0.0:3000

=> Run rails server -h for more startup options

=> Ctrl-C to shutdown server

A server is already running. Check /your_project_path/tmp/pids/server.pid. Exiting

So place your path shown here /your_project_path/tmp/pids/server.pid

and remove this server.pid file:

rm /your_project_path/tmp/pids/server.pid

OR Incase you're server was detached then follow below guidelines:

If you detached you rails server by using command "rails -d" then,

Remove rails detached server by using command

ps -aef | grep rails

OR by this command

sudo lsof -wni tcp:3000

then

kill -9 pID

OR use this command

To find and kill process by port name on which that program is running. For 3000 replace port on which your program is running.

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

Old Solution:

rails s -p 4000 -P tmp/pids/server2.pid

Also you can find this post for more options Rails Update to 3.2.11 breaks running multiple servers

because PID is locked in file and web server thinks that if that file exists then it means it is already running. Normally when web server is closed that file is deleted, but in some cases proper deletion don't happen so you have to remove file manually — Taimoor Changaiz, May 17 '16 at 05:17
Careful this will also kill your browser if it's pointing to :3000! — Aeramor, Jul 21 '18 at 10:19
Very nice! I created a function on my bash profile that kill the running server using this command, so you just type `kill_server` on the terminal and everything is done. I declared this on my bash profile: `kill_server() { sudo kill -9 $(lsof -i :3000 -t) }` — Victor, Nov 30 '20 at 23:18

rainkinz · Accepted Answer · 2019-10-29T16:40:50.783

220

Remove the file: C:/Sites/folder/Pids/Server.pids

Explanation In UNIX land at least we usually track the process id (pid) in a file like server.pid. I think this is doing the same thing here. That file was probably left over from a crash.

edited Oct 29 '19 at 16:40

answered Feb 25 '13 at 17:34

rainkinz

10,082
5
45
73

6

what exactly this file do and cause for this ..can you please explain it a little more :) – swapnesh Feb 25 '13 at 17:36
12

Sorry, I should have commented further. In UNIX land at least we usually track the process id (pid) in a file like server.pid. I think this is doing the same thing here. That file was probably left over from a crash. – rainkinz Feb 25 '13 at 18:18
I think I clone it from Git so do u think it might be a cause ? https://github.com/swapnesh/Add_twitter_bootstrap – swapnesh Feb 25 '13 at 18:22
2

After doing this I'm still getting a "Port in use" for 3000. Anyone know how I can fix this? Thanks! – daveomcd Jan 12 '14 at 01:48
6

Run `netstat -a -o` at a command prompt to see what process is using port 3000 – Rory Jan 13 '14 at 04:42
causes socket.rb:206:in `bind': Address already in use - bind(2) for 0.0.0.0:3000 (Errno::EADDRINUSE), check joshs answer how to resolve this after removing .pid – mmln Aug 28 '14 at 16:09
its `/tmp/pids` now – Phil Apr 24 '17 at 17:25

Josh Bedo · Answer 3 · 2014-09-26T18:05:42.770

lsof -wni tcp:3000

Then you should see the ruby process and you can run

kill -9 processid

you should be good to run the process now

rails s thin

running multiple processes doesn't seem like a good idea and from what i've read many people agree. I've noticed many memory leaks with rails unfortunately so I couldn't imagine having two processes running. I know with one overtime my page refreshes increasingly become slower because of the data being stored on memory.

score 30 · Answer 4 · answered Feb 24 '15 at 12:26

30

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

answered Feb 24 '15 at 12:26

Karan Purohit

2,649
2
17
10

2

@CalamityAdam Rails usually runs on port 3000. He searches for processes based on that and gets only the PID from them (`-t` option) and then kills the process by that retrieved PID. – totymedli Oct 30 '19 at 16:44

score 15 · Answer 5 · edited Mar 27 '18 at 13:56

15

You can get rid of the process by killing it:

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

edited Mar 27 '18 at 13:56

rollstuhlfahrer

3,988
9
25
38

answered Mar 27 '18 at 13:38

manu

199
3
10

I like this one. Nice and concise, yet complete. Cheers. – LunaCodeGirl Oct 17 '19 at 20:11

score 12 · Answer 6 · edited Jun 08 '16 at 03:43

12

$ lsof -wni tcp:3000

# Kill the running process
$ kill -9 5946

$ rm tmp/server.pids

foreman start etc start the service

edited Jun 08 '16 at 03:43

Laurel

5,965
14
31
57

answered Jun 08 '16 at 03:05

user1251378

121
1
3

Lorenzo Sinisi · Answer 7 · 2016-11-17T14:55:24.590

7

gem install shutup

then go in the current folder of your rails project and run

shutup # this will kill the Rails process currently running

You can use the command 'shutup' every time you want

DICLAIMER: I am the creator of this gem

NOTE: if you are using rvm install the gem globally

rvm @global do gem install shutup

edited Nov 17 '16 at 14:55

answered Nov 16 '16 at 11:51

Lorenzo Sinisi

450
5
8

score 5 · Answer 8 · answered Aug 28 '13 at 11:19

5

It happens when you kill your server process and the pid file was not updated. The best solution is to delete the file Server.pid.

Use the command

rm <path to file Server.pid>

answered Aug 28 '13 at 11:19

Ashish Sharma

321
3
13

score 4 · Answer 9 · answered Sep 17 '18 at 23:48

4

On Windows Rails 5.2, delete this file

c:/Sites/<your_folder>/tmp/pids/server.pid

and run

rails s

again.

answered Sep 17 '18 at 23:48

MSC

3,286
5
29
47

score 4 · Answer 10 · answered Nov 28 '20 at 03:49

Just open that C:/Sites/folder/Pids/Server.pids and copy that 4 digit value.that 4 digit value is nothing but a PID, which you need to kill to stop the already running process.

then to stop the process use below command

 kill -9 <pid>

once that already running process get stopped then hit

rails s to start the rails server

score 3 · Answer 11 · answered Jul 20 '15 at 03:24

3

Probably you suspended the server by: ^Z.

The four digital number that vim C:/Sites/folder/Pids/Server.pidsoutputs is the process id.

You should kill -9 processid, replacing the process id with the 4 numbers that vim (or other editor) outputed.

answered Jul 20 '15 at 03:24

Cherenkov

485
1
8
16

What's the right way to stop the server properly? CTRL + C? – dragonfly02 Feb 10 '19 at 16:58

score 3 · Answer 12 · answered Jan 16 '19 at 08:31

3

Run:

in Ubuntu/linux

 sudo rm /var/www/html/rails/WBPOCTEST/tmp/pids/server.pid

Or

 pkill -9 ruby

or

lsof -wni tcp:3000

kill -9 pid

answered Jan 16 '19 at 08:31

Syed Shibli

992
1
12
15

Vaibhav Jain · Answer 13 · 2021-11-09T09:51:59.693

3

On Ubuntu :- sudo kill -9 $(lsof -i :3000 -t)

where, 3000 is port number

Works for me....

For older versions :-

rails s -p 3000 -P tmp/pids/server2.pid

edited Nov 09 '21 at 09:51

answered Aug 10 '21 at 10:12

Vaibhav Jain

305
3
8

score 2 · Answer 14 · answered Nov 03 '17 at 08:18

2

If you are on Windows, you just need to do only one step as 'rails restart' and then again type 'rails s' You are good to go.

answered Nov 03 '17 at 08:18

Alok Amme

129
1
4

almawhoob · Answer 15 · 2018-11-24T16:20:55.360

1

Run: fuser -k -n tcp 3000

This will kill the process running at the default port 3000.

edited Nov 24 '18 at 16:20

answered Sep 06 '18 at 23:20

almawhoob

382
3
5

score 0 · Answer 16 · edited Dec 29 '18 at 14:49

0

I just had this issue and tried setting it to a different port, but the only thing I needed to do was to delete my [app_directory]/tmp/pids/server.pid and everything was good to go.

edited Dec 29 '18 at 14:49

geisterfurz007

5,292
5
33
54

answered Dec 28 '18 at 21:58

Dakota Michael

1

score 0 · Answer 17 · answered Oct 07 '21 at 09:21

0

my docker container has no lsof. Try sudo kill -9 $(netstat -ano -p tcp | grep :3000 | awk '{ print $7 }' | grep -Po '^[\d]+')

answered Oct 07 '21 at 09:21

mfittko

411
4
3

score 0 · Answer 18 · answered Aug 23 '22 at 07:01

0

I have face this issue in my rails application when i used docker in windows mechine. i just removed the server.pid file from the project and restart the rails application.

You just need to delete C:/Sites/folder/Pids/Server.pid this file

answered Aug 23 '22 at 07:01

Syamlal

714
1
11
20

047 Kusen Hang Subba · Answer 19 · 2022-11-07T05:44:49.670

0

Just go to the TMP folder in your application. Go to the pids folder and delete the files present. Now rerun the server. This worked for me.

edited Nov 07 '22 at 05:44

answered Nov 07 '22 at 05:44

047 Kusen Hang Subba

1
1

score 0 · Answer 20 · answered Dec 07 '22 at 14:09

I was after a way I could intuitively understand (as opposed to just memorise).

All you need to know is two things

Run the ps command to list processes, and
Run the kill command to stop a process

Example

Then it's as simple as:

ps
# PID TTY           TIME CMD
# 32953 ttys000    0:00.71 -zsh
# 33730 ttys001    0:00.67 -zsh  
# 46844 ttys004    0:01.78 puma 4.3.12 (tcp://localhost:3000) [myapp]

look for the PID that matches your rails server, and pass it to kill

kill -9 46844

Run ps again to see that it's now stopped.

Note

For more info on -9, run man kill.

Server is already running in Rails

20 Answers20

All you need to know is two things

Example

Note

Linked

Related