<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Answers in-line.<br>
<br>
<blockquote type="cite"
cite="mid:383f4498-dcd1-5255-1d93-e034a38aa861@midnighteng.com">
<div class="moz-cite-prefix">On 7/11/2018 11:47 PM, Jim Aspinwall
No1PC wrote:<br>
</div>
<blockquote type="cite"
cite="mid:760729266.2648127.1531367247395@mail.yahoo.com">
<meta http-equiv="content-type" content="text/html;
charset=utf-8">
<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>
</div>
</blockquote>
</blockquote>
Lem me see if I understand, you blew which image on to a "new USB
flash device"? what hardware did you try to boot? Do I understand
that you tried to boot a "new USB flash device"
<blockquote type="cite"
cite="mid:383f4498-dcd1-5255-1d93-e034a38aa861@midnighteng.com">
<blockquote type="cite"
cite="mid:760729266.2648127.1531367247395@mail.yahoo.com">
<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><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>
</div>
</div>
</div>
</blockquote>
</blockquote>
I would guess possible with a bad disk.<br>
<blockquote type="cite"
cite="mid:383f4498-dcd1-5255-1d93-e034a38aa861@midnighteng.com">
<blockquote type="cite"
cite="mid:760729266.2648127.1531367247395@mail.yahoo.com">
<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> <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>
</div>
</div>
</div>
</blockquote>
</blockquote>
Bad disk.<br>
<blockquote type="cite"
cite="mid:383f4498-dcd1-5255-1d93-e034a38aa861@midnighteng.com">
<blockquote type="cite"
cite="mid:760729266.2648127.1531367247395@mail.yahoo.com">
<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> <br>
NO low voltage errors on the console... all this on a
known Pi3 AND RA-40 interface configuration under prior
Jessie install...<br>
</div>
</div>
</div>
</blockquote>
</blockquote>
Ah, so this is a Pi 3. OK, back to my first question. You blew the
latest Raspbian image on to a "new USB flash device" and booted it
in a Raspberry Pi 3?<br>
<blockquote type="cite"
cite="mid:383f4498-dcd1-5255-1d93-e034a38aa861@midnighteng.com">
<blockquote type="cite"
cite="mid:760729266.2648127.1531367247395@mail.yahoo.com">
<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> <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>
</div>
</div>
</div>
</blockquote>
</blockquote>
This looks to me like a bad burn. to a "new USB flash device"
<blockquote type="cite"
cite="mid:383f4498-dcd1-5255-1d93-e034a38aa861@midnighteng.com">
<blockquote type="cite"
cite="mid:760729266.2648127.1531367247395@mail.yahoo.com">
<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> 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>
</div>
</div>
</div>
</blockquote>
</blockquote>
OK, give me /var/log/syslog. /var/log/messages and
/var/log/asterisk/messages.<br>
<blockquote type="cite"
cite="mid:383f4498-dcd1-5255-1d93-e034a38aa861@midnighteng.com">
<blockquote type="cite"
cite="mid:760729266.2648127.1531367247395@mail.yahoo.com">
<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> <br>
That said...the latest Jessie build is a failure. The
latest Stretch build is a failure. "change my mind"<br>
</div>
</div>
</div>
</blockquote>
</blockquote>
There are a LOT of ASL 1.01 installs on RPi hardware out in the
field. If the image did not work we would know by now.<br>
<blockquote type="cite"
cite="mid:383f4498-dcd1-5255-1d93-e034a38aa861@midnighteng.com">
<blockquote type="cite"
cite="mid:760729266.2648127.1531367247395@mail.yahoo.com">
<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> <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.</div>
</div>
</div>
</blockquote>
</blockquote>
Show me /var/log/syslog and or /var/log/messages<br>
<blockquote type="cite"
cite="mid:383f4498-dcd1-5255-1d93-e034a38aa861@midnighteng.com">
<blockquote type="cite"
cite="mid:760729266.2648127.1531367247395@mail.yahoo.com">
<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>|<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>
</div>
</div>
</div>
</blockquote>
</blockquote>
Are you running with a screen connected to the HDMI port? Show me
the /var/log/boot.log<br>
<blockquote type="cite"
cite="mid:383f4498-dcd1-5255-1d93-e034a38aa861@midnighteng.com">
<blockquote type="cite"
cite="mid:760729266.2648127.1531367247395@mail.yahoo.com">
<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> <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>
</div>
</div>
</div>
</blockquote>
</blockquote>
I'm betting either a bad SD card or take you at your word that you
booted a RPi on a "new USB flash device"
<blockquote type="cite"
cite="mid:383f4498-dcd1-5255-1d93-e034a38aa861@midnighteng.com">
<blockquote type="cite"
cite="mid:760729266.2648127.1531367247395@mail.yahoo.com">
<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> <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>
</div>
</div>
</div>
</blockquote>
</blockquote>
I can see not wanting this left to others but what is a "x-Nix
elitist" <br>
<blockquote type="cite"
cite="mid:383f4498-dcd1-5255-1d93-e034a38aa861@midnighteng.com">
<blockquote type="cite"
cite="mid:760729266.2648127.1531367247395@mail.yahoo.com">
<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> <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>
</div>
</div>
</div>
</blockquote>
</blockquote>
Happy to. Show me the log files<br>
<blockquote type="cite"
cite="mid:383f4498-dcd1-5255-1d93-e034a38aa861@midnighteng.com">
<blockquote type="cite"
cite="mid:760729266.2648127.1531367247395@mail.yahoo.com">
<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> <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>
</div>
</div>
</div>
</blockquote>
</blockquote>
There is a lot more to ASL 1.01 then the menus. That is not to say
that Nate did not do a great job with the menus.<br>
<blockquote type="cite"
cite="mid:383f4498-dcd1-5255-1d93-e034a38aa861@midnighteng.com">
<blockquote type="cite"
cite="mid:760729266.2648127.1531367247395@mail.yahoo.com">
<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> <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>
</div>
</div>
</div>
</blockquote>
</blockquote>
Still trying to figure out what hardware and boot device you are
running.<br>
<blockquote type="cite"
cite="mid:383f4498-dcd1-5255-1d93-e034a38aa861@midnighteng.com">
<blockquote type="cite"
cite="mid:760729266.2648127.1531367247395@mail.yahoo.com">
<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> <br>
Leave all of this to unstable, undocumented Crompton
builds, or do equal or better...<br>
<br>
How can I/we help?</div>
</div>
</div>
</blockquote>
</blockquote>
Give me SSH access to the machine. <br>
See below for my e-mail address.<br>
<br>
Steve N4IRS<br>
<br>
<blockquote type="cite"
cite="mid:383f4498-dcd1-5255-1d93-e034a38aa861@midnighteng.com">
<blockquote type="cite"
cite="mid:760729266.2648127.1531367247395@mail.yahoo.com">
<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><br>
<br>
-------------------</div>
</div>
<div id="ydpbb128784yahoo_quoted_2070487382"
class="ydpbb128784yahoo_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">----------------------------------------------------------------------<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
href="mailto:szingman@msgstor.com" rel="nofollow"
target="_blank" moz-do-not-send="true">szingman@msgstor.com</a>><br>
</div>
<div dir="ltr">To: Users of Asterisk app_rpt <<a
href="mailto:app_rpt-users@lists.allstarlink.org"
rel="nofollow" target="_blank"
moz-do-not-send="true">app_rpt-users@lists.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
href="mailto:b9e5a338-8b97-9d40-5a73-7a1757b76366@msgstor.com"
rel="nofollow" target="_blank"
moz-do-not-send="true">b9e5a338-8b97-9d40-5a73-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>
<br>
</blockquote>
</blockquote>
<br>
</body>
</html>