irlp server 3 44.48.26.1


John
 

Greetings..

Was there a breakdown today?
My logs show my node 6163 had an issue with this server.
PASTE
Jan 13 2021 01:15:56 +1000 ipupdate: WARNING - Comms error to server 44.48.26.1. Cant obtain current IP.
Jan 13 2021 01:40:26 +1000 ipupdate: WARNING - Comms error to server 44.48.26.1. Cant obtain current IP.
Jan 13 2021 01:46:40 +1000 ipupdate: WARNING - Comms error to server 44.48.26.1. Cant obtain current IP.
Jan 13 2021 02:13:20 +1000 ipupdate: The IP has changed from 124.170.91.198 to 124.170.72.13.


My router shows it's been up for 46 days.

FWIW, I had a scammer call me today at 1600K suggesting my NBN service had an problem. She made the mistake of naming my server incorrectly, so we told her to bugger off !

73 John
VK4JKL


David Cameron - IRLP
 

The service did not go down, and those errors are placed when the node is not able to contact the server on port 10000 for whatever reason. Often the problem is an outage of DNS or something with your service.

They happen - the node just logs them.

Dave Cameron

On 2021-01-13 1:27 a.m., John wrote:
Greetings..
Was there a breakdown today?
My logs show my node 6163 had an issue with this server.
PASTE
Jan 13 2021 01:15:56 +1000 ipupdate: WARNING - Comms error to server 44.48.26.1. Cant obtain current IP.
Jan 13 2021 01:40:26 +1000 ipupdate: WARNING - Comms error to server 44.48.26.1. Cant obtain current IP.
Jan 13 2021 01:46:40 +1000 ipupdate: WARNING - Comms error to server 44.48.26.1. Cant obtain current IP.
Jan 13 2021 02:13:20 +1000 ipupdate: The IP has changed from 124.170.91.198 to 124.170.72.13.
My router shows it's been up for 46 days.
FWIW, I had a scammer call me today at 1600K suggesting my NBN service had an problem. She made the mistake of naming my server incorrectly, so we told her to bugger off !
73 John
VK4JKL


Dave K9DC
 

While not mission critical, the 44.48.26.1 server is located in Chicago. I would have expected your node to first try 44.136.33.1, located in Sydney. You might want to look through your environment file and see if you have the parameter "export SERVER_OVERRIDE=server3” set. If it is, just hash # out the line, and restart the node. Then you will start talking with Sydney.

There was a period of time a couple of years ago, when the Australia server was being particularly flaky and intermittent. You may have set SERVER_OVERRIDE to use Chicago. But those problems are far behind us. Server4 is now sitting in a very robust data center in Sydney. The same machine hosts Reflector 9600 and all the IRLP VPN clients for VK and ZL. It’s worth a look.

-k9dc

On Jan 13, 2021, at 04:27, John <gielisj@westnet.com.au> wrote:

Greetings..

Was there a breakdown today?
My logs show my node 6163 had an issue with this server.
PASTE
Jan 13 2021 01:15:56 +1000 ipupdate: WARNING - Comms error to server 44.48.26.1. Cant obtain current IP.
Jan 13 2021 01:40:26 +1000 ipupdate: WARNING - Comms error to server 44.48.26.1. Cant obtain current IP.
Jan 13 2021 01:46:40 +1000 ipupdate: WARNING - Comms error to server 44.48.26.1. Cant obtain current IP.
Jan 13 2021 02:13:20 +1000 ipupdate: The IP has changed from 124.170.91.198 to 124.170.72.13.


My router shows it's been up for 46 days.

FWIW, I had a scammer call me today at 1600K suggesting my NBN service had an problem. She made the mistake of naming my server incorrectly, so we told her to bugger off !

73 John
VK4JKL


John
 

Thanks to both Dave's.

It is still a mystery..

Dave VE7LTD
The +1000 is UTC +10 hours

Dave K9DC
1. There is no "export SERVER_OVERRIDE=server3” in my environment file, or any mention of a server.
2. In /home/irlp/local/serverip there is one line - 44.136.33.1
Is this where we reference my irlp server?
That serverip file has today's date. Perhaps the custom.crons updated that?
3. There was no DC or Cat5 issues (to my knowledge) for the node. It resides in my shack.

73 John

On 14/01/2021 6:58:47 AM, Dave K9DC via groups.io (Dave=dcg.us@groups.io) wrote:
While not mission critical, the 44.48.26.1 server is located in Chicago. I would have expected your node to first try 44.136.33.1, located in Sydney. You might want to look through your environment file and see if you have the parameter "export SERVER_OVERRIDE=server3” set. If it is, just hash # out the line, and restart the node. Then you will start talking with Sydney.
There was a period of time a couple of years ago, when the Australia server was being particularly flaky and intermittent. You may have set SERVER_OVERRIDE to use Chicago. But those problems are far behind us. Server4 is now sitting in a very robust data center in Sydney. The same machine hosts Reflector 9600 and all the IRLP VPN clients for VK and ZL. It’s worth a look.
-k9dc

On Jan 13, 2021, at 04:27, John <gielisj@westnet.com.au> wrote:
Greetings..
Was there a breakdown today?
My logs show my node 6163 had an issue with this server.
PASTE
Jan 13 2021 01:15:56 +1000 ipupdate: WARNING - Comms error to server 44.48.26.1. Cant obtain current IP.
Jan 13 2021 01:40:26 +1000 ipupdate: WARNING - Comms error to server 44.48.26.1. Cant obtain current IP.
Jan 13 2021 01:46:40 +1000 ipupdate: WARNING - Comms


