Post History
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 ...
Answer
#2: Post edited
by
Trilarion
·
2022-10-06T10:06:19Z (about 2 years ago)
replaced specific but meaningless names with XXX, YYY and removed Hope that helps (while true, always implied)
- To fix this:
- First, run `cat` command on the file listed in the message. e.g:
- ```
cat /home/istiak/ruby/qpixel/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
```Hope this helps!
- 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
- ```
#1: Initial revision
by
Kevin M. Mansour
·
2021-07-14T00:10:14Z (over 3 years ago)
To fix this: First, run `cat` command on the file listed in the message. e.g: ``` cat /home/istiak/ruby/qpixel/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 ``` Hope this helps!