Allmon, Supermon not connecting to ASL

AllStarLink
,
1

Setup Information

Connecting Node: 62499
Package Version

allmon3 1.5.1-1.deb12
asl3 3.8-1.deb

Problem Node: 626790
allmon3 1.5.1-1.deb12
asl3 3.8-1.deb

Inquiry

Since the multiple updates this week:

I am unable to connect to Asterisk on the Problem Node. Using Allmon local to 626790, I couldn't log in (changed the username/password on Allmon), that issue resolved.. The Nodes do show, but each says: "Allmon3 is not responding to requests for this node. Check server logs."

From 626790 Message.log

025-07-02 07:02:37.847] NOTICE[58675] manager.c: 127.0.0.1 tried to authenticate with nonexistent user 'admin'
[2025-07-02 07:02:37.848] NOTICE[58675] manager.c: 127.0.0.1 failed to authenticate as 'admin'

I double-checked the secret, they are all the same, /etc/allmon/allmon.ini, /etc/asterisk/allmon3.ini.php, manager.conf

I assume, when I fix this issue, my issue of connecting from Supermon on 62649 will resolve itself.

NOTE: 626790 does connect to 626499 via CL.

Any hints on what else to check?

2

That error is telling you that on the Asterisk side, there is no user named admin created - it's "nonexistent". That means that your manager.conf file is incorrect. It should look pretty much something like this:

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

[admin]
secret = >>SOMETHING SECRET<<
read = all,system,call,log,verbose,command,agent,user,config
write = all,system,call,log,verbose,command,agent,user,config
3

This is what it shows:

; Asterisk Call Management support
;

; By default asterisk will listen on localhost only.
[general]
enabled = yes
port = 5038
;bindaddr = 127.0.0.1 ; Comment when not localhost access
bindaddr = 0.0.0.0

[admin]
secret = my password
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=1.2.3.4/255.255.255.255 ; Uncomment when not localhost
permit=96.224.250.24, 100.77.7.64 ;SBANETWEB

4

What host are you using to access the manager [AMI] interface? I hope that it's one of these IP addresses.

and you can check if this is your issue by commenting out that line (and restarting asterisk).

5

Done as requested, no change.

BTW, it was like that for months and worked...

Thanks for the help!

6

I don't believe you can have two IP ranges on the same line. Try:

deny = 0.0.0.0/0.0.0.0
permit=96.224.250.24/255.255.255.255
permit=100.77.7.64/255.255.255.255
7

That solved 1 issue:

Allmon3 on 626790 no longer shows the errors, however, it also doesn't show that it is logged into 62499.

On 62499 I show Supermon , will not log into 626790, however it does show that 626790 is connected to 62499.

“Curiouser and curiouser!” Cried Alice (she was so much surprised, that for the moment she quite forgot how to speak good English).”

8

The correct format for doing this on a single line is:

permit=192.168.1.105/255.255.255.0&45.75.102.63.0/255.255.255.0

9

It's more concise, but didn't solve the issue.

BTW, connection to my own ASL via Supermon has really slowed down since the update... Not sure if anyone else notice... I made no changes....

10

Are you still getting the same error about a non-existent user?

11

From the log on 626790:


[2025-07-04 06:17:57.476] NOTICE[65719] manager.c: 127.0.0.1 failed to authenticate as 'admin'
[2025-07-04 06:18:13.503] NOTICE[65723] manager.c: 127.0.0.1 tried to authenticate with nonexistent user 'admin'
[2025-07-04 06:18:13.503] NOTICE[65723] manager.c: 127.0.0.1 failed to authenticate as 'admin'
[2025-07-04 06:18:13.505] NOTICE[65724] manager.c: 127.0.0.1 tried to authenticate with nonexistent user 'admin'
[2025-07-04 06:18:13.505] NOTICE[65724] manager.c: 127.0.0.1 failed to authenticate as 'admin'
[2025-07-04 06:18:13.507] NOTICE[65725] manager.c: 127.0.0.1 tried to authenticate with nonexistent user 'admin'
[2025-07-04 06:18:13.507] NOTICE[65725] manager.c: 127.0.0.1 failed to authenticate as 'admin'
[2025-07-04 06:18:29.543] NOTICE[65726] manager.c: 127.0.0.1 tried to authenticate with nonexistent user 'admin'
[2025-07-04 06:18:29.543] NOTICE[65726] manager.c: 127.0.0.1 failed to authenticate as 'admin'
[2025-07-04 06:18:29.545] NOTICE[65727] manager.c: 127.0.0.1 tried to authenticate with nonexistent user 'admin'
[2025-07-04 06:18:29.545] NOTICE[65727] manager.c: 127.0.0.1 failed to authenticate as 'admin'
[2025-07-04 06:18:29.547] NOTICE[65728] manager.c: 127.0.0.1 tried to authenticate with nonexistent user 'admin'
[2025-07-04 06:18:29.547] NOTICE[65728] manager.c: 127.0.0.1 failed to authenticate as 'admin'
12

Was not intended to solve anything, just point out proper usage, and that it is was within asterisk educate to be clear, since that seem to be in question..

13

Thank you @Mike

Any ideas what might have changed in the update to cause this?

Also, the connection time of Supermon to 62499 has gone from "instantaneous" to slow, with these updates... if that's a hint to the issue...

14

Well, no. And it has not been shown to be the result of an update, not saying it wasn't. Don't assume that. Causes you to limit your exploration for cause.
I have been waiting for information to surface that might lead the way since nobody likes to directly answer questions anymore.
But a slow response is likely when it is not getting info expected. It's likely 'retrying'.

Sorry, I don't use supermon to be any better guide here.
But you might tap the supermon user group at groips.io

15

Thanks

The only change to the system was the update, it's been running rock solid for several months now.

And, yes, I did reach out to the Supermon group, yesterday, no response as of yet.

16

You're still having the same issue: Asterisk does not believe that the user 'admin' you're trying auth with exists or is valid. This is almost assuredly some sort of configuration hiccup in /etc/asterisk/manager.conf. A software update would not cause this unless you were using some sort of syntax that is no longer valid with upstream Asterisk if your package upgrade just want from 20 to 22 but I don't recall any such deprecation being in Asterisk between those two versions.

17

Thanks for responding...

You saw my manager.conf.

I'll change the PW and see if that works..

18

These aren't on the local system are they, since you're blocking 127.0.0.1?

19

Oh, yeah, it's flagging the localhost connection. You need a permit=127.0.0.1 statement.

20

Tried adding 127.0.0.1/255.255.255.0&

No success