[cisco-voip] SyslogSeverityMatchFound on nbslogpd

[Ted Nugent]

Thank you sir I know exactly what the problem is now they have 2x vg248s
which are only half configured pounding on the cluster


On Mon, Oct 5, 2009 at 9:58 AM, Wes Sisk <wsisk at cisco.com> wrote:

>  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.
>
> 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.
>
> 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.
>
> historically unconfigured or misconfigured devices have been leading
> triggers.  They cause transient connection attempts and registration failed
> messages repeatedly.
>
> /Wes
>
> On Monday, October 05, 2009 9:54:28 AM, Ted Nugent <tednugent73 at gmail.com><tednugent73 at gmail.com>wrote:
>
> 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
>
>
>  SyslogSeverityMatchFound events generated: SeverityMatch - Alert
> nbslogpd[13840]: 72 messages were dropped SeverityMatch - Alert
> nbslogpd[13840]: 2 messages were dropped
>
> ------------------------------
>
> _______________________________________________
> cisco-voip mailing listcisco-voip at puck.nether.nethttps://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091005/e3d0c23d/attachment.html>