New to opensolaris and dtrace. I''m interested in the network scripts but I find that many don''t work. Should my expectations be low right now? I am running opensolaris on x86 and toolkit 0.99 Net/tcpsnoop_snv.d dtrace: failed to compile script Net/tcpsnoop_snv.d: line 214: conn_tcp is not a member of struct conn_s Net/tcpsnoop_snv "/usr/include/sys/modctl.h", line 318: major: argument mismatch dtrace: failed to compile script /dev/fd/3: "/usr/include/sys/modctl.h", line 318: syntax error near "1" Net/tcpsnoop "/usr/include/sys/modctl.h", line 318: major: argument mismatch dtrace: failed to compile script /dev/fd/3: "/usr/include/sys/modctl.h", line 318: syntax error near "1" Net/tcpsnoop.d dtrace: failed to compile script Net/tcpsnoop.d: line 210: failed to resolve `tcp_g_q: Unknown symbol name -- This message posted from opensolaris.org
Brendan Gregg - Sun Microsystems
2010-Mar-09 00:21 UTC
[dtrace-discuss] new dtrace toolkit?
On Mon, Mar 08, 2010 at 04:07:23PM -0800, Otto P. wrote:> New to opensolaris and dtrace. I''m interested in the network scripts but I find that many don''t work. Should my expectations be low right now?Only for networking, which is probably the most difficult area to start with. There is work underway for a stable DTrace TCP network provider; until that exists, any scripts written based on the unstable fbt provider tend to break from release to release, such as the tcpsnoop/tcptop scripts. This will get a lot better, but we aren''t there yet. There are quite a lot more TCP scripts I would like to write and add to the DTraceToolkit, but I''ve held back until the stable provider is available, otherwise it could just annoy people more. If you search previous posts on dtrace-discuss there are fixes for these scripts for certain releases. And I''ll take another swing on the next DTraceToolkit release. Brendan> I am running opensolaris on x86 and toolkit 0.99 > Net/tcpsnoop_snv.d > dtrace: failed to compile script Net/tcpsnoop_snv.d: line 214: conn_tcp is not a member of struct conn_s > > > Net/tcpsnoop_snv > "/usr/include/sys/modctl.h", line 318: major: argument mismatch > dtrace: failed to compile script /dev/fd/3: "/usr/include/sys/modctl.h", line 318: syntax error near "1" > > Net/tcpsnoop > "/usr/include/sys/modctl.h", line 318: major: argument mismatch > dtrace: failed to compile script /dev/fd/3: "/usr/include/sys/modctl.h", line 318: syntax error near "1" > > > Net/tcpsnoop.d > dtrace: failed to compile script Net/tcpsnoop.d: line 210: failed to resolve `tcp_g_q: Unknown symbol name > -- > This message posted from opensolaris.org > _______________________________________________ > dtrace-discuss mailing list > dtrace-discuss at opensolaris.org-- Brendan Gregg, Fishworks http://blogs.sun.com/brendan
Brendan Gregg - Sun Microsystems wrote:> On Mon, Mar 08, 2010 at 04:07:23PM -0800, Otto P. wrote: >> New to opensolaris and dtrace. I''m interested in the network scripts but I find that many don''t work. Should my expectations be low right now? > > Only for networking, which is probably the most difficult area to start with. > There is work underway for a stable DTrace TCP network provider; until that > exists, any scripts written based on the unstable fbt provider tend to break > from release to release, such as the tcpsnoop/tcptop scripts. This will get > a lot better, but we aren''t there yet. > > There are quite a lot more TCP scripts I would like to write and add to the > DTraceToolkit, but I''ve held back until the stable provider is available, > otherwise it could just annoy people more.I agree that networking has some difficult problems compared with other areas, but I don''t think that''s the only problem here. If folks actually want to rely on these scripts, perhaps they ought to be tested regularly, made the subject of integration requirements (so that others modifying the stack are required to update them), and even moved out of /usr/demo. That which isn''t tested doesn''t work. -- James Carlson 42.703N 71.076W <carlsonj at workingcode.com>
Otto, If you take the time to use google (or whatever search engine you prefer) to search the opensolaris.org dtrace archives, then you will see my fix for the broken dtrace networking scripts here: http://opensolaris.org/jive/thread.jspa?messageID=403388 I think the fix worked in OpenSolaris 2008.11, but I don''t really remember whether it worked in 2009.06 or not. The thing about the dtrace toolkit is that it doesn''t really seem to be maintained by Sun or Oracle, it''s maintained by one guy (Brendan Gregg) so it gets updated whenever the one guy who maintains it feels like updating it. -- This message posted from opensolaris.org
Otto, also, if you can reply to this discussion thread with your output for this command: cat /etc/release so people know what version of Solaris / OpenSolaris you''re running. -- This message posted from opensolaris.org
Otto, If you take the time to use google (or whatever search engine you prefer) to search the opensolaris.org dtrace archives, then you will see my fix for the broken dtrace networking scripts here: http://opensolaris.org/jive/thread.jspa?messageID=403388 I think the fix worked in OpenSolaris 2008.11, but I don''t really remember whether it worked in 2009.06 or not. The thing about the dtrace toolkit is that it doesn''t really seem to be maintained by Sun or Oracle, it''s maintained by one guy (Brendan Gregg) so it gets updated whenever the one guy who maintains it feels like updating it. -- This message posted from opensolaris.org