On Fri, Nov 16, 2007 at 06:29:45AM -0800, Paul van den Bogaard wrote: > Result: had to reboot my T2000 by using the system console and powering it > off and on again after waiting for more than 12 hours to see if it came back.
That's quite surprising -- and distressing. Did you get a dump? Do you have any more data from which we might be able to debug the problem? > Sure too many probes enabled. However this result is lets say "surprising". > Indeed very dangerous since database can be used in production environments. > In my view this is not good. That doesn't sound like too many probes enabled at all. We've enabled millions of probes without incident. > dtrace -x dynvarsize=64m -x cleanrate=203 -qs lw.d >LW/lw.out > dtrace: failed to compile script lw.d: line 374: failed to grab process 14510 This may be that you're hitting the file descriptor limit. Try taking a look with truss on the dtrace(1M) process. > Questions: how do I make this workable. Meaning speedier in startup. > Without reducing my attention to just one or two processes. We'd need to figure out where the system is spending its time -- DTrace is a great place to start. > Question: why is my system so unresponsive (I waited more that 12 hours to > see if it came back) forcing me to power off/on to get it alive and kicking > again? Let's work offline to try to sort this out. > And please note that we are planning to add many, many more probes in PG > source. However if the above is the result I fear great fears ... You're not enabling that many probes; I don't think that's the cause of either problem. Adam -- Adam Leventhal, FishWorks http://blogs.sun.com/ahl _______________________________________________ dtrace-discuss mailing list [email protected]
