Two Minute Drill: LOGMAN.EXE

re: Two Minute Drill: LOGMAN.EXE

Trang Nguyen — Wed, 25 Jun 2008 04:25:06 GMT

Hi,

I'm reading this artical and it seems to say that the IMPORT/EXPORT options are supported in WinXP. I've tried that on my WinXP but it doesn't seem to recognize these verbs.

Is there any specific component/version/SP/etc that I need to have in order to have that work?

If you could answer to my email at tnguyen@ixiacom.com, I will greatly appriciate that.

Thanks,

Trang.

re: Two Minute Drill: LOGMAN.EXE

Ed Sun — Tue, 01 Jul 2008 01:54:45 GMT

I created a performance counter log that queries some logical drive data from many systems, and I use logman to control when I'd like to collect the data. I initially had 42 systems I collected data from. But recently I increased the number of the systems to 96, and I started to get the following error:

C:\>logman start "DB Drive Space Monitor"

Error:

Collection "DB Drive Space Monitor" did not start, check the application event log for any errors.

C:\>

The counter log actually started OK, and the data collection went OK as well, with no error in the event log. But why am I getting this error? How can I stop it? It appears to be a scalability issue of the tool.

Please assist. Thanks.

re: Two Minute Drill: LOGMAN.EXE

Obaid Shirwani — Fri, 25 Jul 2008 09:01:26 GMT

I am trying to limit the logs generated to some specific services only. i am using this line

\Process(*my_service_name*)\ID Process but its generating the same logs with all the service names mentioned. any suggestions. Thanks a million

re: Two Minute Drill: LOGMAN.EXE

BrianS — Tue, 16 Jun 2009 22:45:44 GMT

Great Article BTW! I am having issues with the import not taking in the user account specified in the xml file, any thoughts? It is currently defaulting to use a system account. Thanks again...

re: Two Minute Drill: LOGMAN.EXE

SusieN — Tue, 25 Aug 2009 13:40:36 GMT

We have a number of counters set up from one server to a series of other servers. In order to ensure access across the domain to these servers, the counters have been set up with login credentials. We have tried to schedule a script to run each morning and update the counters so that we can run them across a week without manually changing the counter schedule for each. However, the script only works if the counters are run as <Default> otherwise it is looking for the login credentials. Is there any way of supplying a login and password as part of the logman command line?

re: Two Minute Drill: LOGMAN.EXE

SteveDJ — Fri, 04 Sep 2009 02:04:04 GMT

There is a slight mistake in the samples above. He uses "-si 2" and states that it "sets the Capture Interval at 2 hours"; this is incorrect - it sets the interval to 2 SECONDS.

If you look at the context help, it shows the si option as taking the following: -si <[[hh:]mm:]ss>

Note that if just the number 2 is given, it is 2 seconds, not 2 hours. Adding a second number (i.e. 02:00) means 2 minutes. If you want 2 hours like in the sample, you need to specify 02:00:00

re: Two Minute Drill: LOGMAN.EXE

CC Hameed — Mon, 21 Sep 2009 15:09:48 GMT

@ SteveDJ - thanks for pointing this out. I've corrected the error!

- CC

re: Two Minute Drill: LOGMAN.EXE

Tom Dietrich — Wed, 28 Oct 2009 13:50:45 GMT

Hello,

I've got a nightly batch file in place to stop my counters, zip them, move them, and then start them again. The start command looks like this:

logman -s P1CAS12 start "P1EXB01 - Exchange SP1" -v -cnf 4:00:00

The command starts the counter fine, but the -cnf switch seems to be ignored. -cnf = create new file, and it's set for 4 hours, but it doesn't work. The counter runs all day until the nightly batch file stops it for the maintenance process.

The problem is that this leaves me with a single 400MB log file, which is a nightmare to parse when troubleshooting. We really need the switch to work and create a new file every 4 hours.

The process works fine if I use the PERFMON GUI to start my counters using the Schedule tab and define the 4 hour interval. But this needs to be automated.

Any ideas why the -cnf switch isn't working right?

Thanks!