Fault tolerance is a wonderful thing.
On Apr 29, 2018, at 11:14 PM, Benjamin Naber <Benjamin@Project23D.com> wrote:
John, et al:
Modules for a lack of better terms, on just about any program, look for specific things in other modules.
If something is not correct, and causes issues, other modules will not work, and some, very strange cryptic errors will be thrown when debugging...... *IF* there is bug.
My vague-ness is intentional, as bugs are vast and varied... if the issue is a bug, or user error.
To put it another way, let assume your car engine begins to misbehave. There are MANY systems that must work in harmony for things to run smoothly.
Something simple such as a failing fuel pressure damper will cause cylinder misfires, rough idle, fuel smell, poor fuel economy. From the onset of symptoms, there are many guesses as to what could cause the evident issues... All those signs from ONE failing part.
Operational robustness is extremely hard to obtain.
~Benjamin, KB9LFZ
On Sun, 2018-04-29 at 19:45 -0400, John Rudolph- N2YP wrote: ..... 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.allsta rlink.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-u sers 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