More Echolink Parsing Errors? #261
Comments
|
I joined my node with echo and the table disappeared in allmon3 just now. There is one other node connected that is not echo. Getting this error in allmon3 debug log: EBUG: (asl_allmon.ami_conn) response >> Response: Error Message: Command output follows Output: Error: Entry for 871450 not found! Output: Command 'echolink dbget nodename 871450' failed. In the allstarlink.org nodelist, echo node number is 3871450. |
|
For everyone's reference, the magic happens here: /usr/lib/python3/dist-packages/asl_allmon/ami_parser/init.py starting around line 140 |
|
Interesting. Can you run |
|
Connected to Asterisk 20.10.0+asl3-3.1.0-1.deb12 currently running on allstar-3 (pid = 104723) |
|
My correct nodenumber fails as well: allstar-3CLI> echolink dbget nodename 302884 |
|
How long was node 302884 logged in before you asked for that? It does take the Echolink DB awhile to propagate. |
|
I feel like I previously heard this is fine, but I get this in the CLI when echo connects: [2024-12-17 09:43:12.070] WARNING[139183][C-00000013]: func_channel.c:574 func_channel_read: Unknown or unavailable item requested: 'peerip' I probably wasn't logged in to echo when I tried earlier. Just logged in and tried again, it's been 8 minutes and still failing, but if I lookup the echo node hosted on the allstar node I'm logging into, that does work: allstar-3CLI> echolink dbget nodename 302884 |
|
After I connected again, it picked up another node number DEBUG: (asl_allmon.ami_conn) response >> Response: Error Message: Command output follows Output: Error: Entry for 101425 not found! Output: Command 'echolink dbget nodename 101425' failed. |
|
Lookup fails |
|
Can you provide more of the output around that debug message? The code should be setting "No database information". Do you have a line that says "Invalid response about echolink...". |
|
DEBUG: (asl_allmon.ami_conn) command >> ACTION: RptStatus COMMAND: XStat NODE: 49520 ActionID: b8d629ef-8ea4-4996-a0d4-5a8cd54772be |
|
I'm guessing this is happening instead of the invalid response: ERROR: (asl_allmon.allmon3_ws_status) ERROR: list index out of range |
|
I'm slightly confused why you're seeing that. I may need to setup some time for you to connect to a test node on my system to see what's really going on. Can you try something? In # Connections of 3nnnnnn are Echolink
elif re.match(r'^3[0-9]{6}$', nname):
ename = await self.get_echolink_name(nname)
node_conns[nname]["DESC"] = enameAfter commenting that out, t ry to run it in debug mode again. |
|
I'm also having the same "list index out of range" error on Allmon3 version 1.4.1 After commenting out those 3 lines the connection list loads but all the echolink connections show as "Private or Unavailable". One of the two echolink nodes fails a lookup with the echolink dbget command in asterisks CLI. |
|
Looks like the same here, allmon3 working with wrong node number in the UI after commenting the echo lookup |
|
But are the Echolink IDs accurate (other than the leading 3)? |
|
Negative. The screenshot above is showing the 3rd node number I've received since yesterday's testing. And none of them have looked up successfully, with or without the 3. Neither does my correct echo node number, with or without 3. |
|
Can you be more specific? Are you saying that Asterisk is reporting random IDs for your Echolink connection? What is your expected Echolink ID? When connected with Echolink, paste in the output of |
|
I believe I get a random echo node number each time I disconnect and reconnect. Same as I described at the beginning of this thread. And other echo users seem to get random node numbers the same way. My echo node number per the echo website and my own records is 302884. In the output below, I"m the 3166094 node: allstar-3*CLI> rpt nodes 49520 ************************* CONNECTED NODES ************************* T3166094, T47922 allstar-3*CLI> rpt xnode 49520 T3166094, T47922 RPT_NUMLINKS=2 parrot_ena=0 allstar-3*CLI> |
|
I disconnected and reconnected and it's a different number: allstar-3*CLI> rpt nodes 49520 ************************* CONNECTED NODES ************************* T3263216, T47922 allstar-3*CLI> rpt xnode 49520 T3263216, T47922 RPT_NUMLINKS=2 parrot_ena=0 allstar-3*CLI> |
|
That's very interesting.... So there is an Allmon3 problem in that something is still choking on "node not found" errors from the Echolink database. But another issue Allmon3 can't solve is Echolink sending in randomized IDs. |
|
I'm able to join another node, 45933 and the node number is correct in the allstarlink.org nodelist. That node is hamvoip. |
|
Can you try joining N8EI-R node 2116 with Echolink so I can capture a debug output? |
|
|
Callsign is correct at least :), wroing IP and node |
|
Is your Echolink client using an Echolink proxy? That's normally the default config. |
|
Oh yes of course, I'm on android and using the defaults. |
|
Looks like 'Relay' is the default setting on android, just connected via Public Proxy and it's the right node number in the allstarlink.org nodelist. Choices are: |
|
That would explain why some people can connect fine and others it causes the issue. |
|
To confirm HamVOIP isn't a fluke can you connect to node 43211 and check your name on https://hub.w8wky.org? |
|
Sorry, that's W8WKY-R in Echolink terms... |
|
Can only connect via Relay it seems, and everything looks correct there. Update, worked on Public Proxy 2nd try |
|
I uncommented the lines mentioned around 174 and allmon3 loads fine, when there is no Relay connection. |
|
Will please try this code: https://raw.githubusercontent.com/AllStarLink/Allmon3/refs/heads/fix_261/src/asl_allmon/ami_parser/__init__.py as a replacement for |
|
Node number correct, with the leading 3, no database info for descrip |
|
Hmm, it did an apt upgrade, I guess I wasn't on the latest before, I re-replaced the init.py, but echo nodes are random again. root@allstar-3:/usr/lib/python3/dist-packages/asl_allmon/ami_parser# asl-show-version OS : Debian GNU/Linux 12 (bookworm) Asterisk : 20.10.0+asl3-3.1.0-1.deb12 Installed ASL packages : Package Version |
|
The nodes will still be random. This would only fix the display not working at all. Now the random nodes may be "no info" or be the wrong callsign. That's a different issue. |
|
Commite 3190845 is an incomplete fix |
https://community.allstarlink.org/t/echolink-node-numbers-not-displaying-correctly/22252/15
The text was updated successfully, but these errors were encountered: