Allmon3 "Command Successful OK: Unknown node number " / ASL3 issue

G4ZWH · July 1, 2024, 7:45am

Hi all
I’ve just spun up ASL3 on my debian 12 cloud VPS, it’s looking good

All the basic stuff looked ok but when I try link commands from allmon 3, I get the message

Command Successful

OK:
Unknown node number 537100.

CLI shows == Manager ‘admin’ logged on from 127.0.0.1
== Manager ‘admin’ logged off from 127.0.0.1

I assume it’s as I am remotely accessing it, any ideas on where to start looking?
Thanks & 73
Rob G4ZWH

Edit: I’ve noticed the node is not actually accepting incoming connections either, CLI log shows this:

Connected to Asterisk 20.8.1+asl3-3.0.0-1.deb12 currently running on None (pid = 391)
== Manager ‘admin’ logged on from 127.0.0.1
== Manager ‘admin’ logged off from 127.0.0.1
[2024-07-01 09:01:06.746] NOTICE[428]: dnsmgr.c:225 dnsmgr_refresh: dnssrv: host ‘register.allstarlink.org’ chang ed from XX.XX.XX.XXX:443 to XX.XXX.XX.XXX:443
– Accepting UNAUTHENTICATED call from XX.XX.XX.XXX:4570:
– > requested format = gsm,
– > requested prefs = (gsm|ilbc|speex16|ulaw),
– > actual format = ulaw,
– > host prefs = (ulaw|adpcm|gsm),
– > priority = mine
– Executing [537100@radio-secure:1] NoOp(“IAX2/X.X.X.X:4570-10271”, “Connect from node: 537101”) in new stack
– Executing [537100@radio-secure:2] NoOp(“IAX2/X.X.X.X:4570-10271”, “Connect to: 537100”) in new stack
– Executing [537100@radio-secure:3] NoOp(“IAX2/X.X.X.X4570-10271”, “The Channel IP is X.X.X.X”) i n new stack
– Executing [537100@radio-secure:4] GotoIf(“IAX2/8X.X.X.X:4570-10271”, “0?connect”) in new stack
– Executing [537100@radio-secure:5] GotoIf(“IAX2/X.X.X.X:4570-10271”, “1?denylist”) in new stack
– Goto (radio-secure,537100,9)
– Executing [537100@radio-secure:9] GotoIf(“IAX2/X.X.X.X:4570-10271”, “0?:connect”) in new stack
– Goto (radio-secure,537100,12)
– Executing [537100@radio-secure:12] Rpt(“IAX2/X.X.X.X:4570-10271”, “537100”) in new stack
[2024-07-01 09:01:20.809] WARNING[814][C-00000002]: app_rpt.c:6295 rpt_exec: Cannot find specified system node 53 7100
== Spawn extension (radio-secure, 537100, 12) exited non-zero on ‘IAX2/X.X.X.X:4570-10271’
– Hungup ‘IAX2/X.X.X.X:4570-10271’

N8EI · July 1, 2024, 12:09pm

This makes it sound like your node isn’t authenticating properly. What’s the output of rpt localnodes and rpt show registrations?

wd6awp · July 1, 2024, 2:06pm

In addition to what N8EI said, looks like there may be a typo (added space) in the node number. Check your rpt.conf particularly the [nodes] stanza for a space.

Also be sure you understand the new Asterisk template system if you are editing the configs rather than using the menu.

G4ZWH · July 1, 2024, 2:24pm

Thanks both.

Yes I think something at the basic level has gone wrong…!

I used the script, I haven’t changed anything manually. I used fresh install and got the same issue - I will have to manually check the config files when I have a moment.

73
Rob

CLI command prompt shows

Connected to Asterisk 20.8.1+asl3-3.0.0-1.deb12 currently running on None (pid = 1560)

None*CLI> rpt localnodes

Node

NoneCLI> rpt show registrations
Host Username Perceived Refresh State
x.x.x.x:443 537100 x.x.x.x:4569 179 Registered
1 HTTP registration.
NoneCLI>

