I had meant to post a follow up to this, but just... didn't. Sorry.
Anyway, I had made a silly change to my safe_asterisk script that caused it to
start asterisk in the background, but also with a console. This caused
asterisk to try to write to a non-existent console tty.
Dumb mistake on my part.
Hope this helps someone else.
Mike.
On Thursday, April 06, 2017 10:28:03 AM you wrote:> On Thu, Apr 6, 2017 at 10:20 AM, Mike Diehl <mdiehlenator at
gmail.com> wrote:
> > I found it!
> >
> > I had customized the safe_asterisk script and managed to slip in a -c
on
the asterisk command line.> >
> > So, when I ran strace on the running process, I saw a bunch of
messages
indicating an invalid IOCTL on file handle 1, which is always STDOUT. A
background process shouldn't be writing to STDOUT, so I knew I had dorked
something up.> >
> > I appreciate your time.
> >
>
> Thanks so much for letting me know. Would you mind posting this
> resolution publicly so that anybody following it can learn from what
> happened?
>
> Best wishes,
> Matthew Fredrickson
>
> > Mike.
> >
> >
> >
> > On Tuesday, April 04, 2017 09:18:26 AM you wrote:
> >> On Mon, Apr 3, 2017 at 4:45 PM, Mike Diehl <mdiehlenator at
gmail.com>
wrote:> >> > Those are all rational questions, so here we go:
> >> >
> >> > We upgraded from 11.x, though the system was a backup server,
so it was
never> >> > actually used.
> >> >
> >> > The system is a 2.4Gh quad-core Xenon with 4G of RAM, so it
should have
plenty> >> > of power for what I'm asking it to do. The system is
configured via RT
using> >> > a local Mysql database.
> >> >
> >> > We only use the native SIP channel driver at this time.
> >> >
> >> > I honestly don't see any reason for this server to eat
100% of it's
cpu, and> >> > am hesitant to roll it out to production until I understand
why it is.
> >>
> >> I don't either. Is there any Asterisk logging that indicates
> >> something that might be going on? If you can't see anything,
try
> >> increasing the core debug level and core verbose level (core set
> >> verbose 10, core set debug 10) at the Asterisk CLI and see if you
get
> >> anything more out of logging to see what's going on.
> >>
> >>
> >
> > --
> > Mike Diehl
> > Diehlnet Communications, LLC.
> > Sales: (800) 254-6105
> > Support: (505) 903-5700
> > Fax: (505) 903-5701
> >
>
>
>
>
--
Mike Diehl