systemtap-client doesn't work over the network
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemtap (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: systemtap
Description: Ubuntu 10.04.1 LTS
Release: 10.04
apt-cache policy systemtap-client
systemtap-client:
Installed: 1.0-2
Candidate: 1.0-2
Version table:
*** 1.0-2 0
500 http://
100 /var/lib/
Expected result:
Hello world test script should have worked, like it does on the localhost
Actual tesult:
The connection appears to be reset by the peer
root@u-laptop:~# stap-client -v -e 'probe begin { printf("Hello World!"); exit() }'
Attempting connection with nautilus:20227 using certificate database in '/etc/systemtap
Error in function PR_Connect: -5961: Connection reset by peer
Error in function do_connect: -5961: Connection reset by peer
/usr/bin/
Steps to reproduce:
On the server:
# apt-get install systemtap-server -y -q
# stap-gen-cert
use whatever password you want
# stap-start-server
This should have returned the pid of the running server. to test this as root on the localhost run:
stap-client -e 'probe begin { printf("Hello World!"); exit() }'
You should see "hello world" echo'd to the prompt
copy /etc/systemtap/
On the client
# apt-get install systemtap-client systemtap-server
NOTE installing systemtap-server is necessary to get stap-authorize-
to trust our server
next as root
# stap-authorize-
you should now see a series of .db files in /etc/systemtap/
you should also be able to note the presence of the stap-server via zeroconf
# stap-find-servers
nautilus.local 192.168.15.2 14628 'sysinfo=
To verify that the certificate was added to the client db successfully:
# certutil -L -d /etc/systemtap/
Take note of the DNS names and make sure they line up with the server
you're trying to authorize.
I received extensive help from the residents of #systemtap on freenode. It's
been determined that my network is in good shape along with the server side
connection. At this point the next recommendation is to upgrade from stap-1.0 to
the next available version, and is my next step.
This is an important debug setup especially when working with tiny target
images with no free space for 500MB of debug symbols, it lets you keep
the debug symbols in one place, dramatically reducing the cost of bringing
stap up on a troubled system.
To see what stap-server is doing in this instance use:
strace -o serverd.log -f stap-serverd
as root