Databases
StackOverflow2013
Postsdbo
POUnicorn Eating Memory
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUnicorn Eating Memory
    primarykey
    data
    text
    <p>I have a m1.small instance in amazon with 8GB hard disk space on which my rails application runs. It runs smoothly for 2 weeks and after that it crashes saying the memory is full. App is running on rails 3.1.1, unicorn and nginx</p> <p><strong>I simply dont understand what is taking 13G ?</strong><br> <strong>I killed unicorn and 'free' command is showing some free space while df is still saying 100%</strong><br> <strong>I rebooted the instance and everything started working fine.</strong> </p> <h2>free (before killing unicorn)</h2> <pre><code> total used free shared buffers cached Mem: 1705192 1671580 33612 0 321816 405288 -/+ buffers/cache: 944476 760716 Swap: 917500 50812 866688 </code></pre> <h2>df -l (before killing unicorn)</h2> <pre><code>Filesystem 1K-blocks Used Available Use% Mounted on /dev/xvda1 8256952 7837520 4 100% / none 847464 120 847344 1% /dev none 852596 0 852596 0% /dev/shm none 852596 56 852540 1% /var/run none 852596 0 852596 0% /var/lock /dev/xvda2 153899044 192068 145889352 1% /mnt /dev/xvdf 51606140 10276704 38707996 21% /data </code></pre> <h2>sudo du -hc --max-depth=1 (before killing unicorn)</h2> <pre><code>28K ./root 6.6M ./etc 4.0K ./opt 9.7G ./data 1.7G ./usr 4.0K ./media du: cannot access `./proc/27220/task/27220/fd/4': No such file or directory du: cannot access `./proc/27220/task/27220/fdinfo/4': No such file or directory du: cannot access `./proc/27220/fd/4': No such file or directory du: cannot access `./proc/27220/fdinfo/4': No such file or directory 0 ./proc 14M ./boot 120K ./dev 1.1G ./home 66M ./lib 4.0K ./selinux 6.5M ./sbin 6.5M ./bin 4.0K ./srv 148K ./tmp 16K ./lost+found 20K ./mnt 0 ./sys 253M ./var 13G . 13G total </code></pre> <h2>free (after killing unicorn)</h2> <pre><code> total used free shared buffers cached Mem: 1705192 985876 **719316** 0 365536 228576 -/+ buffers/cache: 391764 1313428 Swap: 917500 46176 871324 </code></pre> <h2>df -l (after killing unicorn)</h2> <pre><code>Filesystem 1K-blocks Used Available Use% Mounted on /dev/xvda1 8256952 7837516 8 100% / none 847464 120 847344 1% /dev none 852596 0 852596 0% /dev/shm none 852596 56 852540 1% /var/run none 852596 0 852596 0% /var/lock /dev/xvda2 153899044 192068 145889352 1% /mnt /dev/xvdf 51606140 10276704 38707996 21% /data </code></pre> <h1>unicorn.rb</h1> <pre><code>rails_env = 'production' working_directory "/home/user/app_name" worker_processes 5 preload_app true timeout 60 rails_root = "/home/user/app_name" listen "#{rails_root}/tmp/sockets/unicorn.sock", :backlog =&gt; 2048 # listen 3000, :tcp_nopush =&gt; false pid "#{rails_root}/tmp/pids/unicorn.pid" stderr_path "#{rails_root}/log/unicorn/unicorn.err.log" stdout_path "#{rails_root}/log/unicorn/unicorn.out.log" GC.copy_on_write_friendly = true if GC.respond_to?(:copy_on_write_friendly=) before_fork do |server, worker| ActiveRecord::Base.connection.disconnect! ## # When sent a USR2, Unicorn will suffix its pidfile with .oldbin and # immediately start loading up a new version of itself (loaded with a new # version of our app). When this new Unicorn is completely loaded # it will begin spawning workers. The first worker spawned will check to # see if an .oldbin pidfile exists. If so, this means we've just booted up # a new Unicorn and need to tell the old one that it can now die. To do so # we send it a QUIT. # # Using this method we get 0 downtime deploys. old_pid = "#{rails_root}/tmp/pids/unicorn.pid.oldbin" if File.exists?(old_pid) &amp;&amp; server.pid != old_pid begin Process.kill("QUIT", File.read(old_pid).to_i) rescue Errno::ENOENT, Errno::ESRCH # someone else did our job for us end end end after_fork do |server, worker| ActiveRecord::Base.establish_connection worker.user('rails', 'rails') if Process.euid == 0 &amp;&amp; rails_env == 'production' end </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USKrishnaprasad Varma
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POUnicorn Eating Memory
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POUnicorn Eating Memory
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POUnicorn Eating Memory
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload