Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
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
Search help
Notifications
Mark all as read See all your notifications »
Q&A

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

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

2 answers

You are accessing this answer with a direct link, so it's being shown above all other answers regardless of its score. You can return to the normal view.

+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)
History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

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)
+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

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
History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

2 comment threads

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

Sign up to answer this question »