[arm-allstar] allstar node with hamvoip stopped reading cos correctly

[David McGough]

I wanted to add a final comment about this.

I helped ku6v get his issues resolved. The problems he had were simple
configuration issues--basically a accidental config oops. The issues
having showed up when he performed an update was simply a coincidence;
asterisk hadn't been restarted after the earlier config oops. When the
update was performed, asterisk got restarted and suddenly the new problem 
showed up. This made it seem like the update broke the system. In reality, 
the minor config file change from weeks earlier is what actually broke 
it.

BTW, this type of scenario is the #1 cause of "the update broke my system"
type complaints that Doug & I hear. There have been a few cases where an
update really did fail to install properly, but they're rare. In most
cases I've seen, these failures were traced to weak 5V power supplies,
causing the SD card to get progressively corrupted over time.

So, the moral of the story is two fold. First, make a backup of your 
/etc/asterisk config files before and after you change something! And, 
second, if you're really having files on the SD card get clobbered, check 
that 5V power supply!


73, David KB4FXC


On Sat, 28 Mar 2020, "Rick Dykstra via ARM-allstar" wrote:

> If you're using and SD card, it's possible a file was corrupted during 
the write. I've seen this twice now on a couple of my nodes when 
updating rpt.conf.  I renamed the file and copied a back up version, and 
restarted asterisk. Problem was solved.


Rick - KR8T

On 3/27/2020 4:15 PM, "ku6v via ARM-allstar" wrote:
> On node 46533 I checked for an update 4 days or so ago. The node was
> connected and working fine before the next chain of events described below
> this.
>
> After the attempt to do so the node went into a mode that only sees COS
> present and that then locks up in TX.
>
> I have reset the power with a web power switch on the mountain remote site.
> No change.
>
> I have disconnected the URI interface and isolated the node from the RLC4
> that connects all the RF radios and repeaters to the node. This leaves the
> node 46533 isolated from the RLC4 and all the other hardware logic inputs
> that would influence the node input logic gates.
>
> I then attempted to reload or check for an update that might clear the issue
> that appeared after the attempt to check for update, item 1, on the admin
> console. However, no new update was available.
>
> Can I force and update OR should I simply start over and reload the Hamvoip
> software?
>
> Any and all input is appreciated.
>
> Wishing to all you are staying safe and healthy as we all go forward.
>
>   
>
> 73 de KU6V
>
> Don
>
>   
>
> _______________________________________________
>
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3/4 web page - http://hamvoip.org
_______________________________________________

ARM-allstar mailing list
ARM-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar

Visit the BBB and RPi2/3/4 web page - http://hamvoip.org