tcpdive.sh unable to find .config located under /usr/src/kernels/..

[keshavsp]

I'm not sure what the implication is but when I run tcpdive.sh, I see the following message regarding a missing file:

$ ./tcpdive.sh -v -R -f 50.1.2.2:*-50.1.2.4:53
Checking "/lib/modules/2.6.32-431.17.1.el6.x86_64/build/.config" failed with error: No such file or directory
$

When I try to search for the file, I note 'build' is linked to a different location under which .config is located:

$ ls -l /lib/modules/2.6.32-431.17.1.el6.x86_64/build 
lrwxrwxrwx. 1 root root 51 Jan 26 17:33 /lib/modules/2.6.32-431.17.1.el6.x86_64/build -> ../../../usr/src/kernels/2.6.32-431.17.1.el6.x86_64

$ ls -l /usr/src/kernels/2.6.32-573.12.1.el6.x86_64/.config 
-rw-r--r--. 1 root root 107139 Dec 15 16:49 /usr/src/kernels/2.6.32-573.12.1.el6.x86_64/.config
$

So, my question is, does the above error message matter for tcpdive.sh to function? If yes, how do I fix it?

Thanks in advance,

Keshav

[zhangskd]

Hi, this version of tcpdive is for kernel 2.6.32-431.17.1.el6.x86_64, so ls -l /usr/src/kernels/2.6.32-431.17.1.el6.x86_64/.config instead of 2.6.32-573.12.1.el6.x86_64.

If the file does lose, a reinstallation of kernel-devel-2.6.32-431.17.1.el6.x86_64.rpm is suggested.

[megarzzy]

i encounter the same problem
[root@localhost zzy]# ll /lib/modules/2.6.32-431.el6.x86_64/
total 3524
lrwxrwxrwx. 1 root root 46 May 12 2014 build -> ../../../usr/src/kernels/2.6.32-431.el6.x86_64
drwxr-xr-x. 2 root root 4096 Nov 22 2013 extra
because build is a soft link
so Checking "/lib/modules/2.6.32-431.el6.x86_64/build/.config" failed with error: No such file or directory .
but i do not how to solve the problem .also i reintall the " kernel-devel-2.6.32-431.17.1.el6.x86_64.rpm " for many times

[megarzzy]

drwxr-xr-x. 22 root root 4096 Feb 25 09:02 build
lrwxrwxrwx. 1 root root 46 May 12 2014 build_bak -> ../../../usr/src/kernels/2.6.32-431.el6.x86_64
I rename the build to build_bak ,then mkdir build,cp all from /usr/src/kernels/2.6.32-431.el6.x86_64,

error disappear,but new error comes

root@localhost tcpdive-master]# ./tcpdive.sh -L -t 10
semantic error: while resolving probe point: identifier 'kernel' at ./src/estab.stp:65:2
source: kernel.function("inet_csk_accept").return
^

semantic error: missing x86_64 kernel/module debuginfo [man warning::debuginfo] under '/lib/modules/2.6.32-431.el6.x86_64/build'
semantic error: while resolving probe point: identifier 'kernel' at :15:2
source: kernel.statement("tcp_rcv_state_process@net/ipv4/tcp_input.c:5830")
^

semantic error: while resolving probe point: identifier 'estab' at :12:7
source: probe estab.* {}
^

semantic error: probe point mismatch (alternatives: Accept Estab) didn't find any wildcard matches: operator '' at :12:13
source: probe estab. {}
^

semantic error: while resolving probe point: identifier 'kernel' at ./src/close.stp:15:2
source: kernel.function("tcp_set_state")
^

semantic error: while resolving probe point: identifier 'kernel' at :83:2
source: kernel.function("inet_sock_destruct")
^

semantic error: while resolving probe point: identifier 'kernel' at ./src/recv.stp:12:2
source: kernel.function("tcp_event_data_recv")
^

semantic error: while resolving probe point: identifier 'kernel' at :119:2
source: kernel.statement("tcp_ack@net/ipv4/tcp_input.c:3756")
^

semantic error: while resolving probe point: identifier 'kernel' at ./src/rtt.stp:54:2
source: kernel.function("tcp_set_rto")
^

semantic error: while resolving probe point: identifier 'kernel' at :12:2
source: kernel.function("tcp_valid_rtt_meas")
^

semantic error: while resolving probe point: identifier 'kernel' at ./src/send.stp:12:2
source: kernel.statement("tcp_write_xmit@net/ipv4/tcp_output.c:1785")
^

semantic error: while resolving probe point: identifier 'trans' at :14:7
source: probe trans.* {}
^

semantic error: probe point mismatch (alternatives: Recv RecvACK Rto Rtt Send) didn't find any wildcard matches: operator '' at :14:13
source: probe trans. {}
^

semantic error: while resolving probe point: identifier 'kernel' at ./src/retrans.stp:34:2
source: kernel.statement("tcp_fastretrans_alert@net/ipv4/tcp_input.c:3139")
^

semantic error: while resolving probe point: identifier 'kernel' at :220:2
source: kernel.function("tcp_try_undo_partial")
^

semantic error: while resolving probe point: identifier 'kernel' at :233:2
source: kernel.statement("tcp_process_frto@net/ipv4/tcp_input.c:3649")
^

semantic error: while resolving probe point: identifier 'kernel' at :103:2
source: kernel.statement("tcp_retransmit_skb@net/ipv4/tcp_output.c:2146")
^

semantic error: while resolving probe point: identifier 'kernel' at :137:2
source: kernel.statement("tcp_fastretrans_alert@net/ipv4/tcp_input.c:3039")
^

semantic error: while resolving probe point: identifier 'kernel' at :66:2
source: kernel.statement("tcp_retransmit_timer@net/ipv4/tcp_timer.c:334")
^

semantic error: while resolving probe point: identifier 'kernel' at :207:2
source: kernel.function("tcp_try_undo_loss")
^

semantic error: while resolving probe point: identifier 'kernel' at :171:2
source: kernel.function("tcp_try_undo_recovery")
^

semantic error: while resolving probe point: identifier 'retran' at :17:7
source: probe retran.* {}
^

semantic error: probe point mismatch (alternatives: FrEvent FrUndo FrtoUndo PktDistr RecoverTime ToEventDistr ToUndo UndoEvent) didn't find any wildcard matches: operator '' at :17:14
source: probe retran. {}
^

Pass 2: analysis failed. [man error::pass2]

[zhangskd]

The kernel version you are using is 2.6.32-431.el6.x86_64? Not this version.
Due to the use of systemtap, a strictly match of kernel version is required.
This version of tcpdive is for 2.6.32-431.17.1.el6.x86_64, the packages needed are listed in README and their download addresses are in the PACKAGES part.

[pmcgleenon]

I had the same problem

./tcpdive.sh -d -L -H -C -p 80
Checking "/lib/modules/2.6.32-431.17.1.el6.x86_64/build/.config" failed with error: No such file or directory

I fixed it by installing the correct kernel-devel package:

kernel-devel-2.6.32-431.17.1.el6.x86_64.rpm

Maybe worth updating the PACKAGES documentation to highlight this