-
Notifications
You must be signed in to change notification settings - Fork 201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Detection of memory leak in a high-volume system causes reboots #29
Comments
@weldpua2008 No, you should never use this tool in high-volume systems since this tool uses code instrumentation instead of sampling, unlike the on-CPU flame graph sampling tool. |
@agentzh We are using the following scripts for a months:
but after adding the above script to schedule every 30 minutes (full version of our Memory Leak Flame Graph is at https://gist.github.com/weldpua2008/44e6884ac2bc6d0c129ddf03a9336656) we are experiencing reboot |
I have added crash and kernel debug to read vmcore.
crash /usr/lib/debug/lib/modules/2.6.32-696.1.1.el6.x86_64/vmlinux ./vmcore
crash> ps is at https://gist.github.com/weldpua2008/5d19c26b80bfbdd0566561a9cbd3cde6 |
Hi, Did you ever work out a solution for this? I'm having similar issues, not running on a cron but just trying to pin down an intermittent hotloop problem. I've found that running ngx-active-reqs script, from openresty-systemtap-toolkit, and then lj-lua-bt causes a crash almost every time. |
@hamishforbes Ensure you build the latest systemtap from its source release. Do not use the version in the system yum repository! It's ancient and very buggy. |
Hello,
We are using the following script to generate Memory Leak Flame Graphs on our production servers every 30 minutes:
We also using the following scripts
After installation debug symbols (
debuginfo-install glibc
) we are getting randomly rebootWe have CentOs 6.8:
The text was updated successfully, but these errors were encountered: