HI,
This afternoon, I went to our local repeater to make a Raspberry reset, as the node was not answering anymore.
After the reboot, the node worked normalIy and I've made an update/upgrade which went all OK.
But since, I do have the following error showing up for which I don't have any clue on what to do to resolve it.
Any help is welcome.
Thanks,
Connected to Asterisk 22.9.0+asl3-3.9.3-1.deb12 currently running on tk5zcg (pid = 764)
[2026-06-27 19:32:23.199] DEBUG[830]: channel.c:4797 ast_sendtext_data: Thread LWP 830 is blocking 'IAX2/89.234.155.3:4569-6634', already blocked by thread LWP 842 in procedure ast_waitfor_nandfds
[2026-06-27 19:32:53.199] DEBUG[830]: channel.c:4797 ast_sendtext_data: Thread LWP 830 is blocking 'IAX2/89.234.155.3:4569-6634', already blocked by thread LWP 842 in procedure ast_waitfor_nandfds
[2026-06-27 19:33:23.199] DEBUG[830]: channel.c:4797 ast_sendtext_data: Thread LWP 830 is blocking 'IAX2/89.234.155.3:4569-6634', already blocked by thread LWP 842 in procedure ast_waitfor_nandfds
[2026-06-27 19:33:53.199] DEBUG[830]: channel.c:4797 ast_sendtext_data: Thread LWP 830 is blocking 'IAX2/89.234.155.3:4569-6634', already blocked by thread LWP 842 in procedure ast_waitfor_nandfds
[2026-06-27 19:34:23.199] DEBUG[830]: channel.c:4797 ast_sendtext_data: Thread LWP 830 is blocking 'IAX2/89.234.155.3:4569-6634', already blocked by thread LWP 842 in procedure ast_waitfor_nandfds
[2026-06-27 19:34:53.199] DEBUG[830]: channel.c:4797 ast_sendtext_data: Thread LWP 830 is blocking 'IAX2/89.234.155.3:4569-6634', already blocked by thread LWP 842 in procedure ast_waitfor_nandfds
So it basically means for some reason...something did not release a lock on a channel when it was supposed to. This can be caused by a network hiccup, getting stuck waiting on I/O...but either way, asterisk is supposed to do something with that channel but can't because something has it locked.
Usually just rebooting Asterisk will clear all of this out. Someone else had this same error popup, but it looked like it could have been something else they were doing cause this.
HI,
Thanks for the answer, but unfortunately a reboot that I did before this post did not help.
The error shows up exactly every 30s, that can probably help to track down my problem?
My log at bootup:
[2026-06-28 07:54:18.171] Asterisk 22.9.0+asl3-3.9.3-1.deb12 built by builder @ allstarlink.org on a aarch64 running Linux on 2026-05-28 19:06:15 UTC
[2026-06-28 07:54:18.326] NOTICE[767] loader.c: 72 modules will be loaded.
[2026-06-28 07:54:18.924] NOTICE[767] cdr.c: CDR simple logging enabled.
[2026-06-28 07:54:18.933] NOTICE[767] dnsmgr.c: Managed DNS entries will be refreshed every 300 seconds.
[2026-06-28 07:54:18.990] NOTICE[767] indications.c: Default country for indication tones: us
[2026-06-28 07:54:18.990] NOTICE[767] indications.c: Setting default indication country to 'us'
[2026-06-28 07:54:19.217] NOTICE[767] res_smdi.c: No SMDI interfaces are available to listen on, not starting SMDI listener.
[2026-06-28 07:54:19.544] NOTICE[767] ./xpmr/xpmr.c: xpmr rxlpf: 1
[2026-06-28 07:54:19.544] NOTICE[767] ./xpmr/xpmr.c: xpmr rxhpf: 0
[2026-06-28 07:54:19.544] NOTICE[767] ./xpmr/xpmr.c: xpmr txlpf: 1
[2026-06-28 07:54:19.544] NOTICE[767] ./xpmr/xpmr.c: xpmr txhpf: 0
[2026-06-28 07:54:19.639] WARNING[767] loader.c: Module 'res_adsi' has been loaded but may be removed in a future release.
[2026-06-28 07:54:19.759] WARNING[790] pbx_config.c: users.conf is deprecated and will be removed in a future version of Asterisk
[2026-06-28 07:54:19.822] NOTICE[830] app_rpt.c: Domain used for DNS node lookup is: nodes.allstarlink.org
[2026-06-28 07:54:19.824] NOTICE[830] app_rpt.c: Normal Repeater Init 1003
[2026-06-28 07:54:19.832] NOTICE[836] chan_usbradio.c: Channel 1003: Set option TONE VERIFY, mode: OFF(0).
[2026-06-28 07:54:22.216] DEBUG[836] channel.c: Thread LWP 836 is blocking 'IAX2/89.234.155.3:4569-15059', already blocked by thread LWP 848 in procedure ast_waitfor_nandfds
[2026-06-28 07:54:53.633] WARNING[822] chan_iax2.c: Resyncing the jb. last_delay -28, this delay 17087, threshold 500, new offset -17087
[2026-06-28 07:55:09.021] DEBUG[836] channel.c: Thread LWP 836 is blocking 'IAX2/89.234.155.3:4569-15059', already blocked by thread LWP 848 in procedure ast_waitfor_nandfds
[2026-06-28 07:55:39.019] DEBUG[836] channel.c: Thread LWP 836 is blocking 'IAX2/89.234.155.3:4569-15059', already blocked by thread LWP 848 in procedure ast_waitfor_nandfds
[2026-06-28 07:56:09.021] DEBUG[836] channel.c: Thread LWP 836 is blocking 'IAX2/89.234.155.3:4569-15059', already blocked by thread LWP 848 in procedure ast_waitfor_nandfds
[2026-06-28 07:56:39.021] DEBUG[836] channel.c: Thread LWP 836 is blocking 'IAX2/89.234.155.3:4569-15059', already blocked by thread LWP 848 in procedure ast_waitfor_nandfds
[2026-06-28 07:57:09.021] DEBUG[836] channel.c: Thread LWP 836 is blocking 'IAX2/89.234.155.3:4569-15059', already blocked by thread LWP 848 in procedure ast_waitfor_nandfds
No. All this tells me is there must be some issue with the upgrades. Someone else mentioned having the exact same error after an upgrade...but they were having other issues and it wasn't clear if it was even related. I'm not a dev...so I don't know the inner details. That particular node is having an issue maybe?
Something is causing a state to go wonky or cause a deadlock in Asterisk.
I did a fresh install of ASL3 coming from hamvoip; so I can't reproduce this on my end.
I'm not a Linux specialist, but I didn't notice anything wrong when using dmesg.
The node seems to work perfectly, apart some echolink frames loss when an Echolink connection is open.