Rule #1, ALWAYS make a backup copy of any config file you intend to modify.  No matter how unimportant, small or mundane you think the change is, make a copy in a safe directory before you change anything, that way you can always fall back to it if you have any doubts.


On Apr 29, 2018, at 7:45 PM, John Rudolph- N2YP <John@n2yp.com> wrote:

The issue has been found and fixed. I ended up with a duplicate stanza heading [46101] which broke everything apparently. Removed that and all is back to normal. I'm really surprised that that item broke so much.
John Rudolph
Amateur Radio Op N2YP
Unadilla,NY


On April 29, 2018 12:00:01 PM EDT, app_rpt-users-request@lists.allstarlink.org wrote:
Send App_rpt-users mailing list submissions to
	app_rpt-users@lists.allstarlink.org

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

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

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

This site is dedicated to the memory of Jim Dixon WB6NIL


Today's Topics:

   1. Errors (John Rudolph- N2YP)
   2. Re: Errors (Steve Zingman)
   3. Re: Errors (Tim Sawyer)
Message: 1
Date: Sat, 28 Apr 2018 22:52:20 -0400
From: John Rudolph- N2YP <John@n2yp.com>
To: app_rpt-users@lists.allstarlink.org
Subject: [App_rpt-users] Errors
Message-ID: <F405D071-964E-4C75-B085-1FE1BCAF4905@n2yp.com>
Content-Type: text/plain; charset="utf-8"

I have a multi node x86 ASL Asterisk 1.01 system up and running. Today I went to add a puesdo/dahdi hub and just made a additions to rpt.conf and iax.conf, and went and rebooted Asterisk and or the whole system and even though I love undone the "new" node the system is broke. My URI'S no longer get a heartbeat but show via lsusb, I can't access Asterisk CLI- get "Unable to connect to remote asterisk (does /var/run/asterisk.ctl exist?)" Yet this file does exist, Can't access radio-tune-menu - get "Error parsing device parameters", nodes no longer register with ASL, allmon2 can't access Asterisk manager, and my EchoLink node shows active but you can't access it. After multiple reboots I did try apt get update and upgrade with no success.  Dahdi and crc_ccitt show running and nothing shows in the asterisk log other than it starting the nodes.

What I don't understand is that I did nothing at all other than add a stanza for another node and uncomment that node number in iax.conf and restart. If someone could walk me through trouble shooting this I would appreciate it so I can learn what went wrong.
John Rudolph
Amateur Radio Op N2YP
Unadilla,NY
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.allstarlink.org/pipermail/app_rpt-users/attachments/20180428/6ab69a2f/attachment-0001.html>
Message: 2
Date: Sat, 28 Apr 2018 22:54:34 -0400
From: Steve Zingman <szingman@msgstor.com>
To: app_rpt-users@lists.allstarlink.org
Subject: Re: [App_rpt-users] Errors
Message-ID: <91ffe40e-471a-101c-a0c2-4f22d6c9f9b8@msgstor.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

Step 1:
Check the log for errors:
it is in /var/log/asterisk the filename is messages

Steve n4IRS

On 04/28/2018 10:52 PM, John Rudolph- N2YP wrote:
 I have a multi node x86 ASL Asterisk 1.01 system up and running. Today 
 I went to add a puesdo/dahdi hub and just made a additions to rpt.conf 
 and iax.conf, and went and rebooted Asterisk and or the whole system 
 and even though I love undone the "new" node the system is broke. My 
 URI'S no longer get a heartbeat but show via lsusb, I can't access 
 Asterisk CLI- get "Unable to connect to remote asterisk (does 
 /var/run/asterisk.ctl exist?)" Yet this file does exist, Can't access 
 radio-tune-menu - get "Error parsing device parameters", nodes no 
 longer register with ASL, allmon2 can't access Asterisk manager, and 
 my EchoLink node shows active but you can't access it. After multiple 
 reboots I did try apt get update and upgrade with no success. Dahdi 
 and crc_ccitt show running and nothing shows in the asterisk log other 
 than it starting the nodes.

 What I don't understand is that I did nothing at all other than add a 
 stanza for another node and uncomment that node number in iax.conf and 
 restart. If someone could walk me through trouble shooting this I 
 would appreciate it so I can learn what went wrong.
 John Rudolph
 Amateur Radio Op N2YP
 Unadilla,NY
 App_rpt-users mailing list
 App_rpt-users@lists.allstarlink.org
 http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

 To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
 You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.allstarlink.org/pipermail/app_rpt-users/attachments/20180428/fbc0d89c/attachment-0001.html>
Message: 3
Date: Sat, 28 Apr 2018 20:58:40 -0700
From: Tim Sawyer <tisawyer@gmail.com>
To: Users of Asterisk app_rpt <app_rpt-users@lists.allstarlink.org>
Subject: Re: [App_rpt-users] Errors
Message-ID:
	<CAG3ht9trmThaNMPUrP6O3v-h-ZQZVCSs2=Kd2UiYZM_i9Tu6ZQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

You probably fat fingered something. It happens to all of us. Start
Asterisk in the non-deamon mode by doing

asterisk -fnvvv

at the linux prompt and watch for errors. Press control-c to exit. Fix
error. Repeat until it starts clean.

On Sat, Apr 28, 2018 at 7:52 PM, John Rudolph- N2YP <John@n2yp.com> wrote:

 I have a multi node x86 ASL Asterisk 1.01 system up and running. Today I
 went to add a puesdo/dahdi hub and just made a additions to rpt.conf and
 iax.conf, and went and rebooted Asterisk and or the whole system and even
 though I love undone the "new" node the system is broke. My URI'S no longer
 get a heartbeat but show via lsusb, I can't access Asterisk CLI- get
 "Unable to connect to remote asterisk (does /var/run/asterisk.ctl exist?)"
 Yet this file does exist, Can't access radio-tune-menu - get "Error parsing
 device parameters", nodes no longer register with ASL, allmon2 can't access
 Asterisk manager, and my EchoLink node shows active but you can't access
 it. After multiple reboots I did try apt get update and upgrade with no
 success. Dahdi and crc_ccitt show running and nothing shows in the asterisk
 log other than it starting the nodes.

 What I don't understand is that I did nothing at all other than add a
 stanza for another node and uncomment that node number in iax.conf and
 restart. If someone could walk me through trouble shooting this I would
 appreciate it so I can learn what went wrong.
 John Rudolph
 Amateur Radio Op N2YP
 Unadilla,NY
 App_rpt-users mailing list
 App_rpt-users@lists.allstarlink.org
 http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

 To unsubscribe from this list please visit http://lists.allstarlink.org/
 cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of
 the page. Enter your email address and press the "Unsubscribe or edit
 options button"
 You do not need a password to unsubscribe, you can do it via email
 confirmation. If you have trouble unsubscribing, please send a message to
 the list detailing the problem.



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

To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.