dtrace discuss - May 2006 - how to recover from anon detrace hang at boot

Hi,

I have a faulty dtrace script (most probably too big bufsize).
My machine hangs at boot (amd64 5.10 Version Generic_118855-10 64-bit).

NOTICE: enabling probe 11 (dtrace:::ERROR)
WARNING: /etc/svc/volatile: File system full, swap space limit exceeded
WARNING: Sorry, no swap space to grow stack for pid 5 (autopush)
WARNING: /etc/svc/volatile: File system full, swap space limit exceeded

How to recover from that ? I have the option to reboot with a failsafe solaris
session but then how to disable the anon dtrace ?

thanks!
 
 
This message posted from opensolaris.org

Hi,

   You can try booting with the following appended to the boot 
command-line (hit ''e'' twice from the GRUB menu and add this to
the multiboot
line): "-B disable-dtrace=true", which will stop the dtrace driver 
module from being loaded (or, even easier, you can boot the failsafe option, 
which doesn''t have the dtrace anonymous probes present in the .conf
files,
then have your root filesystem mounted for you and then clean up the 
anonymous enablings in /kernel/drv/dtrace.conf (all the dof-data* 
properties)).

   --S

Quoting Frederic R. Salles, who wrote the following on Mon, 22 May 2006:
> Hi,
>
> I have a faulty dtrace script (most probably too big bufsize).
> My machine hangs at boot (amd64 5.10 Version Generic_118855-10 64-bit).
>
> NOTICE: enabling probe 11 (dtrace:::ERROR)
> WARNING: /etc/svc/volatile: File system full, swap space limit exceeded
> WARNING: Sorry, no swap space to grow stack for pid 5 (autopush)
> WARNING: /etc/svc/volatile: File system full, swap space limit exceeded
>
> How to recover from that ? I have the option to reboot with a failsafe
solaris
> session but then how to disable the anon dtrace ?
>
> thanks!
>
>
> This message posted from opensolaris.org
> _______________________________________________
> dtrace-discuss mailing list
> dtrace-discuss at opensolaris.org
>

On Mon, May 22, 2006 at 02:44:03PM -0700, Frederic R. Salles
wrote:
> Hi,
> 
> I have a faulty dtrace script (most probably too big bufsize).
> My machine hangs at boot (amd64 5.10 Version Generic_118855-10 64-bit).
> 
> NOTICE: enabling probe 11 (dtrace:::ERROR)
> WARNING: /etc/svc/volatile: File system full, swap space limit exceeded
> WARNING: Sorry, no swap space to grow stack for pid 5 (autopush)
> WARNING: /etc/svc/volatile: File system full, swap space limit exceeded
Yikes -- that''s bad.
> How to recover from that ? I have the option to reboot with a failsafe
solaris
> session but then how to disable the anon dtrace ?
The easiest is to "boot -a" and when it prompts you for the path to an
/etc/system file, enter "/dev/null"; this will prevent DTrace from
being
forceloaded, which should allow you to boot.  (Answer with the default
for every other question.)  Once it boots, you can try running "dtrace
-A"
to blow away the anonymous enabling -- but this will also force the
enabling to load as a side-effect, and if the buffer size is set to be
something absurd, this might not work.  Instead, you can manually
reconstruct the DTrace configuration file without forcing the enabling to
load by doing this:

  # cat /kernel/drv/dtrace.conf | grep -v dof-data > /tmp/dtrace.conf
  # cp /tmp/dtrace.conf /kernel/drv/

And yes, it''s probably a bug that just running "dtrace -A"
does a full
dtrace_open(), thus triggering DTrace (and any anonymous enablings) to
load...

	- Bryan

--------------------------------------------------------------------------
Bryan Cantrill, Solaris Kernel Development.       http://blogs.sun.com/bmc

Thanks for all the replies.

I booted with dtrace kernel module disabled and
cleaned up the /kernel/drv/dtrace.conf file.

Then I fixed the funny size in my dtrace script  "#pragma D option
bufsize=1500m"
 
 
This message posted from opensolaris.org