similar to: Diagnosing into server crash

Can i use dtrace to anlayze my core files ? -- This message posted from opensolaris.org

Hi, we are developing and operating an very critical application in the financial sector. Now our customer wants us to report performance data (roundtrip times of the messages routed). My idea is using dtrace to measure the times with the pid provider catching the timestamps on entry of the in and out functions of the processes. Now my questions ;-): 1) Is this an appropriate method to monitor

Dear Experts, My customer is migrating to Solaris 10 from Solaris 8 and have asked me to determine if: With Dtrace, is the user limited to probing only processes they own? The customer has a general security requirement to control user access via management of privileges. Currently, on Solaris 8, LDAP is strongly while RBAC is weakly applied. This will likely change in the Solaris 10 production

How do I find out why df -k is taking soo long to respond only sometimes? -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?

Hi, I am tracking down a problem and would like to know how I can follow a forked process with my dtrace script, or how I can trace a dynamic library. Here is the problem. I am tracing dtlogin, and specifically I am trying to determine what error libpkcs11`<routine> is returning. It turns out dtlogin forks a lot of processes, and I believe the second forked process is the one that winds

Hi all, I have questions about something I observed just now: 1) on AMD64, S10u1: # dtrace -n ''fbt::copystr:entry{printf ("%p\n", args[0]);}'' -c /bin/pwd dtrace: invalid probe specifier fbt::copystr:entry{printf ("%p\n", args[0]);}: in action list: index 0 is out of range for fbt::copystr:entry args[ ] but # dtrace -n ''fbt::copystr:entry{printf

Hi there, I''ve been using OpenSolaris for three months now, and I''ve started to get interested about to get my hands dirty with DTrace. Since I have an strong GNOME background, I would like to use it to help GNOME developers to find performance problems. Federico Mena Quintero, one of the Novell GNOME guys is one of the people that are working on GNOME performance stuff. He

Hiya, I''m trying to track down some throughput latency that our customer seems to be attributing to our product, I can''t see what he''s talking about, but I want to try and get some deeper granularity than I might get with something like smokeping, and maybe even see if its down to something tunable on our end. I''ve been looking for some examples on how

Hi, Can I use DTrace to determine memory status? 1.Total Physical Memory, Used Memory. 2.Total Swap Space and Used Swap Space. I did find few DTrace scripts but had too much in them and I am unable to chop off unwanted lines of code due to lack of knowledge. It will be very helpful if some one can share the piece of code that serves my purpose as mentioned above. Regards, Ramesh. Ramesh

Hi, Chris (cc) and I try to get the SGE master monitor work with Apple Leopard dtrace. Unfortunately we are stuck with the error msg below. Anyone having an idea what could be the cause? What I can rule out as cause is function inlining for the reasons explained below. Background information on SGE master monitor implementation is under http://wiki.gridengine.info/wiki/index.php/Dtrace

Is there any way to get printf type functionality inside the kernel from dtrace probes. Basically I want to dump progress through flow in my device driver. Something like: DTRACE_PRINTF("Inside chip reset, mailboxes %x %x %x %x %x %x %x %x", mb1, mb2, .....); ... ... DTRACE_PRINTF("reset failed: reason %s", failure_reasons[err]); I may have several such probes and they may

Hello, I wanted to enable tracing in user process. but following example from guide is not working. pid$1::$2:entry { self->trace = 1; } pid$1::$2:return /self->trace/ { self->trace = 0; } pid$1:::entry, pid$1:::return /self->trace/ { } I am getting error like invalid probe description ..... undefined macro variable in probe description. pid$target:user lib:user function:entry

G''Day Folks, I''ve found another use of dtrace, this makes your console keyboard sound like a typewriter. http://www.brendangregg.com/DTrace/typewriter-0.70.tar.gz I''ve only tested it on an UltraSPARC 5 and a Pentium laptop so far, more to follow. Ok, sorry, not actually a practical use of DTrace. :) Enjoy! Brendan [Sydney, Australia]

Hi All, Can I get Dtrace command, which is useful for regular system administration like performance issue. Advance Thanks Muthu -- This message posted from opensolaris.org

Hola, I am trying to isolate the memory leak I suspect in a mailman installation ? I found: http://blogs.sun.com/sanjeevb/date/200506 It gives an error: god at irt-smtp-02:~ 9:21am 65 # ./memleak.d 10312 dtrace: failed to compile script ./memleak.d: line 3: probe description pid10312:libc.so.1:malloc:entry does not match any probes I am on SunOS 5.10 Generic_127112-07 i86pc i386 i86pc Are

I''m a newbie as dtrace, but couldn''t find an answer to this by searching : For example, I have function "lsearch" which is called in many different places. It''s also called by "composemessage". I have been able to successfully create a script which show the return values of "lsearch". Now what I would like to do, is for it to only show the

[1] Predicates in one-liners I would like to list the probe modules in my executable and then dynamically create a dscript to trace execution of those modules alone (by excluding the 3rd party and system libraries). I tried the below script without success. The conditional given in the predicate is not taking effect. Why is this so ? $ dtrace -ln ''pid$target:::

Hi Expert I want to use dtrace to monitor the content change of one file. I made following scripts, #!/usr/sbin/dtrace -s inline int MYPID = $1; syscall::write:entry /pid == MYPID/ { tracemem(arg1, arg2); printf("\n"); } It always has an following error bash-3.00$ sudo dumpFIFO.dtrace 3836 dtrace: failed to compile script ./dumpFIFO.dtrace: line 19: tracemem( ) argument #2

A complex data structure stored in the shared-memory. Couple of processes attach to the shared-memory... Some of them spawn child procs... Two processes have change notification mechanism encoded... Basically the producer timestamps and the consumer compares the timestamp against it''s snapshot, if they differ then does use a semaphore to lock and gather critical data and replaces the

everyone, Just out of curiosity, I did a dtrace -n ''syscall:::entry { @num[execname, probefunc] = count(); }'' and looked at the entries produced by ''rm''. I see everything that rm did, *except* the unlinkat - which is unfortunate because I want to trace which processes have deleted which files. So - does dtrace contain unlinkat as a probe for a system call?