Several CLI errors

[spinto]

The Asterisk service stopped today for some reason. Had to restart it manually.

I’m receiving several CLI errors, mostly with span 1. This was on a server that VICIdial had initially setup.

Do you know of any patches that would resolve the below issue? Will updating to 1.4 fix the issue?

We’re currently using: 1.2.30.2

CLI Output:

Aug 4 14:09:56 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x8283670', 9 retries!
Aug 4 14:09:59 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x82145a8', 9 retries!
Aug 4 14:10:00 NOTICE[3735]: chan_zap.c:8365 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1
Aug 4 14:10:00 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x820aba8', 9 retries!
Aug 4 14:10:00 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x8264258', 9 retries!
Aug 4 14:10:01 WARNING[17618]: file.c:517 ast_openstream_full: File videoprof does not exist in any format
Aug 4 14:10:02 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x827ad60', 9 retries!
Aug 4 14:10:02 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x827ad60', 9 retries!
Aug 4 14:10:02 WARNING[17636]: file.c:1045 ast_waitstream: Unexpected control subclass '-1'
Aug 4 14:10:02 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x8240808', 9 retries!
Aug 4 14:10:02 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x8240808', 9 retries!
Aug 4 14:10:03 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x827a318', 9 retries!
Aug 4 14:10:03 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x828aa80', 9 retries!
Aug 4 14:10:07 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x825d680', 9 retries!
Aug 4 14:10:07 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x825d680', 9 retries!
Aug 4 14:10:07 WARNING[17709]: file.c:1045 ast_waitstream: Unexpected control subclass '-1'
Aug 4 14:10:09 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x8280a90', 9 retries!
Aug 4 14:10:09 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x81f1c78', 9 retries!
Aug 4 14:10:12 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x81f3cf0', 9 retries!
Aug 4 14:10:12 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x8283670', 9 retries!
Aug 4 14:10:12 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x81f3cf0', 9 retries!
Aug 4 14:10:12 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x8283670', 9 retries!
Aug 4 14:10:14 WARNING[6498]: channel.c:2290 ast_write: Thread -1242928240 Blocking 'Zap/3-1', already blocked by thread -1240798320 in procedure ast_waitfor_nandfds
Aug 4 14:10:17 NOTICE[3735]: chan_zap.c:8365 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1
Aug 4 14:10:19 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x8216ac8', 9 retries!
Aug 4 14:10:22 NOTICE[3735]: chan_zap.c:8365 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1
Aug 4 14:10:22 NOTICE[17906]: app_meetme.c:2210 admin_exec: Conference Number not found
Aug 4 14:10:25 NOTICE[3735]: chan_zap.c:8365 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
Aug 4 14:10:26 WARNING[17916]: channel.c:2290 ast_write: Thread -1232880752 Blocking 'Zap/74-1', already blocked by thread -1240265840 in procedure ast_waitfor_nandfds
Aug 4 14:10:28 WARNING[17977]: chan_zap.c:7814 zt_request: Unknown option '-' in '62-1'
Aug 4 14:10:30 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x826fdc8', 9 retries!
Aug 4 14:10:32 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x82a1f20', 9 retries!
Aug 4 14:10:32 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x82be360', 9 retries!
Aug 4 14:10:32 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x822f680', 9 retries!
Aug 4 14:10:33 NOTICE[3735]: chan_zap.c:8365 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1
Aug 4 14:10:37 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x825d270', 9 retries!
Aug 4 14:10:37 WARNING[18119]: file.c:1045 ast_waitstream: Unexpected control subclass '-1'
Aug 4 14:10:38 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x8206e60', 9 retries!
Aug 4 14:10:38 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x825d270', 9 retries!
Aug 4 14:10:38 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x8206e60', 9 retries!
Aug 4 14:10:38 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x825d270', 9 retries!
Aug 4 14:10:48 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x81f1c78', 9 retries!
Aug 4 14:10:48 WARNING[3729]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x81f1c78', 9 retries!

[mflorell]

What kind of T1 card are you using?

Avoided initial deadlock warnings aren't necessarily bad, they can occur on a properly functioning system.

HDLC Bad FCS are bad news.

[spinto]

Here's the lspci (Digium):

Communication controller: Xilinx Corporation Wildcard TE405P/TE410P (1st Gen) (rev 01)

[lerroux]

i also get the deadlock warnings all the time. but my system is working.

[mflorell]

Wow, rev 01. That means it's probably around 4 years old and out of warranty from Digium.

Is there any way you could try another card or a separate testing rig to ensure that it is not an issue with your hardware?

If not, first try switching ports and see if the issue continues, then see if you can get the carrier to put monitoring on the circuit(and make sure they monitor PRI data too!).

[spinto]

The errors have gone away since putting in a new Sangoma

[gardo]

I just love Sangoma cards. Because it should work!