I ma trying to kill the ruby process, but it is impossible. I am using Ubuntu, I clean my cache, I reboot my os, then the ruby server is running. But if I run pgrep -l ruby, I get some pid I am trying to kill with kill -9 $pid. But when I run again pgrep -l ruby, it everlastingly showing the same process I want to kill... Someone could help ?
On my Linux server I ran:
sudo thin start -p 80 -d
Now I'd like to restart the sever. The trouble is, I can't seem to get the old process to kill it.
Hi
We have script to stop our application, all our application use this standard script to stop however in one of our application this script does not work properly. It does not kill the process, thats why we always use the manual process to kill which is to kill the process id (kill -9 <process id>.
Can you please assist? what is missing or wrong .
I previously ran an two Ruby and Rails applications, one of them by using rails console command, the another one using Apache trough Phusion Passenger. Both applications ran in same IP, the only difference was the application running wih rails console was accesible from port 3000.
Now, I would like to run both apps with Apache, but I know what exactly configure to do that.
Hi,
I am a php developer and I decided to learn ruby on rails.
I have a few question.
I have an ubuntu virtual machine with lamp.
It mean that it has alrweady php and when I access the ip of the machine from my browser it does load the index.php.
if I install ruby on rails will theere be collision between the php and ruby or the server just know that if I ask for ruby file or for php.
Hi Everyone,
I am a new unix user. I started a qlogin session in SSH terminal, then I closed the window assuming that the qlogin session will be closed automatically. But it was still running. I tried to kill the process using kill ID or kill -9 ID, but the ID I got using
ps aux | grep qlogin keeps changing.
Does anyone have good suggestions on how to stop the qlogin process ?
I can't figure out how to kill this process. I ran du, but it took too long so I tried to kill it. It didn't die. I've tried SIGKILL, SIGSTOP, SIGINT, etc, with no effect (can't kill it, can't stop it).
I have RVM installed with Ruby 1.9.3 and Rails
$ rails -v
Rails 3.2.8
system: "redhat/5.8/x86_64"
I am trying to start the rails server using either: 'rails server -d' or even just 'rails'
however I am getting the following error:
$ rails server -d
/home/lauren/.rvm/rubies/ruby-1.9.3-p286/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:55:in `require': libcrypto.so.1.0.0: cannot ope
I'm trying to chase a bug on a Rails site and I've noticed that there are recurring Ruby processes which are hogging CPU and won't go away. I'd like to suss out what's starting them and how to either stop them or give them the resources they need to complete and get their work done.
Background: The server is Ubuntu 10.04 LTS. Ruby is 1.9.2-p290.