When an echo link station is connected Allmon 1.3.5 will display zero connections on my node as soon as the echo link station disconnects the display goes back to normal (2 connections)
I noticed that, but caused by you logging into Echolink with same ID twice. Thats not allowed via Echolink rules.
I was not logged in to echolink.
The allmon3 display was correct (connected to 2 nodes) then when our net started a couple of stations connected via echolink my node would show zero connects and stop automatically updating the screen (timers would freeze)
Were there any errors in /var/log/syslog or journalctl -xeu allmon3.service?
Any update on this issue?
That error means it’s getting bad data back from the AMI socket on Asterisk. I’m not immediately able to reproduce the issue. You may find something if you stop the allmon3 service and run it by hand with the --debug flag. Might give you the event that leads up to that error.
Hi, this is error from allmon3 --debug (my echolink node ID 66366)
DEBUG: (asl_allmon.ami_conn) command >> ACTION: COMMAND COMMAND: echolink dbget nodename 066366 ActionID: bcb3741d-2e46-4820-ac9d-caea3632143f
DEBUG: (asl_allmon.ami_conn) response >> Response: Error Message: Command output follows Output: Error: Entry for 066366 not found! Output: Command ‘echolink dbget nodename 066366’ failed.
DEBUG: (asl_allmon.ami_parser) exiting get_echolink_name(066366)
ERROR: (asl_allmon.allmon3_ws_status) ERROR: list index out of range
I think the first point in looking at this is to see what asl3 is showing.
It may not be a allmon thing at all.
cli>
rpt nodes <node#>
And yes, if you try to log-in to EL from two stations even of different ID’s on the same IP,
strange results may happen. It is forbidden. But it sometimes seemingly allows it to happen with the strange results.
Happens more often when your phone is on, connecting automatically to your wifi and your server behind the same NAT has one as well. Your phone apps are allowed to run in the background by default. So you might not be actively using it for it to be an issue.
Also know that when a relay or proxy is used in the EL connection, sometimes they are in error with callsign data which can trigger an error in the management software if it is not trapped out.
I will run the rpt nodes <node#> command during our next Sunday night Net and see what I find. I am having the same issue. I even installed allmon3 on a separate box from the asl nodes in hopes of getting it working.