[arm-allstar] A way to check allstar connection status

[Justin Grigg]

This system has been running for a few months. I am not on-site to check,
but it happens a couple times a week. There are currently three separate
nodes on an internal network. We realize it’s down when the three separate
networks stop talking to each other. If you look at the all star webpage
status during this time, you will see a connection error message. Once you
restart, everything functions normally. There initial thought of the script
was simply to log the issue to see how often it’s happening.






On Tue, Apr 21, 2020 at 8:05 PM "Bryan St Clair via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> You able to see the connection state on the node when this happens? (Not
> deployed yet?)
>
> Does it happen daily? Hourly?
>
> Can it connect out when someone can not connect in?
>
> Bryan
>
> On Tue, Apr 21, 2020, 16:47 "Justin Grigg via ARM-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > it is just that external AllStar nodes can not connect as it acts like
> the
> > node is down.
> >
> > On Tue, Apr 21, 2020 at 7:42 PM "Bryan St Clair via ARM-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> > > Hourly would be the minimum time I would repeat the checks like yours.
> > >
> > > But I don't understand why you would need this.  What exactly is
> > happening
> > > for you to loose registration?  (My best guess at this moment) Assuming
> > > this is a public node.
> > >
> > > The allstar servers only provide a connection location, all
> > services/paths
> > > are node to node.
> > >
> > > If your reg status is failing, that should be fixed as it rarely
> happens
> > on
> > > my nodes.   Unless perhaps your Internet connection is dropping?
> > >
> > > Bryan
> > >
> > >
> > >
> > > On Tue, Apr 21, 2020, 16:34 "Justin Grigg via ARM-allstar" <
> > > arm-allstar at hamvoip.org> wrote:
> > >
> > > > Bryan,
> > > > Thank you for the information and I was leaning that way at first.
> The
> > > > weird part is when the node I am helping with falls into this error
> > > state,
> > > > it is still functioning as an RF repeater and can still ping
> websites.
> > It
> > > > has just lost the connection to allstarlink. Once you cycle asterisk
> it
> > > > reconnects and comes right back up.
> > > >
> > > > I spent this evening creating a script that I believe will take care
> of
> > > > this. It pulls down the text from the allstar node website and
> searches
> > > the
> > > > text for the connection error. If detected, it runs a script that is
> > > > defined in the variables. I have it running a custom asterisk restart
> > > > script.
> > > >
> > > > If I run this hourly, do you think that would be a problem?
> > > >
> > > > Thank you for your quick response!!
> > > >
> > > > Justin
> > > >
> > > >
> > > >
> > > > On Tue, Apr 21, 2020 at 1:20 PM "Bryan St Clair via ARM-allstar" <
> > > > arm-allstar at hamvoip.org> wrote:
> > > >
> > > > > If you want to trigger off a dns error, do just that.
> > > > >
> > > > > Script a dns query on your own node number and if a error returns,
> > > > perform
> > > > > the action you want.
> > > > >
> > > > > But I wouldn't run it too often, I could see that loop easily if
> > there
> > > > was
> > > > > ever a slow update to registration status.
> > > > >
> > > > > Would be smarter to setup a reverse ssh tunnel and you can restart
> it
> > > as
> > > > > needed.
> > > > >
> > > > > On Tue, Apr 21, 2020, 10:11 "Justin Grigg via ARM-allstar" <
> > > > > arm-allstar at hamvoip.org> wrote:
> > > > >
> > > > > > Hello,
> > > > > > I am working on depoying a repeater that will be using a hamvoip
> > node
> > > > as
> > > > > a
> > > > > > controller. This site will have a cellular connection for data
> but
> > it
> > > > is
> > > > > > hard to access. I have a script that will trigger a restart if a
> > > > network
> > > > > > connection is lost, but I am worried about an unrepnisve node.
> > > > > >
> > > > > > My question is if there is a way to check for the node's status
> on
> > > > > Allstar
> > > > > > via bash? I have seen nodes that get locked up and show the
> status
> > > > "Node
> > > > > > ###### is not in the stats database, invalid node number or a
> > > temporary
> > > > > > communications error, please try again later". I want to trigger
> a
> > > > > > asterisks restart automaitclly if this happens.
> > > > > >
> > > > > > Is this possible?
> > > > > >
> > > > > > Thanks!!
> > > > > >
> > > > > > Justin
> > > > > > _______________________________________________
> > > > > >
> > > > > > 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
> > > > >
> > > > _______________________________________________
> > > >
> > > > 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
> > >
> > _______________________________________________
> >
> > 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
>