This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: how to discover description of error which terminated run
- From: Mark Wielaard <mark at klomp dot org>
- To: John Lumby <johnlumby at hotmail dot com>
- Cc: systemtap at sourceware dot org
- Date: Wed, 5 Dec 2012 22:55:13 +0100
- Subject: Re: how to discover description of error which terminated run
- References: <COL116-W57F5039544BDB96F7DE64A3460@phx.gbl>
On Wed, Dec 05, 2012 at 12:02:32PM -0500, John Lumby wrote:
>
> Recently my system tap runs have been terminating abruptly during a run,
> (long after the start of the subject workload so not initialisation-related,
> ?but also long before the workload itself ends)
> and printing something like this at the end:
>
> WARNING: Number of errors: 1, skipped probes: 0
> WARNING: /usr/local/bin/staprun exited with status: 1
> Pass 5: run completed in 20usr/30sys/55140real ms.
> Pass 5: run failed.? Try again with another '--vp 00001' option.
> Keeping temporary directory "/tmp/stapOlPtXe"
>
> Prior to this it has successfully and correctly printed all the output from all probes
> hit till then (they are all user probes by the way? -? I am not using the kprobe)
>
> It has the look of hitting some resource limit but I can't be sure.
> How can I get stap to tell me the description of the error which occurred?
> (and also of course make it continue )
It is strange there is no actualy ERROR reported.
Maybe look at dmesg or /var/log/messages output to see if there is
a hint there?
If there was an actual error message, then the following page has
a couple of hints how to get past some resource limit:
http://sourceware.org/systemtap/wiki/TipExhaustedResourceErrors
Cheers,
Mark