From: "app_rpt-users-request@ohnosec.org" <app_rpt-users-request@ohnosec.org>
To: app_rpt-users@ohnosec.org
Sent: Sunday, October 7, 2012 6:00 AM
Subject: App_rpt-users Digest, Vol 44, Issue 11

Send App_rpt-users mailing list submissions to
    app_rpt-users@ohnosec.org

To subscribe or unsubscribe via the World Wide Web, visit
    http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
or, via email, send a message with subject or body 'help' to
    app_rpt-users-request@ohnosec.org

You can reach the person managing the list at
    app_rpt-users-owner@ohnosec.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of App_rpt-users digest..."

Today's Topics:

1. Re: mpg123: no process killed - Asterisk    endedwith    exit
status 1 (Lu Vencl)
2. Error mpg123 etc. (Ian Wilson)

----------------------------------------------------------------------

Message: 1
Date: Sun, 7 Oct 2012 08:09:54 -0400
From: Lu Vencl <vencl@att.net>
To: Steve Agee <n5zua@earthlink.net>
Cc: "<app_rpt-users@ohnosec.org>" <app_rpt-users@ohnosec.org>
Subject: Re: [App_rpt-users] mpg123: no process killed - Asterisk
    endedwith    exit status 1
Message-ID: <EC2A6F5E-8FEE-472B-9775-4B0B1569B7C4@att.net>
Content-Type: text/plain; charset="cp932"

I don't have Jim's email in this phone and I am traveling this weekend. Can someone fwd this concern to him? Unless of course he is monitoring this list then that would not be necessary.
Thanks
Lu
KA4EPS

Sent from my iPhone, Lu Vencl

On Oct 6, 2012, at 1:44 AM, "Steve Agee" <n5zua@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@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@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Lu Vencl
> Sent: Friday, October 05, 2012 9:42 PM
> To: app_rpt-users@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@ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ohnosec.org/pipermail/app_rpt-users/attachments/20121007/c0f03551/attachment-0001.html>

------------------------------

Message: 2
Date: Sun, 7 Oct 2012 13:20:19 +0100 (BST)
From: Ian Wilson <jedscoot@yahoo.com>
To: "app_rpt-users@ohnosec.org" <app_rpt-users@ohnosec.org>
Subject: [App_rpt-users] Error mpg123 etc.
Message-ID:
    <1349612419.67010.YahooMailNeo@web29401.mail.ird.yahoo.com>
Content-Type: text/plain; charset="utf-8"

This is my experience of the error and how I cured it.
I found that after making a change and downloading the server configuration I would get the error.
Over-writing my [ rpt.conf ] with one from a known working configuration cured it.

Changes I made to the server configuration was to add/remove Echolink connectivity.

I also found that by including another node the error appeared.
This was due to the downloaded [rpt.conf] file not having the second node stanza inserted after the [ ;***Status Reporting *** ] portion of [ rpt.conf ]

Manually setting [ rpt.conf ] with the two node stanzas first then followed by [morse] [schedule] [functions] etc cured it.

I'm new to this so if this is already known apologies for repeating it..

Ian..
28818
28934
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ohnosec.org/pipermail/app_rpt-users/attachments/20121007/3456e139/attachment-0001.html>

------------------------------

_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

End of App_rpt-users Digest, Vol 44, Issue 11
*********************************************