<div dir="ltr"><div class="gmail_quote">On Wed, Jul 6, 2011 at 3:21 AM, Tzafrir Cohen <span dir="ltr"><<a href="mailto:tzafrir.cohen@xorcom.com">tzafrir.cohen@xorcom.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On Tue, Jul 05, 2011 at 08:30:52PM -0400, A E [Gmail] wrote:<br>
> hello people,<br>
><br>
> I am running v1.8.4.2 on debian squeeze on a sparc platform...and for some<br>
> reason I have noticed that only after a few test calls, the asterisk process<br>
> is running between 95% - 99.9% CPU when there's absolutely nothing on the<br>
> system. This is a clean Asterisk system in an internal network with nothing<br>
> else on it with no calls on it but it's still sitting with 96% CPU.<br>
><br>
> I'm not a developer so not that ept with using debug tools etc to figure out<br>
> why it's doing that. Could anyone please tell me how I can figure out why<br>
> it's doing this and/or help debug this. Makes no sense for it to be using<br>
> CPU with nothing happening on the system<br>
<br>
</div></div>The first thing I'd do is run 'top', press shift H, and see what is/are<br>
the offending thread(s).<br>
<br>
Is it a single thread? Two? More?<br>
<br>
Is it all "user" time? Much of it is "system" time?<br>
<br>
If you strace the PID of the top thread (strace -p PID), what do you<br>
see?<br>
<font color="#888888"><br></font><div><div class="h5"><br></div></div></blockquote><div><font class="Apple-style-span" color="#000099">Hi Tzafrir,</font></div><div><font class="Apple-style-span" color="#000099"><br></font></div>
<div><font class="Apple-style-span" color="#000099">thanks for the comments and suggestions. So I'd done all of that and what I'd found was </font></div><div><font class="Apple-style-span" color="#000099"><br></font></div>
<div><font class="Apple-style-span" color="#000099">- After I'd done Shift-h, There was only one / single thread that was taking all of the CPU</font></div><div><font class="Apple-style-span" color="#000099">- 33% was Sser and 66% was System times</font></div>
<div><font class="Apple-style-span" color="#000099">- when I'd run an strace on the PID of the offending thread it just rolled some message past my screen which I couldn't capture and can't remember what it said :(</font></div>
<div><font class="Apple-style-span" color="#000099"><br></font></div><div><font class="Apple-style-span" color="#000099">Anyway I've killed that process, updated the packages the system, upgraded to 1.8.4.4 and will give it another shot and see what happens. Would've helped if I'd kept the system as it was so people could help me figure out what was going on, but the fact that it stopped responding to commands which were trying to kill the hung channels, reloading configs, or even trying to stop the system wouldn't work is bizarre. I hope the developers pay attention to that.</font></div>
<div><br></div></div></div>