similar to: DTrace Toolkit tcpsnoop

Hello, I have the following problem: On a solaris 10 machine, with 5 "zones" there is a process that is talking to the wrong db server. I need to find out which process this is, so I can analize this further. I have tried to doing this using tcpsnoop from the DTrace toolkit, but without success. This is what I''ve done. First I started tcpsnoop, dumping it''s output

Dear dtrace Experts, I have seen some dtrace utilities like opensnoop and execsnoop etc. My interest is to write a simple script that can snoop the files which uses the 3 syscalls like open,create,unlink. I have gone through dtrace oneliners that can do the same : dtrace -n ''syscall::open*:entry { printf("%s %s",execname,copyinstr(arg0));}'' dtrace -n

Folks, I came across an IPv6 snv_31 network driver problem during testing. I can "ping" an IPv6 address, but when I try and log on to the IPv6 address I get an RPC failure. Not knowing much about dtrace, I thought I would give some of the networking dtrace scripts a try that I found here: http://www.opensolaris.org/os/community/dtrace/dtracetoolkit/ (tcptop or any other script in the

Is there any work on keeping DTraceTools up to date with the latest snv builds. These scripts are pretty useful and help get a novice dtrace user like me doing useful work quickly. Specifically the tcp stack tools like tcptop and tcpsnoop don''t work with later OpenSolaris builds. Thanks, Gary -- This message posted from opensolaris.org

HI, T5220, S10U4 + patches mdb -k > ::memstat While above is working (takes some time, ideally ::memstat -n 4 to use 4 threads could be useful) mpstat 1 shows: CPU minf mjf xcal intr ithr csw icsw migr smtx srw syscl usr sys wt idl 48 0 0 1922112 9 0 0 8 0 0 0 15254 6 94 0 0 So about 2mln xcalls per second. Let''s check with dtrace:

We started seeing odd behaviour with clients somehow hammering our ZFS-based NFS server. Nothing is obvious from mpstat/iostat/etc. I''ve seen mention before of NFSv3 client dtrace scripts, and I was wondering if there ever was one for the server end, displaying top talkers, writes/reads, or locations of such to nail down abusive clients short of using snoop/tcpdump to nail down via

I tried some of the scripts in the toolkit (opensnoop, execsnoop, dtruss), and I keep seeing errors like this: dtrace: error on enabled probe ID 3 (ID 113: syscall::exece:return): invalid kernel access in action #5 at DIF offset 0 Anyone know what could be the problem? TIA This message posted from opensolaris.org

I am quite unfamiliar with DTrace (and even more with Solaris/Linux/other) kernel internals. I recently had to help look into an issue where an application apparently sent a UDP packet, but it did not appear on the wire, nor did snoop(1)ing the interface show it, so the assumption is that it was lost (or misdirected) somewhere in the IP stack. We did use Dtrace with syscall::sendto:entry/exit to

G''Day Folks, I''ve just rewritten iosnoop so that uses command line arguments (I caved in and used a little Bourne shell for this - hence it''s lost it''s ".d" extension). It''s much more useful now. # iosnoop -h USAGE: iosnoop [-a|-A|-Degstv] [-d device] [-f filename] [-m mount_point] iosnoop # default output

Hi I have a process which reads a socket using recvfrom. After sometime, for no apparent reason, recvfrom exits with an EINTR causing the sender to barf too. Basically the socket on which these processes were communicating no longer exists. On writing a dtrace, I could determine that a signal was received at that socket causing the EINTR. I do not know of way to see who sent the signal (which

I''m working on a case where customer has a 3rd party streams driver/module, called uplink, which sits over Sun''s ce driver. This 3rd party module is used by the telco to perform telco grade NIC failover. The customer was given an IDR ce driver, to avoid a panic they were given. The IDR driver was successful in avoiding the panic, but now the customer is getting many

Hi all, I am installing a zone onto two different V445s running S10U4 and the zones are taking hours to install (about 1000 packages), that is, the problem is identical on both systems. A bit of trussing and dtracing has shown that the pkginstalls being run by the zoneadm install are making door_call calls to nscd that are taking very long, so far observed to be 5 to 40 seconds, but always in

Hi, I am new to DTrace. Want to capture (for specific port #s) the loopback interface (lo0) tcp message flow with the complete message body. Is this possible with DTrace? Are any examples available? Thanks, Joe ____________________________________________________________________________________ Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase.

Hi, I want to disable extended attributes in my zfs on s10u4. I found out that the command to do is zfs set xattr=off <poolname>. But, I do not see this option in s10u4. How can I disable zfs extended attributes on s10u4? I''m not in the zfs-discuss alias. Please respond to me directly. Thanks Balaji

I have a number of systems running solaris10 and i see the package and binary for dtrace installed however whenever we try to run anything we get this error dtrace: failed to initialize dtrace: DTrace device not available on system the only system in which i dont have this error is the development server that has the full solaris 10 install while others are minimized, do i need additional

Hi Max/DTrace list, > At any rate, without the -C, I can''t use #include <sys/stream.h>. > Without the #include <sys/stream.h>, I can''t use the M_DATA. > As it is, I get the following: > > # ./strrput.d 0xd595a6c0 <-- this is a vnode for a socket > ftp is using (not important here) > dtrace: failed to compile script ./strrput.d: line 7: >

Dtrace does work on some workstation, such as as follows, ----------------------------------------------------------- bash-3.00# dtrace -s ./mem.d `pgrep test` dtrace: script ''./mem.d'' matched 5 probes ^C bash-3.00# uname -a SunOS ftp 5.10 Generic_118833-17 sun4u sparc SUNW,Sun-Blade-100 bash-3.00# dtrace -V dtrace: Sun D 1.1

All, With Jon Haslam''s exciting news about the DTrace doc wiki (if you haven''t seen it yet, make your way to http://wikis.sun.com/display/DTrace), and with some of the discussion with the Apple folks, I''m wondering if the time isn''t right for something of a DTrace summit, perhaps as an unconference. The idea here would not be a DTrace user group (though that

Hi All, One of the customer is seeing the following error messages. He is using a S10U1 system with all latest patches. Dtrace script is attached. I am not seeing these error messages on S10U2 system. What could be the problem? Thanks, Gangadhar. ------------------------------------------------------------------------ rroberto at njengsunu60-2:~$ dtrace -AFs /lib/svc/share/kcfd.d dtrace:

X.Org has adopted GNU autoconf as its build configuration mechanism, so when I integrated the dtrace probes, I checked to see if they should be built using this test, checking for the existence of a program named "dtrace" in the path: dnl Check for dtrace program (needed to build Xserver dtrace probes) AC_ARG_WITH(dtrace, AS_HELP_STRING([--with-dtrace=PATH], [Enable dtrace