N8EI · July 1, 2024, 2:52pm

Are there any errors listed in /var/log/asterisk/message.log? That almost looks like whatever channel driver you chose isn’t loading.

Is this the Pi Appliance image or a standard Debian 12 install?

G4ZWH · July 1, 2024, 2:55pm

Oh interesting. These look relevant to your comment

[2024-07-01 08:07:54.158] ERROR[3886][C-00000001] chan_dahdi.c: Unable to dup channel: No such file or directory
[2024-07-01 08:07:54.158] ERROR[3886] app_rpt/rpt_bridging.c: Failed to request pseudo channel
[2024-07-01 08:07:54.159] WARNING[3886] app_rpt.c: Disabled broken repeater 1999
[2024-07-01 08:08:01.167] WARNING[4036][C-00000002] app_rpt.c: Cannot find specified system node 537100
[2024-07-01 08:08:04.069] WARNING[4039][C-00000003] app_rpt.c: Cannot find specified system node 537100

Standard Debian 12 install (fresh Debian 12, fresh ASL3)

Thanks

N8EI · July 1, 2024, 2:57pm

I cannot wait until we’re finally rid of dahdi…

Paste in the output of:

dpkg -l 'dahdi*'
lsmod | grep dah
find /lib/modules/`uname -r`/ -name '*dah*'

G4ZWH · July 1, 2024, 3:00pm

