CodeMeter logfiles

[Erik Bjornhage]

Hello,

We have a problem where the codemeter installation seems to create some ridiculously sized log files.

On some of our servers we have log files in the gigabyte size - and growing...

They are named "CmActDiagLog" as well as date and time stamp.

New ones are created daily and grow during the day to roughly 2 GB per file before the next one is created the next day. We have not found any way to control these and they grow rapidly enough that it floods the C-drive if we don't manage it regularly.

Any ideas or solutions would be appreciated.

[MinhNguyen · Accepted solution]

Hi Erik, I suggest checking to see if "Logging" function is turned on. Open Codemeter Control Center, File > untick Logging if it's ticked. Further explanation can be found here: https://wiki.tuflow.com/Codemeter_Enable_Logging

The CmActDiagLog basically keeps all the events that you see in the Events tab of Codemeter. If

Logging is enable, the logs won’t be deleted. Worst case scenario, they are safe to be deleted, so you may want to regularly clean it up if my suggestion above doesn’t work

[astridbr]

Hello,

we have the same problems, but our log-files have the size of 3,2GB... that is not funny...

Logging is NOT on, but the files were created. How can this be? Deleting all the files per hand?

Any other suggestions, please?

Thank you for your answers and your help

[MinhNguyen]

The file is created regardless of Logging option being on or off. Turning it off will make sure that old logs get deleted. I imagine if you leave the machine running continuously, new events keep being added to the log file, therefore it's getting big. You can safely delete the file manually as it contains just the log events.

[Erik Bjornhage]

Thank you @MinhNguyen 

From our understanding the logfiles that are created when Logging is enabled on the Server side are named CodeMeterYYY-MM-DD-Hr-Min-Sec.

These can be turned off through activating and deactivating logging.

We have also understood that there is a registry setting for log diagnose levels .

We are trying this and hoping that will solve the problem but there is no doubt the sizes of these log files can become an issue.

Thanks for the help