<!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">
your CM thanks you. attempted registration that fails and/or
auto-registration that fails are very "expensive" processes on CM.
Addressing failed registration is on our "top 10" things to do when we
start on a critical account.<br>
<br>
/Wes<br>
<br>
On Monday, October 05, 2009 10:08:57 AM, Ted Nugent
<a class="moz-txt-link-rfc2396E" href="mailto:tednugent73@gmail.com"><tednugent73@gmail.com></a> wrote:<br>
<blockquote
cite="mid:22e6380b0910050708n100d669v41add66db1b06bc1@mail.gmail.com"
type="cite">
<div>Thank you sir I know exactly what the problem is now they have
2x vg248s which are only half configured pounding on the cluster</div>
<div><br>
<br>
<div class="gmail_quote">On Mon, Oct 5, 2009 at 9:58 AM, Wes Sisk <span
dir="ltr"><<a moz-do-not-send="true" href="mailto:wsisk@cisco.com">wsisk@cisco.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">
nblogpd - non blocking syslog proxy implemented because the original
syslog would go into blocking state which would cause any logging
process to also block. This was bad for ccm process when syslog got
too busy.<br>
<br>
messages were dropped - non blocking syslog implements a buffer. When
buffer is filled faster than it can be written to disk then messages
are dropped.<br>
<br>
how to fix? take a look at all syslogs (system,security,callmanager)
and see what is rapidly/frequently/consistently writing to the logs.
Address why that is happening.<br>
<br>
historically unconfigured or misconfigured devices have been leading
triggers. They cause transient connection attempts and registration
failed messages repeatedly.<br>
<br>
/Wes
<div class="im"><br>
<br>
On Monday, October 05, 2009 9:54:28 AM, Ted Nugent
<a moz-do-not-send="true" href="mailto:tednugent73@gmail.com"
target="_blank"><tednugent73@gmail.com></a> wrote:<br>
</div>
<blockquote type="cite">
<div class="im">
<p><font face="'Times New Roman'" size="4"><span
style="font-size: 16px;">After a new cluster upgrade to 7.1.2.31900-1
we're seeing this error logging about every 4-6 hours. I can't seem to
find any info on the nbslogpd service? Anyone know what this might be
about and how i might fix it? TIA</span></font></p>
<p><font face="'Times New Roman'" size="4"><span
style="font-size: 16px;"><br>
</span></font></p>
<p><span
style="font-size: 12pt; font-family: "Times New Roman","serif";">SyslogSeverityMatchFound
events generated: SeverityMatch - Alert nbslogpd[13840]:
72 messages were dropped SeverityMatch - Alert nbslogpd[13840]: 2
messages were
dropped </span></p>
</div>
<pre><hr size="4" width="90%">
_______________________________________________
cisco-voip mailing list
<a moz-do-not-send="true" href="mailto:cisco-voip@puck.nether.net"
target="_blank">cisco-voip@puck.nether.net</a>
<a moz-do-not-send="true"
href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
<br>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>