root@None:~# dpkg -l ‘dahdi*’
lsmod | grep dah
find /lib/modules/uname -r/ -name ‘dah’
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
++±==============-=============-============-=================================>
ii dahdi 1:3.1.0-2 amd64 utilities for using the DAHDI ker>
ii dahdi-dkms 1:3.3.0-5+asl all DAHDI telephony interface (dkms k>
ii dahdi-linux 1:3.3.0-5+asl all DAHDI telephony interface - Linux>
un dahdi-source (no description available)
lines 1-9/9 (END)…skipping…
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
++±==============-=============-============-=================================================
ii dahdi 1:3.1.0-2 amd64 utilities for using the DAHDI kernel modules
ii dahdi-dkms 1:3.3.0-5+asl all DAHDI telephony interface (dkms kernel driver)
ii dahdi-linux 1:3.3.0-5+asl all DAHDI telephony interface - Linux userspace parts
un dahdi-source (no description available)
~

N8EI · July 1, 2024, 3:02pm

Interesting. Did you have any errors during the apt install process? Please try running apt install --reinstall dahdi-linux. Then do a modprobe dahdi and then rerun lsmod | grep dah.

G4ZWH · July 1, 2024, 3:04pm

Thanks
I didn’t notice any errors… I could do a clean install and look for any errors?

root@None:~# apt install --reinstall dahdi-linux
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 66.7 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 https://repo.allstarlink.org/public bookworm/main amd64 dahdi-linux all 1:3.3.0-5+asl [66.7 kB]
Fetched 66.7 kB in 1s (116 kB/s)
(Reading database ... 52587 files and directories currently installed.)
Preparing to unpack .../dahdi-linux_1%3a3.3.0-5+asl_all.deb ...
Unpacking dahdi-linux (1:3.3.0-5+asl) over (1:3.3.0-5+asl) ...
Setting up dahdi-linux (1:3.3.0-5+asl) ...

N8EI · July 1, 2024, 3:05pm

That can’t have been all of the output of the apt install --reinstall?

G4ZWH · July 1, 2024, 3:08pm

Yep it stopped there:

root@None:~# apt install --reinstall dahdi-linux
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 66.7 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 https://repo.allstarlink.org/public bookworm/main amd64 dahdi-linux all 1:3.3.0-5+asl [66.7 kB]
Fetched 66.7 kB in 1s (118 kB/s)
(Reading database ... 52587 files and directories currently installed.)
Preparing to unpack .../dahdi-linux_1%3a3.3.0-5+asl_all.deb ...
Unpacking dahdi-linux (1:3.3.0-5+asl) over (1:3.3.0-5+asl) ...
Setting up dahdi-linux (1:3.3.0-5+asl) ...
root@None:~#

and

modprobe: FATAL: Module dahdi not found in directory /lib/modules/6.1.0-22-cloud-amd64
root@None:~#

I could reinstall debian 12 and do a fresh install of ASL3 looking for any errors on the way?

This is a cloud machine by the way, Ionos VPS

N8EI · July 1, 2024, 3:14pm

Sorry… my mistake. apt install --reinstall dahdi-dkms is what should force the kernel rebuild.

G4ZWH · July 1, 2024, 3:15pm

Ah ok… The plot thickens:

root@None:~# apt install --reinstall dahdi-dkms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Progress: [ 80%] [##############################################################################################################............................]
After this operation, 0 B of additional disk space will be used.
Get:1 https://repo.allstarlink.org/public bookworm/main amd64 dahdi-dkms all 1:3.3.0-5+asl [1190 kB]
Fetched 1190 kB in 1s (1111 kB/s)
(Reading database ... 52587 files and directories currently installed.)
Preparing to unpack .../dahdi-dkms_1%3a3.3.0-5+asl_all.deb ...
Deleting module dahdi-3.3.0 completely from the DKMS tree.
Unpacking dahdi-dkms (1:3.3.0-5+asl) over (1:3.3.0-5+asl) ...
Setting up dahdi-dkms (1:3.3.0-5+asl) ...
Loading new dahdi-3.3.0 DKMS files...
Building for 6.1.0-22-cloud-amd64
Module build for kernel 6.1.0-22-cloud-amd64 was skipped since the
kernel headers for this kernel do not seem to be installed.#########################################........................................................]
root@None:~#

N8EI · July 1, 2024, 3:25pm

Interesting Please provide as separate commands with separate output

uname -a
dpkg -l 'linux-headers*'

G4ZWH · July 1, 2024, 3:29pm

Thanks for your help!

First

root@None:~# uname -a
root@None:~# 1.0-22-cloud-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.94-1 (2024-06-21) x86_64 GNU/Linux

Second

root@None:~# dpkg -l 'linux-headers*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                          Version      Architecture Description
+++-=============================-============-============-=========================================================
un  linux-headers                 <none>       <none>       (no description available)
ii  linux-headers-6.1.0-22-amd64  6.1.94-1     amd64        Header files for Linux 6.1.0-22-amd64
ii  linux-headers-6.1.0-22-common 6.1.94-1     all          Common header files for Linux 6.1.0-22
un  linux-headers-686-pae         <none>       <none>       (no description available)
ii  linux-headers-amd64           6.1.94-1     amd64        Header files for Linux amd64 configuration (meta-package)
un  linux-headers-generic         <none>       <none>       (no description available)
root@None:~#

N8EI · July 1, 2024, 3:36pm

This is definitely not a standard Debian 12 Bookworm VPS installation. Note that “1.0-22-cloud-amd64” – looks like some sort of oddball customized Linux image from Ionos. Try doing this:

apt install linux-headers-$(uname -r) linux-headers-6.1.0-22-cloud-amd64

and see if anything new installs. But if they’ve stuck in a rando kernel without the corresponding headers there’s going to be problems building the kernel modules. Are you able to install with a stock Debian image?

G4ZWH · July 1, 2024, 3:46pm

Interesting, thank you!

That command started to install and then spat out another error.

I have just had a look and there is a separate debian 12 ISO which I am installing now.

I’ll see what happens!

G4ZWH · July 1, 2024, 6:08pm

Ok I rebuilt it using what I think is the stock Debian 12.

It’s now accepting incoming connections. Separate issue though, allmon3 is throwing this up:

537100 - Unavailable Node

Up: 0

Allmon3 is not responding to requests for this node. Check server logs.

Any idea where the logs are to check what’s going on? Thanks

N8EI · July 1, 2024, 6:35pm

journalctl -xeu allmon3