<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
you didn't include what version you are running ;)<br>
<br>
Looks like<br>
CSCso02381 CEF core due to invalid incoming QBE message header <br>
<br>
I just updated the RNE to include the include the backtrace, check bug
toolkit in 24-48 hours.<br>
<br>
Looks like it's fixed in 6.1(3.3206.1), 6.1(4), and 7.0(1). What
version are you running?<br>
<br>
/Wes<br>
<br>
On Wednesday, January 27, 2010 12:14:32 PM, Voll, Scott
<a class="moz-txt-link-rfc2396E" href="mailto:Scott.Voll@wesd.org"><Scott.Voll@wesd.org></a> wrote:<br>
<blockquote
cite="mid:06D9FD985A42704BB0E8F483ACA3FE2E3F4037D5B4@miranda.wesd.org"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="Section1">
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">Where do
I find this “backtrace”
in the bug toolkit?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">Here is
my backtrace:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">#0
0x0032ca92 in strncpy ()
from /lib/tls/libc.so.6<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">#1
0x00e17f38 in OK_BOD_strncpy
() from /lib/csa/libcsa.so.6<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">#2
0x00e15570 in strncpy ()
from /lib/csa/libcsa.so.6<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">#3
0x080b26eb in
CQBE_Parser::qbeGet (pMsgBuf_=0x1756f000, pParsedMsg_=0x1755e5ec,
pQbeString_=0x2e312e36, pNextOffset_=0x1755e46c) at qbeparser.cpp:410<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">#4
0x080b4dc6 in CTIQBE::ProviderOpenCompletedEvent::qbeGet
(this=0x80b26eb, pMsgBuf_=0x175625c0, pNextOffset_=0x1755e46c) at
qbeparser.cpp:2847<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">#5
0x080b948c in
CQBE_Parser::qbeParse (this=0x175625a0, pInputMsg_=0x175625c0,
inputMsgLength_=89, pParsedMsg_=0x1755e5a0, parsedMsgBufferSize_=16384)
at
qbeparser.cpp:5542<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">#6
0x08095221 in
CCtiInterface::receiveLoop (this=0x0) at ctireceiver.cpp:428<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">#7
0x00000000 in ?? ()<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">Scott<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<div>
<div
style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span
style="font-size: 10pt; font-family: "Tahoma","sans-serif"; color: windowtext;">From:</span></b><span
style="font-size: 10pt; font-family: "Tahoma","sans-serif"; color: windowtext;">
Wes Sisk [<a class="moz-txt-link-freetext" href="mailto:wsisk@cisco.com">mailto:wsisk@cisco.com</a>] <br>
<b>Sent:</b> Wednesday, January 27, 2010 8:46 AM<br>
<b>To:</b> Voll, Scott<br>
<b>Cc:</b> Cisco VoIP (<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>)<br>
<b>Subject:</b> Re: [cisco-voip] FW: [RTMT-ALERT-CMPUB-Cluster]
CoreDumpFileFound<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">yep, it means your cef process generated a core
dump.
i.e. it crashed. this is the equivalent of windows dr.watson and
user.dmp.<br>
<br>
First level diagnosis:<br>
from the CLI use 'utils core list' to identify the core file and then
'utils
core analyze' to generate the backtrace from the core file. you
*should*
be able to search for the backtrace in bug toolkit to find the relevant
defect.
if btk is not cooperating then open a tac case and provide your CM
version and
the backtrace. That is adequate to identify the defect for known
crashes.<br>
<br>
Second level diagnosis:<br>
If the backtrace does not match a known signature then we have to
diagnose the
core. That requires:<br>
- the actual cef core file (core files may be very large)<br>
- the backtrace from the core file<br>
- cef traces for 1 hour leading up to the failure<br>
- possibly other traces such as cm SDI/SDL for the same timeframe<br>
<br>
/Wes<br>
<br>
<br>
On Wednesday, January 27, 2010 10:41:41 AM, Voll, Scott <a
moz-do-not-send="true" href="mailto:Scott.Voll@wesd.org"><Scott.Voll@wesd.org></a>
wrote:<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">I’m not
finding much on a Google
search. Any idea what this means?</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">I’m
guessing a Cisco Extended
Function crashed on my first node, but not quite sure what needs to be
done or
if this is a tac case.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">From a
TAC point of view which
RTMT logs should I be getting if I need to open a ticket?</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">This is
the first time I’ve seen
this error.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">Thanks</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">Scott</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">PS. CM
6.1.4-2000.2</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> </span><o:p></o:p></p>
<div
style="border-style: solid none none; border-color: -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span
style="font-size: 10pt; font-family: "Tahoma","sans-serif";">From:</span></b><span
style="font-size: 10pt; font-family: "Tahoma","sans-serif";"> <a
moz-do-not-send="true" href="mailto:RTMT_Admin@wesd.org">RTMT_Admin@wesd.org</a>
[<a moz-do-not-send="true" href="mailto:RTMT_Admin@wesd.org">mailto:RTMT_Admin@wesd.org</a>]
<br>
<b>Sent:</b> Wednesday, January 27, 2010 6:06 AM<br>
<b>To:</b> Voll, Scott<br>
<b>Subject:</b> [RTMT-ALERT-CMPUB-Cluster] CoreDumpFileFound</span><o:p></o:p></p>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size: 12pt; font-family: "Times New Roman","serif";">CoreDumpFileFound
TotalCoresFound : 1 CoreDetails : The following lists up to 6 cores
dumped by
corresponding applications. Core1 : Cisco Extended Functions
(core.13530.11.cef.1264601139) AppID : Cisco Log Partition Monitoring
Tool
ClusterID : NodeID : CM1 . The alarm is generated on Wed Jan 27
06:05:44 PST
2010. </span><o:p></o:p></p>
<pre><o:p> </o:p></pre>
<pre style="text-align: center;">
<hr align="center" size="4" width="90%">
</pre>
<pre><o:p> </o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>cisco-voip mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true"
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true"
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<p class="MsoNormal"><span
style="font-size: 12pt; font-family: "Times New Roman","serif";"><o:p> </o:p></span></p>
</div>
</blockquote>
<br>
</body>
</html>