On Tue, Nov 1, 2016 at 8:02 AM, Justin Foreman <[email protected]> wrote:
> From a fresh restart, after a random amount of time (typically within 10 > minutes), my Foreman / Katello instance becomes unusable because two > Passenger RubyApp: /usr/share/foreman processes spike to 100% cpu and stay > there. I'm not seeing anything obvious in the logs, and I've tried to > attach strace to the ruby processes, but I am not seeing anything out of > the ordinary (although I'm not the sharpest with strace output). > > Any help would be appreciated, as we're dead in the water. I even tried > using the backup/restore functionality to a new server (which worked > successfully after a bit of massaging), but ended up with the same two ruby > processes at 100% CPU. > > from another thread from yesterday, lzap wrote: Can you guys try foreman-tracer utility (SystemTap based, will only work on CentOS 7 or higher or ST-enabled kernels) on your production instance? No changes required in Foreman, setup is quite easy: https://github.com/lzap/foreman-tracer Interesting statistics would be foreman-tracer rails objects-total and foreman-tracer rails objects It's like "top" utility experience, pastebin the bottlenecks please. > Justin > > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
