Communities

The Great Outdoors

Photography & Video

Scientific Speculation

Electrical Engineering

Languages & Linguistics

Software Development

Community Proposals

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

Notifications

Mark all as read See all your notifications »

Q&A

Posts Tags Edits

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

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

+2

−1

There's a easiest way to solve the problem that is you have to remove the file /home/istiak/ruby/qpixel/tmp/pids/server.pid. Then, you can run your server again.

rm /home/istiak/ruby/qpixel/tmp/pids/server.pid

Otherwise, you can kill the process also. Before killing the process you have find number of the process

more /home/istiak/ruby/qpixel/tmp/pids/server.pid

Then, put that number on following command (instead of 2786)

kill -9 PID (eg,2786)

You can try following code instead of above command (both are equivalent)

kill -9 $(more /home/istiak/ruby/qpixel/tmp/pids/server.pid)

If above code doesn't work than, try following ones.

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

posted over 3 years ago

CC BY-SA 4.0

3y ago

deleted user

Copy Link

Raw

Markdown

2 comment threads

Don't use the `-9` option unless all else failed! The `-9` option is the “nuclear option”, leaving... (1 comment)

Don't kill the process by process ID number unless you have actually verified what that process is (14 comments)

celtschk‭ wrote about 2 years ago

Don't use the -9 option unless all else failed!

The -9 option is the “nuclear option”, leaving the process no chance to clear up (e.g. deleting that server.pid file).

Normally you should use kill without that option. This will send a SIGTERM signal that should terminate the process, but gives it a chance to clean up after itself. Now if the process hangs badly, that might not work; if the process is still running after a normal kill, then it is the time to take thenuclear option kill -9 (unless the process is in uninterruptible sleep, in which case ps will show D in the stat field; if that is the case, -9 won't be able to terminate the process either).

And of course I agree with the other thread, that you should first check what the PID actually refers to.