Procuring a Reporter memory dump for Linux
This should only be done at the request of Bluecoat support.
Procuring a dump, when Reporter causes LINUX to go into a High Utilization state:
–" ps –aux |grep reporter"
6: In the same terminal window, use the number found in the above command to execute this command which will kill the Reporter service, and create a core:
–" kill -segv <PID NUMBER> "
General LINUX Notes on taking a core:
%% -- output one '%'
%p -- pid
%u -- uid
%g -- gid
%s -- signal number
%t -- UNIX time of dump
%h -- hostname
%e -- executable filename
NOTE1: If the core_pattern file does not include “%p” (the default does not) and the core_uses_pid file contains a non-zero value (something other than ‘0’), then a dot and PID will be appended to the name of the core dump file.
NOTE2: You must be root to configure these things.
NOTE3: Here is an example to make the core file name to contain executable file name and time of the dump:
echo core.%e.%t > /proc/sys/kernel/core_pattern
NOTE4: More information about the -segv switch can we found here WIKI SITE
NOTE5:Generic informatoin about taking a memory dump on LINUX, can be found here IBM INFO.
To debug the dump yourself, you need to execute this command "yum install gdb" but this will only work on a Red Hat registered machine.
Rate this Page
Please take a moment to complete this form to help us better serve you.