I have a setup in which logman.exe does not stop automatically, and it accumulates lots of memory. So I want to know in which cases the logman.exe is not stopped automatically.

Question

I have a setup in which logman.exe does not stop automatically, and it accumulates lots of memory. So I want to know in which cases the logman.exe is not stopped automatically.

Answer 1

Hello

Thank you for posting in Microsoft Community forum.

logman.exe is a command-line tool that you can use to create and manage Event Trace Session and Performance logs. The logman start command starts a data collector and sets the begin time to manual, while the logman stop command stops a Data Collector Set and sets the end time to manual.

In normal operation, logman.exe should stop when the data collection is complete or when the logman stop command is issued. However, there could be several reasons why logman.exe might not stop automatically:

Configuration Issues: If the data collector set is not configured correctly, logman.exe might not stop as expected. For example, if the stop condition is not set or if it’s set to an unusually high value, logman.exe might continue running indefinitely.

Resource Issues: If the system is under heavy load or if there are resource constraints (like low memory or high CPU usage), logman.exe might not be able to stop as expected.

Software Issues: There could be a bug in the software causing logman.exe to not stop automatically. This could be a bug in logman.exe itself or in the underlying Windows operating system.

Permissions Issues: If logman.exe does not have the necessary permissions to stop the data collector set, it might continue running.

If logman.exe is consuming a lot of memory and not stopping as expected, it might be worth checking the configuration of your data collector sets and ensuring that your system has sufficient resources.

Best Regards,

Wesley Li

Answer 2

Thanks for your reply.

I have also observed one more issue in my setup. Some of the logman data collector sets are taking time to start. Some are taking 2 mins time, and some take 3 mins time to start.
Is there any case in which logman data collector sets take this type of issue? or what should be the reason for this issue?
Also, the logman.exe process is consuming too much memory in my setup. So, what should be the reason for this?

Answer 3

One possible reason for the delay could be conflicts with other processes or data collector sets. For instance, the “NT Kernel Logger”, a kernel event provider, cannot be accessed at the same time by multiple consumers (e.g., multiple data collector sets). If your Data Collector Set (DCS) is collecting kernel logger information, you might experience delays. It’s recommended to stop the resource monitor before running your DCS, or if running multiple DCSs that collect kernel logger info, run one DCS at a time.

windows server 2008 - Perfmon - Cannot start data collector set - Server Fault

As for the high memory usage by logman.exe, it could be due to the size and complexity of the data being collected. If logman.exe is consuming a lot of memory and not stopping as expected, it might be worth checking the configuration of your data collector sets and ensuring that your system has sufficient resources. If the issue persists, you may want to consider optimizing your data collector sets or upgrading your system resources.