Node can no longer connect

App_rpt-users
1

since doing an update to my system my node apparently can not connect to anyone or anyone connect to me… i get errors…
Failed to get unit file state for asl3-update-nodelist.service: No such file or directory
Failed to restart asl3-update-nodelist.service: Unit asl3-update-nodelist.service not found.
Failed to get unit file state for asl3-update-nodelist.service: No such file or directory
Failed to restart asl3-update-nodelist.service: Unit asl3-update-nodelist.service not found.
Failed to restart asl3-update-nodelist.service: Unit asl3-update-nodelist.service not found.

any ideas?

2

also seeing this error coming through
[2024-11-17 19:07:27.246] WARNING[20235][C-0000002f]: func_channel.c:569 func_channel_read: Unknown or unavailable item requested: ‘peerip’

when i try to connect to 56332 it does nothing, no errors or anything, connecting to any other node, it tries, then says “connection failed”

3

more log information…

[2024-11-17 17:56:15.387] WARNING[1311] app_rpt.c: attempt_reconnect: cannot find node 56332
[2024-11-17 17:56:20.612] WARNING[1311] app_rpt.c: attempt_reconnect: cannot find node 56332
[2024-11-17 17:56:25.849] WARNING[1311] app_rpt.c: attempt_reconnect: cannot find node 56332
[2024-11-17 17:56:31.096] WARNING[1311] app_rpt.c: attempt_reconnect: cannot find node 56332
[2024-11-17 17:56:36.337] WARNING[1311] app_rpt.c: attempt_reconnect: cannot find node 56332

4

The 5 most popular reasons for connection failure

5

this was working fine until 3 days ago, now other than echolink it works great

Are you registered ? Are you in the nodes list located /var/lib/asterisk/rpt_extnodes this file does not exist in my system

Do you have a path to the connection ? Yes, it has worked well in the past

IAX Port = 4569 which is also open on my router.

again this all worked fine until 3 days ago when i did a system/software update

6

I think allstarlink is having a global issue at the moment, and I’m pretty sure they are aware/working on it.
I can see that your node is registered but there is no DNS entry for it.
And there should be.
dig @ns-1467.awsdns-55.org 56332.nodes.allstarlink.org txt

; <<>> DiG 9.18.28-1~deb12u2-Debian <<>> @ns-1467.awsdns-55.org 56332.nodes.allstarlink.org txt
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 16640
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;56332.nodes.allstarlink.org. IN TXT

;; AUTHORITY SECTION:
nodes.allstarlink.org. 900 IN SOA ns-868.awsdns-44.net. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400

;; Query time: 47 msec
;; SERVER: 205.251.197.187#53(ns-1467.awsdns-55.org) (UDP)
;; WHEN: Sun Nov 17 22:37:56 EST 2024
;; MSG SIZE rcvd: 140

root@ASL3:~# dig @ns-1467.awsdns-55.org 56332.nodes.allstarlink.org txt

; <<>> DiG 9.18.28-1~deb12u2-Debian <<>> @ns-1467.awsdns-55.org 56332.nodes.allstarlink.org txt
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 5425
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;56332.nodes.allstarlink.org. IN TXT

;; AUTHORITY SECTION:
nodes.allstarlink.org. 900 IN SOA ns-868.awsdns-44.net. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400

;; Query time: 51 msec
;; SERVER: 205.251.197.187#53(ns-1467.awsdns-55.org) (UDP)
;; WHEN: Sun Nov 17 22:41:39 EST 2024
;; MSG SIZE rcvd: 140

7

that is the node i am trying to connect to can you see my node 62225?

8

I can see that 62225 is registered using the allstarlink live node list on the website.
I also see you in DNS but the problem that is going on is that these are not updating.
Looks like if you bring up a new node or change the node’s Internet connection It’s currently broken.
So if your IP/port has not changed (today) you’re probably ok…
Most people will not notice the problem right away.
And it will likely get fixed soon.
I have some very broken stuff right now because I changed Internet connections earlier today.
62225.nodes.allstarlink.org. 60 IN TXT “NN=62225” “RT=2024-11-17 12:41:15” “RB=1” “IP=204.X.X.102” “PIP=0” “PT=4569” “RH=register-west”

9

Still unable to connect to most nodes.

Anyone have an update?

10

@kb0rpj can you be more specific about what you mean by “still unable to connect to most nodes”?

Your issue overnight was that your node was perceived to have been not registering/re-registering for more than 24 hours. I implemented a new cleanup process for the DNS records where if the node database hasn’t updated the timestamp was more than 24 hours old. Your node was removed as one of 13 nodes at 0000 UTC (7p 11/17) for inactivity. Was it offline for a period of time?

What system are you running? ASL3 or something else?

11

yes ASL3 on debian 12

Out of 4 nodes i tried, i was only able to connect to 1 node.

as far as i know the node has been running correctly. I checked allmon3 before the weekly net last night and it showed 56332 at “connecting” i had him reboot 56332 and it wouldn’t even try to connect at this point. i rebooted my end, no change

so i tried 42605, 40297, 61244, and 61693, all but 61244 says “connection failed” as soon as it tries to connect,

AllStar registrations: │
│ │
│ “rpt show registrations” │
│ │
│ Host Username Perceived │
│ Refresh State │
│ 34.105.111.212:443 62225 │
│ 204.48.104.102:4569 179 Registered │
│ 1 HTTP registration. │
│ │
│ “iax2 show registrations” │
│ │
│ Host dnsmgr Username Perceived │
│ Refresh State │
│ 0 IAX2 registrations.

the only other issue is, i am unable to start the node list update, says node list service is not found, i am not sure if that is related or not

12

at 818am (cst) i tried the connection again and it was able to connect to 56332 normally