K2CB
April 27, 2026, 2:36am
1
Since the last update, I am getting nonstop WARNING messages in the CLI -
[2026-04-26 20:18:10.592] WARNING[2434096][C-0000051f]: channel.c:1117 __ast_queue_frame: Exceptionally long voice queue length (97 voice / 99 total) queuing to Announcer/IAXLink-00006e90;1
Not sure exactly what this is telling me. Any suggestions?
Eric
K2CB
N8EI
April 27, 2026, 1:11pm
2
Might be related this spurious bug we see sometimes:
opened 03:08AM - 20 Apr 24 UTC
app_rpt
Found Allmon attempting to connect to a regularly connected node. `asterisk -r` … would immediately return system prompt.
Attached messages.log and coredump --running.
[iTerm2 Session Apr 19, 2024 at 8:53:34 PM.txt](https://github.com/AllStarLink/app_rpt/files/15046731/iTerm2.Session.Apr.19.2024.at.8.53.34.PM.txt)
[core-asterisk-running-2024-04-20T02-50-36Z-full.txt](https://github.com/AllStarLink/app_rpt/files/15046733/core-asterisk-running-2024-04-20T02-50-36Z-full.txt)
Does it go away if you restart Asterisk?
N8EI
April 27, 2026, 1:22pm
3
Or do you have a link perpetually trying to connect but failing?
K2CB
April 28, 2026, 12:08am
4
Yes, it goes away for a little while after a restart. Then starts up again.
I did have one node in the allmon3.ini that is temporarily OOS. I just REM'ed it out in the ini file, and restarted again. I'll check it again in a little while.
Eric
K2CB
K2CB
April 28, 2026, 2:41am
5
Looks like the fix was REM'ing out the OOS node in allmon3.ini.
Thanks for the guidance.
Eric
K2CB
N8RAW
April 28, 2026, 12:01pm
6
This is a bug that we need to figure out. Trying to connect to a dead should not result in a long voice queue. Is this an external "connect" method? (Not a rpt.conf startup macro?)