CiscoWorks log overflooded

Unanswered Question
Nov 4th, 2008

Hi all

I have two logs which are overflooded. Can anyone tell me what these records indicate, and what to do?

In dmgtDbg.log these INFO records come again and again:

[Tue Nov 04 07:05:31 W. Europe Standard Time 2008][dmgrDbg]##### INFO ##### re-evaluate DbgLevel=0x0

[Tue Nov 04 07:05:37 W. Europe Standard Time 2008][dmgrDbg][dmgrDbg] getenv(PX_DBG)=NULL

[Tue Nov 04 07:05:37 W. Europe Standard Time 2008][dmgrDbg][dmgrDbg] getenv(PX_MY_DEBUG)=NULL

[Tue Nov 04 07:05:37 W. Europe Standard Time 2008][dmgrDbg][dmgrDbg] getenv(PX_MY_TRACE)=NULL

[Tue Nov 04 07:05:37 W. Europe Standard Time 2008][dmgrDbg][dmgrDbg] getenv(PX_DBG_LEVEL)=NULL

The CSDiscovery.log is growing very fast (maybe this is normal?)with records like this:

070027 [email protected]: [EvalTask-DiscoveryThreadPool-19/10.200.2.15]GeneralSystemAGI: eval() >>>

070027 [email protected]: [EvalTask-DiscoveryThreadPool-19/10.200.2.15]GeneralSystemAGI: eval() <<<

070027 [email protected]: [EvalTask-DiscoveryThreadPool-19/10.200.2.15]GeneralIpAddrAGI: eval() >>>

I regularly run the logbackup.pl that emptys the log. But the recomended filesize of 1024KBytes is soon reaced again.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 2 (1 ratings)
Loading.
Joe Clarke Tue, 11/04/2008 - 06:22

The messages in dmgtDbg.log are typical. You will just need to rotate this file when it gets too big. The log file size recommendations are on the low side, so I wouldn't worry about those.

As for the CSDiscovery.log, go to Common Services > Server > Admin > CS Log Configurations, and make sure CS Discovery debugging is disabled.

Nael Mohammad Sat, 05/28/2011 - 01:01

Use logrot.pl to have logs rotated automaticly from CSCOpx/bin/logrot.pl -c and the config file is stored under NMSROOT/objects/logrot.

Actions

This Discussion