CSA : Event queue is full-Dropping event

Unanswered Question
May 11th, 2010

Hi,

I have currently a CSA v6.0.1.135 MC running with 3 CSA agent testmachines (winxpsp3). On the first day the CSA agent events were registered at the CSA MC. Since the day after the installation, no CSA events are appearing anymore on the MC. I checked the csalog.txt on the testmachines and MC and this log shows a lot of the following entries:

%CSA-6-TRACE: %[Component=Csamanager][PID=820]: Event queue is full-Dropping event #820

%CSA-5-FORWARD_EVENT_REMOTE_FAILED: %[Component=Csamanager][PID=820]: Failed to forward event number(s) 2-22 to component Csamcmanager60.

It seems like the event queue is full (local or MC?) and that the events are dropped, instead of uploaded to the MC.

Any idea what is causing the full event queue and how to solve this problem?

Thanks

Kind regards,

Nico

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
tsteger1 Wed, 05/12/2010 - 17:23

Never seen that one before and I've broken quite a few MCs

Is that snippet from the host or the MC?  Are they still registered?  Restarted everything and checked Windows event logs on all?

Deployed another agent kit to another host?

So many places to look...

Tom

nicocallens Mon, 05/17/2010 - 01:19

Hi Tom,

Thanks for your answer. The 3 agents are still registered and online. I even recreated and reinstalled the agent kits. The first day after the installation the agents register events on the MC after that day the event queue is full is appearing in the agents csalog.txt.

regards,

Nico

jan.nielsen Thu, 05/13/2010 - 06:15

Sounds alot like a bug i encounterede a few weeks ago, i believe it was in the leventmgr.exe on the agent there was some bug, we replaced it with the 6.0.2 Beta version of leventmgr.exe which fixed it, so there probably is a bugid on this now, you should try a TAC case i think.

nicocallens Mon, 05/17/2010 - 01:21

Hi Jan,

Thanks for sharing you CSA experience. I will inform with Cisco about the bug ID and open a TAC case.

regards,

Nico

Actions

This Discussion