[Asterisk-Users] Asterisk hogging CPU resources

[Surfer Dude]

I will just put my few cense in here...  I would keep an eye on what you are
updating however.  For instance, in sh, or bash:

    cvs -n update -dA 2>&1 |grep -v "^cvs"

will show you, in a nice format which files would be updated were you to
update the files.  After you get that list you may want to check on each
file.

    cvs st <filename>

show you which version of the file you have locally and what the version on
the server is.  This way you can see how many changes have taken place on
the file since your last update.

    cvs log <filename>

Will give you the comments that the developer added to each version of the
file.  These are sometimes very important to know.  It could help you decide
whether or not you want to actually update at this time.

    cvs diff -rHEAD <filename>

will show you the actually difference in the file between the version you
have and the very latest version in the repository.  You can use this
command to watch the code that is being checked in.  You can see how bugs
are fixed.  And you may spot a problem with the code that was checked in.

All these commands can help you get a feel of what is actually going on.  If
you do an update and then problems occur you may be more equipped to find
out why the problems are occurring and what you can do to get around them.

This has been one of my methods copping on the tip of any codeline.

Jason




----- Original Message ----- 
From: "Steven Critchfield" <critch at basesys.com>
To: <asterisk-users at lists.digium.com>
Sent: Friday, June 20, 2003 9:45 AM
Subject: Re: [Asterisk-Users] Asterisk hogging CPU resources


> >From your asterisk source directory issue these commands
>
> make clean
> cvs update -d
> make upgrade
>
>
> The clean makes sure there is less stuff in the way of CVS to try and
> find newer copies. The -d of the cvs command will also download files
> that you may not have in your current tree. and the make upgrade is like
> make install except it doesn't overwrite your configs or sound files.
>
> On Fri, 2003-06-20 at 11:30, Derek Beaumont wrote:
> > The version of asterisk I am running is:
> > Asterisk CVS-06/05/03-09:41:32
> >
> > I am not 100% sure of how to update Asterisk.
> > Do I just download using CVS, then run
> > make clean
> > make upgrade
> > ?
> >
> >
> > -----------------------------------------------------------------------
> > This blows my main idea of not having a timing source to keep asterisk
> > from entering a busy loop.
> >
> > Are you running the most current CVS? I know there had been a bug some
> > time back that caused every asterisk thread to open handles on
> > /dev/zap/timer repeatedly and at some point my system had run out of
> > file handles to give out and performance started sucking. A CVS upgrade
> > fixed that. Oddly enough too was that it only happened on 1 of my 3
> > asterisk machines.
> >
> > On Fri, 2003-06-20 at 10:06, Derek Beaumont wrote:
> > > The interfaces I'm using are 2 X100Ps and a TDM400P
> > >
> > >
> > >
> > > --------------------------------------------------------------------
> > > What kind of interfaces are you using?
> > >
> > > I'm using zap and IAX on my main asterisk server that deals in about
> > > 300-400 calls a day without the cpu load you are seeing.
> -- 
> Steven Critchfield  <critch at basesys.com>
>
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
>
>