This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/17393] java.exp: ERROR: Cannot attach to module control channel
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Tue, 08 Mar 2016 15:52:12 +0000
- Subject: [Bug runtime/17393] java.exp: ERROR: Cannot attach to module control channel
- Auto-submitted: auto-generated
- References: <bug-17393-6586 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17393
David Smith <dsmith at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dsmith at redhat dot com
--- Comment #3 from David Smith <dsmith at redhat dot com> ---
(In reply to Martin Cermak from comment #2)
> How to reproduce manually:
>
> Either:
> cd /usr/share/systemtap/testsuite
> make RUNTESTFLAGS='java.exp' installcheck
>
> Or:
> cd /usr/share/systemtap/testsuite
> javac -d ./ systemtap.apps/singleparam.java
> stap systemtap.apps/singleparam.stp -c "java singleparam >/dev/null 2>&1"
On f23 I'm still seeing this. It happens pretty regularly when running the test
case, but not as often when run by hand.
Here's the interesting part of the output when "-vvv" is added to the command
line. First, here's the output of a successful run:
====
stapio:stp_main_loop:782 got STP_EXIT
stapio:cleanup_and_exit:474 detach=0
stapio:close_relayfs:440 closing
stapio:close_relayfs:462 done
stapio:cleanup_and_exit:491 closing control channel
stapio:close_ctl_channel:112 Closed ctl fd 4
stapio:cleanup_and_exit:499
Renamed module to: stap_d6d5dc4cdf58d2cfe354504512002cb9_19483
stapio:cleanup_and_exit:506 removing
stap_d6d5dc4cdf58d2cfe354504512002cb9_19483
staprun:parse_modpath:458
modpath="/lib/modules/4.4.3-300.fc23.x86_64/systemtap/stap_d6d5dc4cdf58d2cfe354504512002cb9_19483.ko"
staprun:main:431
modpath="/lib/modules/4.4.3-300.fc23.x86_64/systemtap/stap_d6d5dc4cdf58d2cfe354504512002cb9_19483.ko",
modname="stap_d6d5dc4cdf58d2cfe354504512002cb9_19483"
staprun:init_staprun:337 init_staprun
staprun:remove_module:246 stap_d6d5dc4cdf58d2cfe354504512002cb9_19483
staprun:init_ctl_channel:72 Opened
/sys/kernel/debug/systemtap/stap_d6d5dc4cdf58d2cfe354504512002cb9_19483/.cmd
(4)
staprun:close_ctl_channel:112 Closed ctl fd 4
staprun:remove_module:271 removing module
stap_d6d5dc4cdf58d2cfe354504512002cb9_19483
staprun:remove_module:283 Module stap_d6d5dc4cdf58d2cfe354504512002cb9_19483
removed.
Spawn waitpid result (0x0): 0
====
Here's the output of a failure run:
====
stapio:stp_main_loop:782 got STP_EXIT
stapio:cleanup_and_exit:474 detach=0
stapio:close_relayfs:440 closing
stapio:close_relayfs:462 done
stapio:cleanup_and_exit:491 closing control channel
stapio:close_ctl_channel:112 Closed ctl fd 4
stapio:cleanup_and_exit:499
Renamed module to: stap_d6d5dc4cdf58d2cfe354504512002cb9_18888
stapio:cleanup_and_exit:506 removing
stap_d6d5dc4cdf58d2cfe354504512002cb9_18888
staprun:parse_modpath:458
modpath="/lib/modules/4.4.3-300.fc23.x86_64/systemtap/stap_d6d5dc4cdf58d2cfe354504512002cb9_18888.ko"
staprun:main:431
modpath="/lib/modules/4.4.3-300.fc23.x86_64/systemtap/stap_d6d5dc4cdf58d2cfe354504512002cb9_18888.ko",
modname="stap_d6d5dc4cdf58d2cfe354504512002cb9_18888"
staprun:init_staprun:337 init_staprun
staprun:remove_module:246 stap_d6d5dc4cdf58d2cfe354504512002cb9_18888
staprun:init_ctl_channel:72 Opened
/sys/kernel/debug/systemtap/stap_d6d5dc4cdf58d2cfe354504512002cb9_18888/.cmd
(-1)
ERROR: Cannot attach to module stap_d6d5dc4cdf58d2cfe354504512002cb9_18888
control channel; not running?
ERROR: 'stap_d6d5dc4cdf58d2cfe354504512002cb9_18888' is not a zombie systemtap
module.
Spawn waitpid result (0x100): 1
====
In the failure case, for some odd reason we get back into init_staprun() at
exit.
--
You are receiving this mail because:
You are the assignee for the bug.