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

Don Hackler donh at sigma.net
Sat Oct 6 12:52:35 EDT 2012


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 at sigma.net] 
> Sent: Saturday, October 06, 2012 3:00 AM
> To: 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 <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: Scott Weis
> To: 'Lu Vencl' ; 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: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Lu Vencl
> Sent: Friday, October 05, 2012 9:42 PM
> To: 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
>  
> Automatically restarting Asterisk.
> mpg123: no process killed
> Asterisk ended with exit status 1
> Asterisk died with code 1.
> Automatically restarting Asterisk.
> mpg123: no process killed
> Asterisk ended with exit status 1
> Asterisk died with code 1.
> Automatically restarting Asterisk.
> mpg123: no process killed
> Asterisk ended with exit status 1
> Asterisk died with code 1.
> Automatically restarting Asterisk.
> mpg123: no process killed
> Asterisk ended with exit status 1
> Asterisk died with code 1.
> Automatically restarting Asterisk.
> mpg123: no process killed
> Asterisk ended with exit status 1
> Asterisk died with code 1.
> Automatically restarting Asterisk.
> mpg123: no process killed
> Asterisk ended with exit status 1
> Asterisk died with code 1.
> Automatically restarting Asterisk.
> mpg123: no process killed
> Asterisk ended with exit status 1
> Asterisk died with code 1.
> Automatically restarting Asterisk.
> mpg123: no process killed
> Asterisk ended with exit status 1
> Asterisk died with code 1.
> Automatically restarting Asterisk.
> mpg123: no process killed
> Asterisk ended with exit status 1
> Asterisk died with code 1.
> Automatically restarting Asterisk.
> mpg123: no process killed
> Asterisk ended with exit status 1
> Asterisk died with code 1.
> Automatically restarting Asterisk.
> mpg123: no process killed
> Asterisk ended with exit status 1
> Asterisk died with code 1.
> Automatically restarting Asterisk.
> mpg123: no process killed
> Asterisk ended with exit status 1
> Asterisk died with code 1.
> Automatically restarting Asterisk.
> mpg123: no process killed
> Asterisk ended with exit status 1
> Asterisk died with code 1.
> Automatically restarting Asterisk.
>  
>  
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.allstarlink.org/pipermail/app_rpt-users/attachments/20121006/57f5c618/attachment.html>


More information about the App_rpt-users mailing list