Please help Allmon3 is not responding to requests for this node

Allmon
1

I have installed Allstarlink version 3 ffor Debian 12 Install. after completing and entering the appropriate node in allstarlink, but in allmon a message is obtained:

Allmon3 is not responding to requests for this node.

journalctl -u allmon3.service -f

Aug 14 13:59:08 ip-172-31-43-202 allmon3[575]: ERROR: (asl_allmon.ami_conn) Logon failure msg=(Response: Error Message: Authentication failed )
Aug 14 13:59:08 ip-172-31-43-202 allmon3[575]: ERROR: (asl_allmon.allmon3_ws_status) No connection for 127.0.0.1:5038 on 16700 due to unreachable AMI - waiting 15 seconds
Aug 14 13:59:24 ip-172-31-43-202 allmon3[575]: ERROR: (asl_allmon.ami_conn) Logon failure msg=(Response: Error Message: Authentication failed )
Aug 14 13:59:24 ip-172-31-43-202 allmon3[575]: ERROR: (asl_allmon.allmon3_ws_status) No connection for 127.0.0.1:5038 on 16700 due to unreachable AMI - waiting 15 seconds
Aug 14 13:59:40 ip-172-31-43-202 allmon3[575]: ERROR: (asl_allmon.ami_conn) Logon failure msg=(Response: Error Message: Authentication failed )

please help.
Thank you

2

I too am getting same response.

Aug 14 14:24:36 racknerd-776ea46 allmon3[13528]: ERROR: (asl_allmon.ami_conn) Logon failure msg=(Response: Error Message: Authentication failed )
Aug 14 14:24:36 racknerd-776ea46 allmon3[13528]: ERROR: (asl_allmon.allmon3_ws_status) No connection for 127.0.0.1:5038 on 16700 due to unreachable AMI - waiting 15 seconds

Maybe someone can help us both.

3

The error is pretty clear. Your /etc/asterisk/manager.conf and /etc/allmon3/allmon3.ini files do not contain the same password information. What specifically did you install to reach this condition - a hand-install of Debian 12 x86_64 with packages or the ASL3 Pi Appliance or something different?

4

Hello
/etc/asterisk/manager.conf and /etc/allmon3/allmon3.ini

is the same password

allmon3.ini

[624501]
host=127.0.0.1:5038
user=admin
pass=Password2024

manager.conf

[general]
enabled = yes
;displaysystemname = yes
port = 5038
bindaddr = 127.0.0.1 ; Comment when not localhost access

[admin]

secret = Password2024
read = all,system,call,log,verbose,command,agent,user,config
write = all,system,call,log,verbose,command,agent,user,config
deny = 0.0.0.0/0.0.0.0 ; Uncomment when not localhost
permit = 127.0.0.1/255.255.255.0 ; Uncomment when not localhost

Test telnet 127.0.0.1 5038
Trying 127.0.0.1…
Connected to 127.0.0.1.
Escape character is ‘^]’.
Asterisk Call Manager/9.0.0

Response: Error
Message: Missing action in request
Response: Error
Message: Missing action in request

check log

DEBUG: (asl_allmon.allmon3_ws_status) enter node_status_main(624501)
DEBUG: (asl_allmon.ami_conn) asl_create_connection()
DEBUG: (asl_allmon.ami_conn) connect() using 127.0.0.1:5038:5038
DEBUG: (asl_allmon.node_db) entering full_update
DEBUG: (asl_allmon.node_db) entering get_allmon_db()
INFO: (asl_allmon.node_db) Retrieving database from https://allmondb.allstarlink.org/
WARNING: (asl_allmon.ami_conn) connection failed to 127.0.0.1:5038:5038: [Errno -2] Name or service not known

Aug 15 01:26:00 ip-172-31-9-58 allmon3[9850]: WARNING: (asl_allmon.ami_conn) connection failed to 127.0.0.1:5038:5038: [>
Aug 15 01:26:00 ip-172-31-9-58 allmon3[9850]: INFO: (asl_allmon.allmon3_ws_status) node: 624501 - sleeping for RETRY_INT>
Aug 15 01:26:11 ip-172-31-9-58 allmon3[9850]: INFO: (asl_allmon.allmon3_server) admin has no node restrictions
Aug 15 01:26:11 ip-172-31-9-58 allmon3[9850]: WARNING: (asl_allmon.ami_conn) connection failed to 127.0.0.1:5038:5038: [>
Aug 15 01:26:11 ip-172-31-9-58 allmon3[9850]: ERROR: (asl_allmon.ami_conn) asl_cmd_response() Exception: <class 'Attribu>
Aug 15 01:26:11 ip-172-31-9-58 allmon3[9850]: ERROR: (asl_allmon.ami_conn) asl_cmd_response() Message: ‘NoneType’ object>
Aug 15 01:26:11 ip-172-31-9-58 allmon3[9850]: ERROR: (asl_allmon.ami_parser) asl_cmd() exception <class 'asl_allmon.ami_>
Aug 15 01:26:11 ip-172-31-9-58 allmon3[9850]: ERROR: (asl_allmon.ami_parser) asl_cmd() message <class 'asl_allmon.ami_co>
Aug 15 01:26:11 ip-172-31-9-58 allmon3[9850]: ERROR: (asl_allmon.allmon3_ws_cmd) Could not connect to AMI interface 127.>
Aug 15 01:26:11 ip-172-31-9-58 allmon3[9850]: WARNING: (asl_allmon.allmon3_ws_cmd) Command was ignored
Aug 15 01:26:15 ip-172-31-9-58 allmon3[9850]: INFO: (asl_allmon.allmon3_ws_status) node: 624501 - attempting reconnectio>
Aug 15 01:26:15 ip-172-31-9-58 allmon3[9850]: WARNING: (asl_allmon.ami_conn) connection failed to 127.0.0.1:5038:5038: [>
Aug 15 01:26:15 ip-172-31-9-58 allmon3[9850]: INFO: (asl_allmon.allmon3_ws_status) node: 624501 - sleeping for RETRY_INT>
Aug 15 01:26:30 ip-172-31-9-58 allmon3[9850]: INFO: (asl_allmon.allmon3_ws_status) node: 624501 - attempting reconnectio>
Aug 15 01:26:30 ip-172-31-9-58 allmon3[9850]: WARNING: (asl_allmon.ami_conn) connection failed to 127.0.0.1:5038:5038: [>
Aug 15 01:26:30 ip-172-31-9-58 allmon3[9850]: INFO: (asl_allmon.allmon3_ws_status) node: 624501 - sleeping for RETRY_INT

Please help
Thank you

5

uname -a
Linux ip-172-31-9-58 6.1.0-23-cloud-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.99-1 (2024-07-15) x86_64 GNU/Linux

netstat -na | grep 5038
tcp 0 0 127.0.0.1:5038 0.0.0.0:* LISTEN

6

Remove the “:5038” You don’t need to specify the port, it’s auto-assumed to be TCP/5038.

7

Ok Thank you for your help

8

I have check and use command Execute Command on 624501
but result is
Command Successful

OK:
Unknown node number 624501.

what’s problem ?

9

I have check and use command Execute Command on 624501
but result is
Command Successful

OK:
Unknown node number 624501.

what’s problem ?

10

[2024-08-15 03:47:19.106] Asterisk 20.9.1+asl3-3.0.4-1.deb12 built by builder @ allstarlink.org on a x86_64 running Lin>[2024-08-15 03:47:19.132] NOTICE[412] loader.c: 69 modules will be loaded.
[2024-08-15 03:47:19.301] NOTICE[412] cdr.c: CDR simple logging enabled.
[2024-08-15 03:47:19.303] NOTICE[412] dnsmgr.c: Managed DNS entries will be refreshed every 300 seconds.
[2024-08-15 03:47:19.316] NOTICE[412] indications.c: Default country for indication tones: us
[2024-08-15 03:47:19.316] NOTICE[412] indications.c: Setting default indication country to ‘us’
[2024-08-15 03:47:19.359] NOTICE[412] res_smdi.c: No SMDI interfaces are available to listen on, not starting SMDI list>[2024-08-15 03:47:19.365] WARNING[412] chan_dahdi.c: Only FXO signalled channels may belong to a call group
[2024-08-15 03:47:19.365] WARNING[412] chan_dahdi.c: Only FXO signalled channels may belong to a pickup group
[2024-08-15 03:47:19.365] NOTICE[412] chan_dahdi.c: Ignoring any changes to ‘userbase’ (on reload) at line 23.
[2024-08-15 03:47:19.365] NOTICE[412] chan_dahdi.c: Ignoring any changes to ‘vmsecret’ (on reload) at line 31.
[2024-08-15 03:47:19.365] NOTICE[412] chan_dahdi.c: Ignoring any changes to ‘hassip’ (on reload) at line 35.
[2024-08-15 03:47:19.365] NOTICE[412] chan_dahdi.c: Ignoring any changes to ‘hasiax’ (on reload) at line 39.
[2024-08-15 03:47:19.365] NOTICE[412] chan_dahdi.c: Ignoring any changes to ‘hasmanager’ (on reload) at line 47.
[2024-08-15 03:47:19.365] WARNING[412] chan_dahdi.c: Only FXO signalled channels may belong to a call group
[2024-08-15 03:47:19.365] WARNING[412] chan_dahdi.c: Only FXO signalled channels may belong to a pickup group
[2024-08-15 03:47:19.544] WARNING[412] loader.c: Some non-required modules failed to load.
[2024-08-15 03:47:19.556] WARNING[412] loader.c: Module ‘res_adsi’ has been loaded but may be removed in a future relea>[2024-08-15 03:47:19.567] ERROR[412] loader.c: res_timing_dahdi declined to load.
[2024-08-15 03:47:19.685] NOTICE[475] app_rpt.c: Normal Repeater Init 624501
[2024-08-15 03:47:19.685] WARNING[483][C-00000001] chan_dahdi.c: Unable to open ‘/dev/dahdi/pseudo’: No such file or di>[2024-08-15 03:47:19.685] ERROR[483][C-00000001] chan_dahdi.c: Unable to dup channel: No such file or directory
[2024-08-15 03:47:19.685] ERROR[483] app_rpt/rpt_bridging.c: Failed to request dahdi/pseudo
[2024-08-15 03:47:19.685] WARNING[483] app_rpt.c: Disabled broken repeater 624501
[2024-08-15 03:52:19.669] NOTICE[456] dnsmgr.c: dnssrv: host ‘register.allstarlink.org’ changed from 34.105.111.212:443>

11

modprobe: FATAL: Module dahdi not found in directory /lib/modules/6.1.0-23-cloud-amd64

12

sudo 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.
1 not fully installed or removed.
Need to get 0 B/66.7 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database … 64239 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 linux-headers-6.1.0-23-cloud-amd64 (6.1.99-1) …
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.1.0-23-cloud-amd64.
Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Error! The /var/lib/dkms/dahdi/3.3.0/6.1.0-23-cloud-amd64/x86_64/dkms.conf for module dahdi includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config.
This indicates that it should not be built.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.1.0-23-cloud-amd64 failed!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.1.0-23-cloud-amd64.postinst line 1
1.
dpkg: error processing package linux-headers-6.1.0-23-cloud-amd64 (–configure):
installed linux-headers-6.1.0-23-cloud-amd64 package post-installation script subprocess returned error exit status 1
Setting up dahdi-linux (1:3.3.0-5+asl) …
Errors were encountered while processing:
linux-headers-6.1.0-23-cloud-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)

13

`[2024-08-15 06:01:30.674] ERROR[7040] loader.c: res_timing_dahdi declined to load.
[2024-08-15 06:01:30.799] ERROR[7090][C-00000001] chan_dahdi.c: Unable to dup channel: No such file or directory
[2024-08-15 06:01:30.799] ERROR[7090] app_rpt/rpt_bridging.c: Failed to request pseudo channel
[2024-08-15 06:02:34.371] ERROR[8929] loader.c: res_timing_dahdi declined to load.
[2024-08-15 06:02:34.556] ERROR[8978][C-00000001] chan_dahdi.c: Unable to dup channel: No such file or directory
[2024-08-15 06:02:34.556] ERROR[8978] app_rpt/rpt_bridging.c: Failed to request dahdi/pseudo
[2024-08-15 06:14:20.454] ERROR[9012] loader.c: res_timing_dahdi declined to load.
[2024-08-15 06:14:20.681] ERROR[9061][C-00000001] chan_dahdi.c: Unable to dup channel: No such file or directory
[2024-08-15 06:14:20.681] ERROR[9061] app_rpt/rpt_bridging.c: Failed to request dahdi/pseudo
[2024-08-15 06:30:29.432] ERROR[405] loader.c: res_timing_dahdi declined to load.
[2024-08-15 06:30:29.579] ERROR[462][C-00000001] chan_dahdi.c: Unable to dup channel: No such file or directory
[2024-08-15 06:30:29.579] ERROR[462] app_rpt/rpt_bridging.c: Failed to request dahdi/pseudo
[2024-08-15 06:43:16.458] ERROR[407] loader.c: res_timing_dahdi declined to load.
[2024-08-15 06:43:16.660] ERROR[475][C-00000001] chan_dahdi.c: Unable to dup channel: No such file or directory
[2024-08-15 06:43:16.660] ERROR[475] app_rpt/rpt_bridging.c: Failed to request dahdi/pseudo
[2024-08-15 06:46:32.065] ERROR[702] loader.c: res_timing_dahdi declined to load.
[2024-08-15 06:46:32.265] ERROR[749][C-00000001] chan_dahdi.c: Unable to dup channel: No such file or directory
[2024-08-15 06:46:32.265] ERROR[749] app_rpt/rpt_bridging.c: Failed to request dahdi/pseudo

14

The version of Linux being “6.1.0-23-cloud-amd64” implies you’re trying to install this in a VPS service? We’ve seen problems where the VPS service is providing a customized Debian build that doesn’t work. Please try the following although it’s unlikely to be helpful:

sudo apt install linux-headers-6.1.0-23-cloud-amd64

It also appears that you’re on a UEFI system with SecureBoot:

Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

That probably won’t work well as there’s known issues building Dahdi on Debian 12 + UEFI + SecureBoot.

15

sudo apt install linux-headers-6.1.0-23-cloud-amd64

Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
The following NEW packages will be installed:
linux-headers-6.1.0-23-cloud-amd64
0 upgraded, 1 newly installed, 0 to remove and 40 not upgraded.
Need to get 0 B/1144 kB of archives.
After this operation, 2405 kB of additional disk space will be used.
Selecting previously unselected package linux-headers-6.1.0-23-cloud-amd64.
(Reading database … 52585 files and directories currently installed.)
Preparing to unpack …/linux-headers-6.1.0-23-cloud-amd64_6.1.99-1_amd64.deb …
Unpacking linux-headers-6.1.0-23-cloud-amd64 (6.1.99-1) …
Setting up linux-headers-6.1.0-23-cloud-amd64 (6.1.99-1) …
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.1.0-23-cloud-amd64.
Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Error! The /var/lib/dkms/dahdi/3.3.0/6.1.0-23-cloud-amd64/x86_64/dkms.conf for module dahdi includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config.
This indicates that it should not be built.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.1.0-23-cloud-amd64 failed!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.1.0-23-cloud-amd64.postinst line 1
1.
dpkg: error processing package linux-headers-6.1.0-23-cloud-amd64 (–configure):
installed linux-headers-6.1.0-23-cloud-amd64 package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
linux-headers-6.1.0-23-cloud-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)

16

Is this a VPS? Did you choose “6.1.0-12-cloud-amd64” as the kernel? Can you use normal Debian 12?

17

Yes this is VPS, and how build normal Debian 12 install for VPS ?

18

You’d have to talk to your VPS provider. Presumably you’d have to do a “custom install” of some sort using standard Debian 12 media.