This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Systemtap does not clean up properly
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: Cor-Paul Bezemer <c dot bezemer at tudelft dot nl>
- Cc: systemtap at sourceware dot org
- Date: Thu, 19 Sep 2013 11:33:00 -0400
- Subject: Re: Systemtap does not clean up properly
- Authentication-results: sourceware.org; auth=none
- References: <1379594422059-244731 dot post at n7 dot nabble dot com> <190889500 dot 18089486 dot 1379597221958 dot JavaMail dot root at redhat dot com> <523B03B6 dot 5040704 at tudelft dot nl>
c.bezemer wrote:
> Thanks, but we are actually already doing this.
I guess the question is how are you killing the userspace stap
processes, and how are you trying to manually remove the stap_XXXX
modules? If you just SIGINT the stap* processes, they should clean up
nicely after themselves. If you SIGKILL, then you take responsibility
for removing the kernel modules, which should be just an rmmod.
> Here is a stack trace in case it helps:
> http://paste.debian.net/42978/
That trace appears to show some near-OOM conditions from stap scripts
that are trying to start up, as opposed to anything related to
shutdown. (The actual pattern indicates a fragmentation problem that
dsmith's commit 3f873e53e should fix.)
- FChE