All threads / Vim is being "killed" by OOM when trying to open prod log

Ask A Question

Notifications

You’re not receiving notifications from this thread.

Vim is being "killed" by OOM when trying to open prod log

Drew Bragg asked in Servers

I'm hvaing an odd issue that I can't see to get a handle on.

When I ssh into my prod server and I try to open /home/deploy/app/shared/log/production.log in vim or nano the process just hangs for a while and then I get a message that just says killed. when I checkout the kernal log I see that OOM killed vim. I also can't pull down the log with rsync.

I can tail the log and see everyting just fine but I can't actually open the file...

Does anyone have a good idea of where to start looking into this?

The file is almost certainly too big to fit into memory.
I'd suggest you use e.g. grep or tail or split to make it manageable.

I'm curious as to why this is happening. The server is set up the exact same way as every other server I have yet this is the only one with this issue.

Join the discussion

Want to stay up-to-date with Ruby on Rails?

Join 37,344+ developers who get early access to new tutorials, screencasts, articles, and more.

    We care about the protection of your data. Read our Privacy Policy.

    logo Created with Sketch.

    Ruby on Rails tutorials, guides, and screencasts for web developers learning Ruby, Rails, Javascript, Turbolinks, Stimulus.js, Vue.js, and more. Icons by Icons8

    © 2020 GoRails, LLC. All rights reserved.