dcrclient.log file is large, is it needed?

Answered Question

I'm getting pop-up messages from my LMS 3.0 stating /var is near full. Upon doing some digging, I found the dcrclient.log file in the /var/adm/CSCOpx/log directory. It's over 10 Gig and I'm not sure what it is for.

Can anyone shed some light on this? Could it be a debug that I forgot to turn off? Why is it so large? Can I just clean it up? etc...

Thanks,

I have this problem too.
0 votes
Correct Answer by Joe Clarke about 7 years 3 months ago

Actually, nevermind. I suspected perhaps the files were corrupt, but it doesn't matter. Either wa, the solution will be to replace the originals with ones with debugging disabled. If you replace the three original files under /opt/CSCOpx/lib/classpath/com/cisco/nm/dcr with these versions, then restart dmgtd, debugging for DCR, DCR's client APIs, and CSTM will be disabled.

NOTE: make sure the resulting three files have the following permissions after replacing the originals:

-rwxr-xr-x 1 casuser casusers

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Lucien Avramov Thu, 08/13/2009 - 09:04

Per the description on CS Log:

Enables/Disables debug for the component that provides a common repository of devices, device attributes, and the credentials required to manage devices.

Make sure to go to : Common Services -> Server -> Admin -> CS Log Configurations.

Choose component : Device and Credentials Repository and click on disable for debug mode.

You can stop the daemons (./etc/init.d/dmgtd stop) and then clean the file (do not delete it) and restart the daemons (./etc/init.d/dmgtd start)

Joe Clarke Thu, 08/13/2009 - 09:07

No, dcrclient.log is part of the DCR process, and logs details about client connections to DCR. This is typically interprocess connections, but it can also be dcrcli interactions. It should not be deleted.

Joe Clarke Thu, 08/13/2009 - 09:05

Most likely this is due to debugging that was left on. Go to Common Services > Server > Admin > CS Log Configurations, and make sure debugging is disabled for Device and Credential Repository. Then run:

/opt/CSCOpx/bin/logrot_trunc /var/adm/CSCOpx/log/dcrclient.log

That should reduce the size to zero bytes. If the file immediately jumps back to 10 GB, then shutdown dmgtd, run the same logrot_trunc command, then restart dmgtd.

I performed the above and it did clear out the file. I turned off debugging also. I'm actually not sure if it was on or not, b/c I reset debugging on the entire system.

The file is already over 5 Meg. It's growing fast too. I double checked and debugging is disabled. Could this be due to the # of devices we're managing. The server is question is a the Slave system. The Master is also an LMS 3.0 system and it's managing over 4000 devices.

I'll keep my eye on the file size. Maybe it will steady out.

Thanks for the quick response,

Joe Clarke Thu, 08/13/2009 - 10:08

It could be indicative of another problem. Compress the log, and post it.

Joe Clarke Thu, 08/13/2009 - 10:23

Debugging is still enabled. Post the /opt/CSCOpx/lib/classpath/com/cisco/nm/dcr/log4j-dcrclient.properties , /opt/CSCOpx/lib/classpath/com/cisco/nm/dcr/log4j-dcr.properties, and /opt/CSCOpx/lib/classpath/com/cisco/nm/dcr/log4j-dcrclient1.properties files.

Lucien Avramov Thu, 08/13/2009 - 10:30

You can see that debugging is enabled as it's mentioned in the log file:

[Thread-4] DEBUG CTM.client

This is populating quickly the log file.

Posting the properties file requested will help.

Joe Clarke Thu, 08/13/2009 - 10:52

As suspected, debugging was still enabled. Replace these files with the ones in my previous post, verify permissions, restart dmgtd, and the dcr*.log files should no longer grow.

Correct Answer
Joe Clarke Thu, 08/13/2009 - 10:51

Actually, nevermind. I suspected perhaps the files were corrupt, but it doesn't matter. Either wa, the solution will be to replace the originals with ones with debugging disabled. If you replace the three original files under /opt/CSCOpx/lib/classpath/com/cisco/nm/dcr with these versions, then restart dmgtd, debugging for DCR, DCR's client APIs, and CSTM will be disabled.

NOTE: make sure the resulting three files have the following permissions after replacing the originals:

-rwxr-xr-x 1 casuser casusers

Joe Clarke Thu, 08/13/2009 - 11:35

The permissions are critical. I have a feeling that's why you couldn't disable debugging in the GUI. Your original files were in tact.

Actions

This Discussion