<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Eric,<br>
Good catch on the -rvvv. That's what I get for answering a e-mail at
04:30 AM.<br>
<br>
Steve<br>
<br>
<div class="moz-cite-prefix">On 7/12/2018 9:48 AM, Eric Osterberg
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAJLaYFU7Nhj3SR_DZrwi6Br20z8BJmthoRtXd0YK3r-xwyc71g@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div dir="ltr">
<div>
<div>
<div>
<div>That's a lot of text I'm not going to fully read. I
sense some frustration. <i><u>(Under statement/insert
sarcasm)<br>
<br>
</u></i></div>
First idea I have for you... Your "<span
style="font-family:monospace,monospace">asterisk -rvvv</span>"
command is trying to connect with an already running
instance of the asterisk service. That error message about
"...var/run/asterisk.ctl..." does not exist... simply
means that the service isn't online. You might try this
command... "<span style="font-family:monospace,monospace">asterisk
-cgvvv</span>". I suspect you'll learn more about what's
failing from that output.<br>
<br>
</div>
Here's a reference to the command line options... <a
href="https://www.voip-info.org/asterisk-options"
moz-do-not-send="true">https://www.voip-info.org/asterisk-options</a><br>
</div>
<div>PS: I know nothing about this build... Just some basic
asterisk administration... Hope it helps you and you in turn
pay it forward and help others.<br>
</div>
<div><br>
</div>
73 - Good luck...<br>
</div>
NØNKI - Eric in Minneapolis Minnesota<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Jul 11, 2018 at 10:47 PM, Jim
Aspinwall No1PC <span dir="ltr"><<a
href="mailto:no1pc@yahoo.com" target="_blank"
moz-do-not-send="true">no1pc@yahoo.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div style="font-family:Helvetica
Neue,Helvetica,Arial,sans-serif;font-size:16px">
<div style="font-family:Helvetica
Neue,Helvetica,Arial,sans-serif;font-size:16px">
<div>So, I 'blew' the latest Stretch build into a new
USB flash device... booted and tried to configure an
existing node onto it on hardware that is known to
work under prior.</div>
<div><br>
</div>
<div>1. ASL-MENU did NOT over-write the rpt.conf nor
iax.conf files with given parameters - run as
'repeater' sudo root or enabled root user. FAIL.
How is this fail 'possible' ?<br>
<br>
2. Asterisk -rvvvvv... consistently revealed that
the attached known interface did not exist and
failed out with "...var/run/asterisk.ctl..." does
not exist... when it actually does - what condition
manifests this? <br>
<br>
NO low voltage errors on the console... all this on
a known Pi3 AND RA-40 interface configuration under
prior Jessie install...<br>
<br>
To this... after decades of WinTel system support
and a variety of x-Nix support work... <br>
<br>
... please understand I do NOT *want* to hint at,
support, or indicate that 'Crompton' may be on to
something because his builds aren't all that stable
and documentation and support are no better an often
wrong, accusational... but have not exhibited this
level of 'stupid' non-function.<br>
<br>
I am also someone at the brunt of "it doesn't work"
as an esclation point in massive enterprises, and
can at least identify and analyze log files that may
contain some hints... "give me (path)xxx log
file..." and at least I provide or know full paths,
not casual non-specific references. I would hope,
expect the contributing community to be robust in
definitive, helpful logging and not simply dismiss
users to unqualified rhetoric/fault.<br>
<br>
That said...the latest Jessie build is a failure.
The latest Stretch build is a failure. "change my
mind"<br>
<br>
I'm back to tweaking the prior Jessie build to work
as 'advertised' sans asl-menu and don't dare chance
an upgrade/update process to the latest...<br>
<br>
I merely anticipate the coders know various failure
conditions, can detect and log them... but that is
an anticipation not rendered in actual logical
recorded fact.|<br>
<br>
OK - get it - code contributors are volunteers.
Volunteers that are supposedly intimate and
knowledgeable with the code, functions, conditions,
etc. Bad power (not evident), bad storage/boot
device (not evident), yadda... so, what?<br>
<br>
If you cannot document the 'proper' necessary
requirements for hardware, process, etc. you cannot
hold us users accountable or nor unknown
circumstances to blame for failures. This is
logical, programmatic... SOMETHING can detect (or
not) attached hardware and communications
functions... but yet not tell us what part(s)
failed?<br>
<br>
Certainly when a convenient configuration
menu/utility cannot/will not write-out changed
parameters - one can determine a file system or
rights issue... and reveal same... not leaving the
user with the deception the system is good to go
when it is sitting there at useless defaults.<br>
<br>
We really do NOT want this project left to Crompton
for the popular vote, nor the x-Nix elitists... it's
much too good for either of that.<br>
<br>
I among others are willing to dig deep and provide
any log files, etc. that are effective to supportive
solutions. If logging content is ambiguous, not
adequate to specific known logical issues, improve
logging. If scripts do not work... let's debug... <br>
<br>
The leave behind is that if you were lucky enough to
capture a prior Jesse build... sans asl-menu...
stash it away and work around manual configs, leave
it not user-friendly.<br>
<br>
If there are specific hardware, storage device
requirements, document and better test for them.
Obviously a current bootable latest Jessie build is
NOT effective to new or existing node success. Why?<br>
<br>
Leave all of this to unstable, undocumented Crompton
builds, or do equal or better...<br>
<br>
How can I/we help?</div>
<div><br>
<br>
-------------------</div>
</div>
<div
id="m_-2779603841141272794ydpbb128784yahoo_quoted_2070487382"
class="m_-2779603841141272794ydpbb128784yahoo_quoted">
<div style="font-family:'Helvetica
Neue',Helvetica,Arial,sans-serif;font-size:13px;color:#26282a">
<div>
<div dir="ltr">Today's Topics:<br>
</div>
<div dir="ltr"><br>
</div>
<div dir="ltr"> 1. Re: URI-X Issues With New
Raspbian build (Steve Zingman)<br>
</div>
<div dir="ltr"> 2. Replay of June 26th Net at 8pm
EDT (tonight) on 29999 (Mike)<br>
</div>
<div dir="ltr"><br>
</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">------------------------------<wbr>------------------------------<wbr>----------<br>
</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">Message: 1<br>
</div>
<div dir="ltr">Date: Tue, 10 Jul 2018 15:31:47
-0400<br>
</div>
<div dir="ltr">From: Steve Zingman <<a
rel="nofollow" moz-do-not-send="true">szingman@msgstor.com</a>><br>
</div>
<div dir="ltr">To: Users of Asterisk app_rpt <<a
rel="nofollow" moz-do-not-send="true">app_rpt-users@lists.<wbr>allstarlink.org</a>><br>
</div>
<div dir="ltr">Subject: Re: [App_rpt-users] URI-X
Issues With New Raspbian build<br>
</div>
<div dir="ltr">Message-ID: <<a rel="nofollow"
moz-do-not-send="true">b9e5a338-8b97-9d40-5a73-<wbr>7a1757b76366@msgstor.com</a>><br>
</div>
<div dir="ltr">Content-Type: text/plain;
charset="utf-8"; Format="flowed"<br>
</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">If I had to guess, I would say a
bad SD card burn. or a bad card.<br>
</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">Steve N4IRS<br>
</div>
<div dir="ltr"><br>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
______________________________<wbr>_________________<br>
App_rpt-users mailing list<br>
App_rpt-users@lists.<wbr><a href="http://allstarlink.org"
moz-do-not-send="true">allstarlink.org</a><br>
<a href="http://lists.allstarlink.org/"
moz-do-not-send="true">http://lists.allstarlink.org/</a><wbr>cgi-bin/mailman/listinfo/app_<wbr>rpt-users<br>
<br>
To unsubscribe from this list please visit <a
href="http://lists.allstarlink.org/"
moz-do-not-send="true">http://lists.allstarlink.org/</a><wbr>cgi-bin/mailman/listinfo/app_<wbr>rpt-users
and scroll down to the bottom of the page. Enter your email
address and press the "Unsubscribe or edit options button"<br>
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. <br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
App_rpt-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:App_rpt-users@lists.allstarlink.org">App_rpt-users@lists.allstarlink.org</a>
<a class="moz-txt-link-freetext" href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users">http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users</a>
To unsubscribe from this list please visit <a class="moz-txt-link-freetext" href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users">http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users</a> 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. </pre>
</blockquote>
<br>
</body>
</html>