[arm-allstar] Pi lockup

[David McGough]

Hi Tom,

Are you streaming to Broadcastify or writing anything (like audio logs) to 
the network regularly?

I've not been able to duplicate this with "typical" installations, so far.  
There have been a few reports of issues similar to yours, however.

I have duplicated this type issue in one scenario, which probably isn't
common for most installations, but is how I've got my systems setup. For
all my tower mounted RPi3 systems, I log audio, etc., to a remote NFS
share with "spinning" hard drives located on the ground.  Typically the
microwave link between the tower top and ground is VERY reliable; up until
one day when on-tower power repairs were underway and some power was
turned off for several hours.  The NFS share wasn't accessible at that
point, and trying to write to it caused the writing process to block---the
app_rpt RPT thread, in this case. And, the world stopped spinning, of
course (i.e.: repeater was down, dazed and confused).

I've got a solution to this problem in progress now.

Do you have anything similar in your setup?

73, David KB4FXC



On Tue, 4 Dec 2018, "Tom Eaton via ARM-allstar" wrote:

> If my pi loses internet connection, node does not work as a controller on
> my repeater until internet is back up, can someone tell me why. running
> latest update.
> 
> Thanks
> Tom KC4CBQ
> _______________________________________________
> 
> 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 web page - http://hamvoip.org
>