[arm-allstar] Node registration failures

[Chris Zenchenko]

Following up on this.
It has been a week and my nodes still won't register.
The nscheck returns good on all look-ups.
The ping to register.allstarlink.org returns just fine.
The nodes just won't register.
I've left the computer off for anywhere from 5 minutes to over an hour.
There must be some log or something that can tell me why the server won't
register my nodes.
It did in the past as indicated in my earlier message.
I'm completely stuck.


-----Original Message-----
From: arm-allstar <arm-allstar-bounces at hamvoip.org> On Behalf Of "Doug
Crompton via arm-allstar"
Sent: Tuesday, June 19, 2018 10:26 AM
To: ARM Allstar <arm-allstar at hamvoip.org>
Cc: Doug Crompton <wa3dsp at gmail.com>
Subject: Re: [arm-allstar] Node registration failures

Chris,

  It seems you are doing everything right and since it is happening on
multiple nodes it is not anything you are doing. The problem is the Allstar
registration server which we know has problems. The fact that you are
having the problem might be related to, but not the fault of, your Internet
connection. If a connection goes down and you lose registration using the
current registration system it could fail to return in some cases. This
could happen in just a minute or two. When this happens as you have found
out the only answer is to go completely offline for a period and then
return.

The answer is a new registration server which we are about to introduce. So
if you can bear with it for a bit we should have an answer and since you
are apparently experiencing this problem consistently you would be a prime
candidate for a beta test. This will be happening very soon.


*73 Doug*

*WA3DSP*

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


On Tue, Jun 19, 2018 at 11:14 AM, "Chris Zenchenko via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> Looking for ways to troubleshoot an on-going problem with nodes failing to
> register.
>
> 1.      No changes in server info on allstar.org.
> 2.      2. No changes in .conf files
> 3.      3. No changes in public ip of server with nodes.
> 4.      4. 60 minutes or more with node server powered down.
> 5.      5. Nodes registered and working and connecting at times.
> 6.      Using new dns method.
> 7.      7. Confirmed pings to allstar registration server.
> 8.      8. Successful pings to servers during system_diagnostics.
> 9.      Code updates have been run.
>
> This registration problem has been popping up over the past two months or
> so.
> In the latest case I was out of town for 5 days.
> When I left nodes were connecting and all was well.
> When I returned nodes could not connect and check_reg returned
> unregistered.
> See above points.
> I have no idea where to look next but stability just doesn't exist.
> In the past I have tried the 5 to 10 minute power off with success but it
> shouldn't be necessary several times per week.
> The latest failure to register has gone on since Sunday evening and still
> wasn't working this morning.
> There must be a logical reason for this but I can't find it.
> Any thoughts would be helpful
> tnx
>
> _______________________________________________
>
> 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