Add coredump analysis & debug mode #104
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
List coredumps of the Manager & child process of Varnish. This contains useful information such as: time of the crash, pid, uid, gid, signal, whether corefile is present, path of the executeable and size of the corefile. Gather further information of each coredump, such as but not limited to: command line, cgroup, stack traces of threads, loaded so, path of the corefile. Coredump analysis of the latest crash is done using coredumpctl, we invoke gdb on the coredump to get the backtrace. This depend on coredumpctl having --debugger-arguments. A debug mode is introduced and activated through "-d", when activated we invoke gdb on all Varnish instances to get full backtrace and threads information. This is behind a non-default flag as it will pause Varnish while gathering this information. Signed-off-by: Asad Sajjad Ahmed <[email protected]>
Pulling this information later can be tricky. File format could have changed, symbols might be missing, etc. So, the best solution here is to run these commands on the Varnish server itself. Signed-off-by: Asad Sajjad Ahmed <[email protected]>
asadsa92
force-pushed
the
gdb_full_bt
branch
from
e9e1ef7 to
c7e7594
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
List coredumps of the Manager & child process of Varnish. This contains useful information such as: time of the crash, pid, uid, gid, signal, whether corefile is present, path of the executeable and size of the corefile.
Gather further information of each coredump, such as but not limited to: command line, cgroup, stack traces of threads, loaded so, path of the corefile.
Coredump analysis of the latest crash is done using coredumpctl, we invoke gdb on the coredump to get the backtrace. This depend on coredumpctl having --debugger-arguments.
A debug mode is introduced and activated through "-d", when activated we invoke gdb on all Varnish instances to get full backtrace and threads information. This is behind a non-default flag as it will pause Varnish while gathering this information.
Signed-off-by: Asad Sajjad Ahmed [email protected]