As a more general question, are there any new ways for tracking down issues - I remember that DTrace was mentioned one time, but I don't know if that ever happened...
Also, I'm thinking that it's worth running "nwamadm interact -v" too to see what type of events are being generated (if any). I guess what I'm saying is that it's probably worth creating a Phase 1 troubleshooting page for best practice on submitting enough information for a bug to be sufficiently populated - this is especially useful when people are in different timezones, since otherwise a bug just gets bounced back asking for more information, which wastes a day or so. Darren. On 21/04/2009 23:17, bugzilla-daemon at defect.opensolaris.org wrote: > http://defect.opensolaris.org/bz/show_bug.cgi?id=8305 > > > Michael Hunter <michael.hunter at sun.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |michael.hunter at sun.com > Status|NEW |INCOMPLETE > > > > > --- Comment #1 from Michael Hunter <michael.hunter at sun.com> 2009-04-21 > 15:16:54 --- > We are going to need a lot more information to figure out what is going on. > > First of all you should always run for a while with debugging on. > > The end of http://opensolaris.org/os/project/nwam/picea/troubleshooting/ has > information about how to turn debugging on > > You might also grab a core of nwamd (see gcore(1)) or any other relevant nwam > processes. >
