[App_rpt-users] mpg123: no process killed - Asterisk endedwith exit status 1

Mon Oct 8 02:28:05 UTC 2012

All,

Thanks for the tips. I have been out of town so I was unable to follow
along, but Jim was kind enough to take a look at my new node I just
installed from the ISO and he had to re-compile Zaptel.

So to others out there that are having this issue, you might take a look at
this.

Why this is required on a new install I still do not understand, I have
never had to do this before, but for those like me that have no idea how to
do this, Jim suggested to "re-installed from SVN sources or something like
that" should take care of it.  I have been able to do SVN updates via
/etc/svnupdate/svnupdate.sh on my other nodes, but I don't see this on the
new install, so I think I have to copy that over first, unless someone can
please advise the correct or alternate procedure.

Or you can re-compile Zaptel. In looking at the history of what he did,
please look below as this should offer a clue. Or course some of the
commands may not be needed, but again just trying to help newbies (like
myself)  along.

Thanks again Jim for your help today.

    2  chkconfig zaptel off

    3  chkconfig asterisk off

    4  asterisk -r

    5  sync

    6  reboot

    7  service zaptel start

    8  asterisk -vvvvcn

    9  service zaptel stop

   10  cd /usr/src/astsrc/zaptel/

   11  make install

   12  make clean

   13  make install

   14  service zaptel start

   15  asterisk -vvvvcn

   16  chkconfig zaptel on

   17  chkconfig zaptel off

   18  sync

   19  reboot

   20  asterisk -r

   21  asterisk -vvvcn

   22  ntsysv

   23  history

   24  sync

   25  reboot

From: Don Hackler [mailto:donh at sigma.net] 
Sent: Saturday, October 06, 2012 12:53 PM
To: Lu Vencl
Cc: app_rpt-users at ohnosec.org; 'Scott Weis'; 'Steve Agee'
Subject: Re: [App_rpt-users] mpg123: no process killed - Asterisk endedwith
exit status 1

I had the same thing. about 5 minutes later asterisk would finally stay up,
but there would be other problems when I would try to 

make connections to radios work.  One way audio, among other things.  I
spent a few days trying to troubleshoot it.

When I finally did a fresh download and re-installed from scratch,
everything just came up and worked as expected.

The other problem I had with that bad disk was the dictionary package was
missing, so when you tried to set the

password during the install, the root password wasn't getting set, so I
would have to boot it in single user mode and force a password into it. 

On Oct 6, 2012, at 4:41 AM, "Lu Vencl" <vencl at att.net> wrote:

Very interesting.. I will try that and report back..

The odd thing is that Asterisk will eventually start, but it takes about 5
minutes or so to settle down.

KA4EPS

From: Don Hackler [mailto:donh@ <http://sigma.net> sigma.net] 
Sent: Saturday, October 06, 2012 3:00 AM
To:  <mailto:app_rpt-users at ohnosec.org> app_rpt-users at ohnosec.org
Cc: Lu Vencl; Scott Weis; Steve Agee
Subject: Re: [App_rpt-users] mpg123: no process killed - Asterisk endedwith
exit status 1

When I had this problem, I tried to install a few times and kept coming up
with this error.  I had to download a fresh copy of the install CD to

correct the problem.  There was a subtle problem in the downloaded bits on
the first CD.

On Oct 5, 2012, at 10:44 PM, Steve Agee < <mailto:n5zua at earthlink.net>
n5zua at earthlink.net> wrote:

I'm having this issue as well on a fresh install. The machine is 64 bit:

[Oct  5 22:42:47] ERROR[23279] asterisk.c: Asterisk has detected a problem
with your Zaptel configuration and will shutdown for your protection.  You
have options:
        1. You only have to compile Zaptel support into Asterisk if you need
it.  One option is to recompile without Zaptel support.
        2. You only have to load Zaptel drivers if you want to take
advantage of Zaptel services.  One option is to unload zaptel modules if you
don't need them.
        3. If you need Zaptel services, you must correctly configure Zaptel.
mpg123: no process killed
Asterisk ended with exit status 1
Asterisk died with code 1.
Automatically restarting Asterisk.

N5ZUA

----- Original Message -----

From:  <mailto:kb2ear at kb2ear.net> Scott Weis

To:  <mailto:vencl at att.net> 'Lu Vencl' ;  <mailto:app_rpt-users at ohnosec.org>
app_rpt-users at ohnosec.org

Sent: Friday, October 05, 2012 9:23 PM

Subject: Re: [App_rpt-users] mpg123: no process killed - Asterisk endedwith
exit status 1

Your system most likely updated it's kernel.. So you need to rebuild/install
zaptel.

From:  <mailto:app_rpt-users-bounces at ohnosec.org>
app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-
<mailto:users-bounces at ohnosec.org> users-bounces at ohnosec.org] On Behalf Of
Lu Vencl
Sent: Friday, October 05, 2012 9:42 PM
To:  <mailto:app_rpt-users at ohnosec.org> app_rpt-users at ohnosec.org
Subject: [App_rpt-users] mpg123: no process killed - Asterisk ended with
exit status 1

Anyone know why a new node I just built goes through several of these before
settling down after a reboot?

I have hear this complaint from someone else before, but he can't remember
what he did to fix his node.

Thanks

Lu

KA4EPS