Dave K9DC
 

No, your preferred server is determined by running the command scripts/find_best_server, which is part of update, call, connect-to-reflector etc. Its output is stored in local/serverip. But that is where your node starts the server rotation. In your case you will start out with server4, if server4 does not respond, it will continue through to the others. Any one of them will do. Most of the time, your node will pick server4 because your node number starts with 6.

I have no idea why your node picked server3 that time. But it doesn’t really matter. As I said, any one of the five servers will do.

-k9dc

On Jan 13, 2021, at 18:56, John <gielisj@westnet.com.au> wrote:

Thanks to both Dave's.

It is still a mystery..

Dave VE7LTD
The +1000 is UTC +10 hours

Dave K9DC
1. There is no "export SERVER_OVERRIDE=server3” in my environment file, or any mention of a server.
2. In /home/irlp/local/serverip there is one line - 44.136.33.1
Is this where we reference my irlp server?
That serverip file has today's date. Perhaps the custom.crons updated that?
3. There was no DC or Cat5 issues (to my knowledge) for the node. It resides in my shack.

73 John

On 14/01/2021 6:58:47 AM, Dave K9DC via groups.io (Dave=dcg.us@groups.io) wrote:
While not mission critical, the 44.48.26.1 server is located in Chicago. I would have expected your node to first try 44.136.33.1, located in Sydney. You might want to look through your environment file and see if you have the parameter "export SERVER_OVERRIDE=server3” set. If it is, just hash # out the line, and restart the node. Then you will start talking with Sydney.
There was a period of time a couple of years ago, when the Australia server was being particularly flaky and intermittent. You may have set SERVER_OVERRIDE to use Chicago. But those problems are far behind us. Server4 is now sitting in a very robust data center in Sydney. The same machine hosts Reflector 9600 and all the IRLP VPN clients for VK and ZL. It’s worth a look.
-k9dc
On Jan 13, 2021, at 04:27, John <gielisj@westnet.com.au> wrote:
Greetings..
Was there a breakdown today?
My logs show my node 6163 had an issue with this server.
PASTE
Jan 13 2021 01:15:56 +1000 ipupdate: WARNING - Comms error to server 44.48.26.1. Cant obtain current IP.
Jan 13 2021 01:40:26 +1000 ipupdate: WARNING - Comms error to server 44.48.26.1. Cant obtain current IP.
Jan 13 2021 01:46:40 +1000 ipupdate: WARNING - Comms




John
 

OK I'm satisfied Dave

Today I was looking for a birdy in the QTH
so we started shutting things down.
When the main router rebooted, and synced with my server
I dialled up ipupdate and recorded this..


/home/irlp/log$ ipupdate
CURRENT IP address obtained from dyndns.org
Obtaining last IP from file.
The CURRENT IP is : 124.170.91.182
The LAST IP was : 124.170.72.13
The IP has changed from 124.170.72.13 to 124.170.91.182. Updating the server.
Trying 44.136.33.1, port 15426...
Connected to 44.136.33.1
Authentication Complete, sending Update info

So perhaps Sydney server was non compos mentis the other day.

73 John

On 14/01/2021 10:18 am, Dave K9DC via groups.io wrote:
No, your preferred server is determined by running the command scripts/find_best_server, which is part of update, call, connect-to-reflector etc. Its output is stored in local/serverip. But that is where your node starts the server rotation. In your case you will start out with server4, if server4 does not respond, it will continue through to the others. Any one of them will do. Most of the time, your node will pick server4 because your node number starts with 6.
I have no idea why your node picked server3 that time. But it doesn’t really matter. As I said, any one of the five servers will do.
-k9dc

On Jan 13, 2021, at 18:56, John <gielisj@westnet.com.au> wrote:

Thanks to both Dave's.

It is still a mystery..

Dave VE7LTD
The +1000 is UTC +10 hours

Dave K9DC
1. There is no "export SERVER_OVERRIDE=server3” in my environment file, or any mention of a server.
2. In /home/irlp/local/serverip there is one line - 44.136.33.1
Is this where we reference my irlp server?
That serverip file has today's date. Perhaps the custom.crons updated that?
3. There was no DC or Cat5 issues (to my knowledge) for the node. It resides in my shack.

73 John

On 14/01/2021 6:58:47 AM, Dave K9DC via groups.io (Dave=dcg.us@groups.io) wrote:
While not mission critical, the 44.48.26.1 server is located in Chicago. I would have expected your node to first try 44.136.33.1, located in Sydney. You might want to look through your environment file and see if you have the parameter "export SERVER_OVERRIDE=server3” set. If it is, just hash # out the line, and restart the node. Then you will start talking with Sydney.
There was a period of time a couple of years ago, when the Australia server was being particularly flaky and intermittent. You may have set SERVER_OVERRIDE to use Chicago. But those problems are far behind us. Server4 is now sitting in a very robust data center in Sydney. The same machine hosts Reflector 9600 and all the IRLP VPN clients for VK and ZL. It’s worth a look.
-k9dc
On Jan 13, 2021, at 04:27, John <gielisj@westnet.com.au> wrote:
Greetings..
Was there a breakdown today?
My logs show my node 6163 had an issue with this server.
PASTE
Jan 13 2021 01:15:56 +1000 ipupdate: WARNING - Comms error to server 44.48.26.1. Cant obtain current IP.
Jan 13 2021 01:40:26 +1000 ipupdate: WARNING - Comms error to server 44.48.26.1. Cant obtain current IP.
Jan 13 2021 01:46:40 +1000 ipupdate: WARNING - Comms