[arm-allstar] Pi lockup

[Doug Crompton]

We are definitely looking into this issue but so far have not been able to
duplicate it, Knowing exactly how you are connected via the Internet is
important and how and what you are connected to at the time. Also if you
are running any add on scripts or programs and if you have made any
modifications to Allstar configs,

Is it WIFI or Wired Connect?
Is it DHCP or Static on the Pi?
Are you using *3 or *73 connects?
How many connections were active?

While it would be difficult for most to do this having HDMI and a keyboard
connected would allow some more troubleshooting. It is doubtful that Linux
itself is hung but rather Allstar.

The most important question here is if this node has been in existence for
awhile did it start doing it at any particular point? This would help in
determining a change that might have caused an issue.

This does not seem to be a widespread problem and since it is hard to
duplicate any further information that could help would be appreciated.


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*

On Wed, Dec 5, 2018 at 10:20 PM "DAVID HARESNAPE via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> We have a node here in the Kansas City area doing the same thing.  It is
> located on top of a business building, and it has done this twice so far.
> Internet was lost last Saturday and just came back today around midday. The
> repeater was down during this time, but came back up when the ISP was
> restored. We are also using the latest versions, a Pi3, and a DMK URI.  I
> have not been able to duplicate this with any of our other nodes.  Have not
> had this problem before, after several years of using Allstar Asterisk.
>
> If anyone has any ideas on what could be causing this, suggestions
> appreciated.  Unfortunately, I do not know who the ISP is, nor do we have
> any control over it, as it is provided for us by someone else.
>
> Dave Haresnape WB0OUE
> Edgerton, KS
>
>
> ----- Original Message -----
> From: "Chris Viningre via ARM-allstar" <arm-allstar at hamvoip.org>
> To: "arm-allstar" <arm-allstar at hamvoip.org>
> Cc: "Chris Viningre" <chrisviningre at gmail.com>
> Sent: Wednesday, December 5, 2018 6:56:51 PM
> Subject: Re: [arm-allstar] Pi lockup
>
> I have this same problem but I just figured that's the way it was. For me
> it not a big issue. It happens anytime I lose internet for a long period of
> time. This happens every time I'm driving to work. My commute is 1 1/4 hr.
> drive and half of that time I'm in a dead area with not cellphone service.
> I'm unable to control my node in any way. Don't even get a connect
> beep. The only thing I can do is log onto Supermon and control it. Most of
> this time once I get back into cell range everything starts working.
> Sometime It doesn't and I have to restart Asterisk. I have duplicated this
> problem at home by disconnecting my internet and waiting. I haven't made
> note on how long. I hope this information helps.
>
> Chris Viningre WS5B
> 70 W. Roadrunner
> Salt Flat, Texas 79847
> C:(915) 504-1510
> chrisviningre at gmail.com
>
>
>
> On Tue, Dec 4, 2018 at 4:06 PM "David McGough via ARM-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> >
> > 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
> > >
> >
> > _______________________________________________
> >
> > 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
> >
> _______________________________________________
>
> 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
> _______________________________________________
>
> 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
>