Communities

Writing

Codidact Meta

The Great Outdoors

Photography & Video

Scientific Speculation

Cooking

Electrical Engineering

Judaism

Languages & Linguistics

$Mathematics$

tag:snake search within a tag

answers:0 unanswered questions

user:xxxx search by author id

score:0.5 posts with 0.5+ score

"snake oil" exact phrase

votes:4 posts with 4+ votes

created:<1w created < 1 week ago

post_type:xxxx type of post

Search help

Notifications

Mark all as read See all your notifications »

Q&A Meta

Q&A

Posts Tags Edits

Ask Question

Comments on "A server is already running" error in rails

Parent

"A server is already running" error in rails

+2

−0

..$ rails s
=> Booting Puma
=> Rails 5.2.6 application starting in development 
=> Run `rails server -h` for more startup options
A server is already running. Check /home/istiak/ruby/qpixel/tmp/pids/server.pid.
Exiting

I was using my laptop. But, suddenly my laptop had turned off (for low battery). When I turned on my laptop and trying to run the server, I got above error. What should I do now? I had tried to go to gateway (http://localhost:3000/) but I couldn't visit that site.

ruby-on-rails server

posted over 3 years ago

CC BY-SA 4.0

2y ago by Trilarion‭

deleted user

Raw

Markdown

History

is a duplicate

This question has been asked before and has already been answered. It should be marked as a duplicate.

Please enter the URL of the proposed duplicate in the details field below.

not constructive

This question cannot be answered in a way that is helpful to anyone. It's not possible to learn something from possible answers, except for the solution for the specific problem of the asker.

0 comment threads

Post

+1

−1

To fix this:

First, run cat command on the file listed in the message. e.g:

cat /home/XXX/ruby/YYY/tmp/pids/server.pid

cat command will return a 5 digit number. e.g

12345 is the PID of the process that is running the current rails server.

Then kill the running process using:

kill -9 12345

Then you can run the server using:

rails s

posted over 3 years ago

CC BY-SA 4.0

2y ago by Trilarion‭

Kevin M. Mansour‭

24 reputation 2 3 3 3

Copy Link

Raw

Markdown

History

2 comment threads

PIDs are not required to be a 5-digit number (1 comment)

Beware! (1 comment)

elgonzo‭ wrote over 3 years ago · edited over 3 years ago

copy link

Beware of killing a process just by a given process number if that process number stems from a session before the computer was switched off and restarted (as seems to be the case here according to the explanation in the Q). It's possible that there is now another process using the same PID, a process that might very well be entirely unrelated to the formerly running ruby-on-rails server. And killing that process might yield unwanted consequences, depending on what actual process has been killed.