Guest

Preview Tool

Cisco Bug: CSCur31777 - AIM stuck due to communication failure b/w AIM and AVSDB

Last Modified

Jun 21, 2020

Products (4)

  • Cisco Videoscape Distribution Suite for Television
  • Cisco TV Streamer Application
  • Cisco Visual Quality Experience (VQE) Channel Provisioning Tools
  • Cisco Visual Quality Experience Application

Known Affected Releases

3.5(1) 3.5(1)ES1

Description (partial)

Symptom:
AIM fails to get DB trigger and corresponding publishing will fail

Conditions:
Incase of any communication failures between aim and avsdb, the connection is not cleaned up by aim process and indefinitely querying on the old connection. Any new trigger from DB will try to send with a new connection but AIM is not listening to that. This resulted in no more communication between DB and AIM.

This is a defect and need to be fixed by handling the connections properly during failure scenarios.

Logs snippet:

avsdb.log.20141010-060004:2014-10-10 05:00:30.023925 UTC mxvault-01 setsockopt TIMEOUT timeout.tv_sec = 15 timeout.tv_usec = 0


Here are the possible scenarios which can trigger this failure
1.	If there is any communication failure (like AIM threads might be busy with processing request) between AVSDB and AIM.
2.	If AVSDB is restarted, then, there is a chance to hit this issue

Repro : Very difficult to reproduce this issue in the normal scenario. So simulated this issue by instrumenting the failures in AVSDB trigger



[Wrap text]  [Edit this enclosure] 
Description: Modified 10/24/2014 09:15:51 by cdsbuild 
Incase of any communication failures between aim and avsdb, the connection is not cleaned up by aim process and indefinitely querying on the old connection. Any new trigger from DB will try to send with a new connection but AIM is not listening to that. This resulted in no more communication between DB and AIM.

This is a defect and need to be fixed by handling the connections properly during failure scenarios.

Logs snippet:

avsdb.log.20141010-060004:2014-10-10 05:00:30.023925 UTC mxvault-01 setsockopt TIMEOUT timeout.tv_sec = 15 timeout.tv_usec = 0


Here are the possible scenarios which can trigger this failure
1.	If there is any communication failure (like AIM threads might be busy with processing request) between AVSDB and AIM.
2.	If AVSDB is restarted, then, there is a chance to hit this issue

Repro : Very difficult to reproduce this issue in the normal scenario. So simulated this issue by instrumenting the failures in AVSDB trigger

[Unwrap text]  [Edit this enclosure] 
Description: Modified 10/24/2014 09:15:51 by cdsbuild 
Incase of any communication failures between aim and avsdb, the connection is not cleaned up by aim process and indefinitely querying on the old connection. Any new trigger from DB will try to send with a new connection but AIM is not listening to that. This resulted in no more communication between DB and AIM.

This is a defect and need to be fixed by handling the connections properly during failure scenarios.

Logs snippet:

avsdb.log.20141010-060004:2014-10-10 05:00:30.023925 UTC mxvault-01 setsockopt TIMEOUT timeout.tv_sec = 15 timeout.tv_usec = 0


Here are the possible scenarios which can trigger this failure
1.	If there is any communication failure (like AIM threads might be busy with processing request) between AVSDB and AIM.
2.	If AVSDB is restarted, then, there is a chance to hit this issue

Repro : Very difficult to reproduce this issue in the normal scenario. So simulated this issue by instrumenting the failures in AVSDB trigger

[Unwrap text]  [Edit this enclosure] 
R-comments: Added 10/24/2014 06:28:56 by kjeevana 





[Wrap text]  [Edit this enclosure] 
R-comments: Added 10/24/2014 06:28:56 by kjeevana 
[Unwrap text]  [Edit this enclosure] 
R-comments: Added 10/24/2014 06:28:56 by kjeevana
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.