Two Minute Drill: LOGMAN.EXE

re: Two Minute Drill: LOGMAN.EXE

Mike — Tue, 30 Nov 2010 14:57:50 GMT

I was having the same problem Ed Sun had and it was just because the remote machine from which I was collecting the performance counters was too busy.

re: Two Minute Drill: LOGMAN.EXE

Mat Mirabito — Wed, 20 Oct 2010 00:13:51 GMT

For anyone having the problem that MafruhaUnited was reporting, it's likely that you need to save the import file as Unicode instead of ANSI.

re: Two Minute Drill: LOGMAN.EXE

Kishore — Wed, 05 May 2010 10:11:05 GMT

How to run multiple counter log files using single command.

re: Two Minute Drill: LOGMAN.EXE

MafruhaUnited — Thu, 11 Mar 2010 22:34:29 GMT

How do I match logman counter interval time and create new file on each interval of collection.

My colde is like this, but it is not showing me the result I want to have.

"-si 00:00:15 -cnf 00:00:15" does not work togather

re: Two Minute Drill: LOGMAN.EXE

MafruhaUnited — Wed, 10 Mar 2010 15:58:16 GMT

Can anyone give me a hint as Why my logman Import and export command is not working?

The comand is as :

C:\Windows\system32>logman import daily_perf_log -xml "C:\PerfLogs\daily_log.x

Error:

Unspecified error

Thanks,

MafruhaUnited

re: Two Minute Drill: LOGMAN.EXE

Thomas — Thu, 04 Feb 2010 10:27:51 GMT

I've made a batch script, where during installation of the server (Windows 2003 or 2008) a counter log is created.

On Windows 2008 it creates perfectly, but doesn't start even if the schedule is set ... so I've so start it manually.

On Windows 2003 it creates perfectly and starts if the log file type ISEN'T binary circular file. If it's one of the other types it starts, but runs only for about 5 mins. even if I had set a max log on 100 MB and overwrite the file .....

Any good ideas?????

Hope so ... :o) Cheers ....

re: Two Minute Drill: LOGMAN.EXE

Balaji — Tue, 12 Jan 2010 10:45:36 GMT

Hi, What is the use of -r option? Can someone explain it with an example?

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!

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

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