Forum Discussion
swo0sh_gt_13163
Altostratus
Thanks for the reply.
Let me try to rephrase it, Basically I want to check how to check core dump status? Just to inform you that I have already imported QKview file to iHealth, I have checked CPU utilization from graphs, however it seemed normal.
Now from Logs (In iHealth), my colleague found that core CPU status from the logs (not sure the exact location from, and this is what I am looking for), where there was details about when CPU spike was generated along with the time stamp.
I hope this makes sense. Please revert if there is any confusion.
Andre_Nurwono
Aug 15, 2013Employee
Core dumps and qkview data are two different things.
A core dump is a memory dump of one software state, when it crashes (like what happens if you see the blue screen of death in Windows)
A qkview file is a snapshot of the entire system by collecting system information, including rrd performance graphs.
The qkview .tgz file does not collect core files, you will need to copy a core file from /var/core/ manually, such as using WinSCP, then upload it to your support case (if you need to know why the software crashed).
If you upload a qkview to ihealth, you can check CPU utilization by clicking on the graphs view, it will display CPU utilization data as far back as 30 days, and it looks like you've already done that.
If you already found logs that could point to a symptom of the CPU spike, you could search the AskF5 knowledge base fopr the meaning of the logs. You can also see where the core files are by searching for "core" in the "Commands" section of ihealth.
(look for ls critical files)
From then on to grab the core you will need to find it in the TMOS filesystem (search /var/core/ which is the most common location of any corefiles)
To analyze the core, you may open a support ticket with F5 support.