[CAMI-2] cami.c: Parser occasionally gets desynced

← All Issues || New Issue →

Sort Normal || Priority

Details

As evidenced by frequent intermittent LBBS test failures of the TAP/IXO paging tests, CAMI frequently barfs and doesn't parse responses correctly:

[2026-04-27 12:34:27.651] VERBOSE[94269] manager.c: Manager 'amiuser' logged on from 127.0.0.1
1777293267:552 : 1104 : *** Initialized Asterisk Manager Interface: Asterisk Call Manager/11.0.0
1777293267:640 : 847 : ==> AMI Action:
Action:Login
ActionID:1
Username:amiuser
Secret:amipass

1777293269:115 : 350 : Next chunk: Response: Success
 ...
1777293269:117 : 1269 : WARNING: Didn't receive any AMI response (for 1) within 1000 ms?
1777293269:122 : 354 : Got start of response... (Response: Success
ActionID: 1
Message: Authentication accepted

)
1777293269:124 : 360 : Finished eventless response
1777293269:124 : 375 : Starts response: 0, middle of response: 0, ends response: 1
1777293269:131 : 387 : Response has been finalized
1777293269:132 : 1124 : <== AMI Response: Response: Success
ActionID: 1
...
1777293269:137 : 1221 : ERROR: BUG! current_response was 0x53e67d0 (1) immediately after lock acquired?
1777293269:138 : 350 : Next chunk: Event: FullyBooted ...
1777293269:138 : 375 : Starts response: 0, middle of response: 0, ends response: 0
1777293269:139 : 382 : Dispatching lone (unsolicited) event (Event: FullyBooted ...)
1777293269:139 : 1234 : <== AMI Event: Event: FullyBooted
Privilege: system,all
Uptime: 2
LastReload: 2
Status: Fully Booted

1777293269:462 : 1323 : ERROR: Requested AMI action but not yet logged in?
1777293269:463 : 1495 : No response to AMI action
[2026-04-27 12:34:44.469]   DEBUG[94273]: node.c:659 node_shutdown: Beginning shut down of node 2

Rerunning the test often results in a pass, so this reproduces only sometimes.

Comments

You must be logged in to leave a comment.