Running Rails Console Gets Killed

Asked Sep 03 '17 at 10:26

Active Sep 03 '17 at 10:26

Viewed 1,251 times

When i run on my production servers the command:

bundle exec rails c production

After few seconds i get "Killed", the server has 32GB RAM and have no lack of memory.

I use Ruby 2.1.6 with Rails 4.2.9 On CentOS 6.5.

I tried add SWAP file it doesn't worked.

asked Sep 03 '17 at 10:26

matanco

Is there any stacktrace? In stdout or log/production.log ? – kiddorails Sep 03 '17 at 12:10
No there is nothing on both of them. – matanco Sep 03 '17 at 12:14
Can you check if there is any log in `/var/log/kern.log`? – André Guimarães Sakata Sep 03 '17 at 14:52
This [question](https://stackoverflow.com/questions/726690/who-killed-my-process-and-why) may help you. – André Guimarães Sakata Sep 03 '17 at 14:53
Is there a renegade `cron` job calling `killall ruby`? Does this happen with any Ruby process or just your `rails c`? Using a tool like `top` or `htop` do you see memory get exhausted? An infinite loop allocating memory in your initializers could cause this. – tadman Sep 03 '17 at 17:34

0 Answers0