[arm-allstar] Unable to View Node Status - Can not find info for node 40260

[David McGough]

Hi Jeff,

What you're seeing isn't an installation issue. The ASL network folks made 
some major network infrastructure ungrades this last week and the dust 
still seems to be settling.

The stats.allstarlink.org message: "Can not find info for node 40260, 
invaild node number or a temporary communications error, please try again 
later. " isn't a show-stopper.  You're still operable.

Leave the node on-line for a few hours and we'll keep our finger crossed 
that it starts showing up on the stats system.

Again, this isn't a show-stopper.

73, David KB4FXC



On Sat, 2 Jan 2021, Jeff Hochberg wrote:

> Hi David,
> 
> Thanks for your quick response. Unfortunately those changes don't
> make a difference.
> 
> I had only modified the remote base/frequency agile options (from no to
> yes) a few minutes ago. They had been set to the default settings all along.
> 
> When I ran through the initial setup wizard, there was a question that
> asked if I wanted to send stats to AllStarLink...I chose yes. That's how
> I've been answering the question each time.
> 
> When I looked in rpt.conf, the two lines you asked me to uncomment were
> already uncommented.
> 
> FYI I've even re-imaged the SD card - even used different SD cards -
> several times. This happens consistently each and every time. I've been
> fighting with it for 2 days straight.
> 
> [image: image.png]
> 
> 
> ***************************************************
> Georgia Digital: http://dmr.georgiadigital.net/ipsc
> GeorgiaDMR.net on Groups.io: https://groups.io/g/GeorgiaDMR
> Appalachian Trail Golden Packet: https://atgp.groups.io/g/main
> ***************************************************
> 
> Jeff Hochberg
> W4JEW
> Atlanta, GA
> 404-304-4575
> jeff at w4jew.com
> 
> 
> On Sat, Jan 2, 2021 at 5:31 PM David McGough <kb4fxc at inttek.net> wrote:
> 
> >
> > Jeff,
> >
> > There are a couple of issues that I see. First, go to the allstarlink.org
> > portal and into the section Portal-->node settings-->40260 ...On this
> > setup screen, take a look at the right side and set "Is node a remote base
> > station?" to NO and set "If remote base, is it frequency agile?" to NO.
> >
> > ...And, save the settings (submit).
> >
> > Then, on your node itself, login and go the the bash shell prompt (admin
> > menu #9). Then, edit (e.g.: nano) the /etc/asterisk/rpt.conf file.  Look
> > down the [40260] stanza to the point where you see the statpost lines and
> > uncomment them, like this:
> >
> > ...change:
> >
> > ;statpost_program=/etc/asterisk/local/send_node_stats.sh
> > ;statpost_url=none
> >
> > ...to:
> >
> > statpost_program=/etc/asterisk/local/send_node_stats.sh
> > statpost_url=none
> >
> >
> > ...then, save the file. Type "exit" to go back to the admin menu and then
> > reboot.
> >
> > These changes should get you fixed up.
> >
> > 73, David KB4FXC
> >
> >
> > > Date: Sat, 2 Jan 2021 17:16:58 -0500
> > > From: Jeff Hochberg <jeff at w4jew.com>
> > > To: arm-allstar at hamvoip.org
> > > Subject: Unable to View Node Status - Can not find info for node 40260
> > >
> > > Hello,
> > >
> > > This is driving me crazy! I've been fighting with this for a couple of
> > > days and can't really find anything that indicates what the issue might
> > > be.
> > >
> > > When I go to Lists & Stats, AllStar Node List, then I look up my node ID
> > > number (40260). The indicator is lit up green (see screenshot) -
> > something
> > > thinks I'm connected. Then I click on the 40260 link and consistently get
> > > the following message:
> > >
> > > "Can not find info for node 40260, invaild node number or a temporary
> > > communications error, please try again later."
> > >
> > > At first, I thought there was a firewall issue, however I literally have
> > > the Pi hanging out on the naked Internet...no NAT...no firewall
> > whatsoever
> > > and I'm still getting the same results.
> > >
> > > If I check /var/log/asterisk/messages, I see the following:
> > >
> > > Registered IAX2 to '34.105.111.212', who sees us as 23.127.128.81:4569
> > > with no messages waiting
> > >
> > > That looks good, right? So what else might be wrong with my
> > configuration?
> > >
> >
> >
>