The Dirtracer Blog is here!

Welcome to the new Dirtracer Blog!


I am Lee Trujillo, an Engineer supporting the Sun Java Directory Server since December 2003.  I am also the creator of Dirtracer, Sun's number one tool for tracing issues for our Sun Directory Server.

Early in 2004, I saw that the support organization had no formalized standard for asking for and obtaining data related to issues surrounding the Directory Server, so I created Stracer (Stack Tracer), the predecessor to Dirtracer (Directory Tracer).  Stracer 1.0 consisted of 169 lines of shell script that basically gathered pstacks, prstats and top output from a running ns-slapd process.  Conversely, Dirtracer 6x (2008) is a complex 2,590 line script of functions that can be combined in many ways to gather Directory data based on problem type.

Dirtracer is a troubleshooting tool designed to help reduce resolution time on complex Directory Server problems and to ease the data-gathering process for Sun's customers.

Dirtracer is part of the GDD (Gathering Debug Data) suite of tools and has already been used for years to tackle some of the most persistent, difficult Sun Java Systems Directory Server problems faced in the field.  For problems such as server hangs, crashes, and high cpu utilization, Dirtracer simplifies the sampling of system resources and crash data in order to help identify trends.

Save you and your customers time and aggravation -- discover the power of Dirtracer.

I expect Dirtracer version 6.0.6 to be available later today on the external Big Admin Administration Portal site for Customer and partner download.

[LT]
Comments:

If I set following value , how long does dirtracer take to complete.
MEM_LEAK_TRACKING="1"
NUMBEROFCHECKS="500" # Number of checks: total number of loops
INTERVAL="1800" # Interval: seconds between loops

Is it 12 loops per day and therefor 500/12 = 41.6 days

Posted by rasika sudasinghe on July 26, 2009 at 11:27 PM MDT #

Hi Rasika,

This would work out to be 10.41 days actually.

I quickly setup a config file using Configurator option 5:

Memory Leak [5]

I then chose 500 for the number of checks:

NUMBEROFCHECKS="500" # Number of checks: total number of loops
INTERVAL="1800" # Interval: seconds between loops

So doing the math we have 1800 (interval in seconds) x 500 (number of checks) which comes out to 900000 total seconds (approx 15000 seconds).

When DirTracer runs, it shows this same information. Remember, DirTracer loops based on the INTERVAL so a 1800 second interval means each loop will run for 1800 seconds or 30 minutes.

\* Dirtracer mainloop will run for [900000 sec. About 15000 min.]

So with...

15000 minutes divided by 60 minutes in an hour = 250 hours
250 hours divided by 24 hours in a day = 10.41 days.

Regards,

Lee

Posted by Leroy Trujillo on July 27, 2009 at 01:07 AM MDT #

Post a Comment:
  • HTML Syntax: NOT allowed
About

A Tech Blog about the Sun Java Systems Dirtracer Toolkit. Dirtracer and this blog written and maintained by Lee Trujillo an Oracle Senior Principal Support Engineer.

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today