Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

VCS Control: Application failed: An unexpected software error was detected in app[10827]: SIGABRT (tkill(2) or tgkill(2))

We have a VCS Control running 7.0.1, it reboots when the message appears. Never seen this error before.

Mar 10 15:58:32

app[16498]: Event="Application Failed" Thread-ID="16525" Version="X7.0.1" Build="266732" UTCTime="2014-03-10 19:58:32.296662"

Mar 10 15:57:56

crashreporter: Level="INFO" Event="Alarm Raised" Id="15011" UUID="28e9758c-af74-11df-bc7c-377aec3ad232" Severity="error" Detail="Application failed: An unexpected software error was detected in app[15724]: SIGABRT (tkill(2) or tgkill(2))" UTCTime="2014-03-10 19:57:56,887"

Mar 10 15:57:50

app[16060]: Event="Application Failed" Thread-ID="16078" Version="X7.0.1" Build="266732" UTCTime="2014-03-10 19:57:50.354272"

6 REPLIES
Cisco Employee

Hello aaronmwu1, Could you

Hello aaronmwu1,

 

Could you please confirm your VCS incident report?

VCS WebUI: Maintenance > Diagnostics > Incident reporting > View

 

If there's the log message "SipParams_setParam ppcmains/sipmsg/sipparams.cpp:425" on Stack section, you hitted a known software issue CSCuh41614.

https://tools.cisco.com/bugsearch/bug/CSCuh41614/

If yes, the problem is fixed in latest VCS software version X8.1.

 

Regards,

Yusuke

New Member

Thanks Yusuke,I have

Thanks Yusuke,

I have something different in the stack trace:

0x0000000000928241 SrtpMasterKeyParams ppcmains/rtp/srtp/SrtpMasterKeyParams.cpp:17
0x00007f91b1b7d02e (InstructionPointer)
0x00007f91b1eb4320 (__builtin_return_address(0))
 
Cisco Employee

Yeah.  This bug is fixed in

Yeah.  This bug is fixed in X7.1.

CSCua16714

VCS fails when presented with AES 256k Key for Traversal call.  If your experiencing this now, did you just upgrade to MOVI 4.7?  Customers running prior to X7.1 which upgraded MOVI are experiencing this now. 

Best to upgrade to at least 7.1

Hope this helps. 

VR

Patrick

New Member

Yes we did upgrade 3 MOVI

Yes we did upgrade 3 MOVI users to 4.7 and found out that it causes the application failure and reboots the VCS.  Thanks Patrick.

New Member

Patrick, One last thing to

Patrick,

 

One last thing to verify.  We are planning to upgrade the VCS to 7.2.1 to match the VCS-E.  We are still on TMS 13.1.2 and upgrading the VCS to 7.2.1 which uses the TMS Provisioning Extension.  We use Movi and  I believe 7.2.1 still supports the TMS agent legacy?  Will there be any negative affects if we stay on TMS 13.1.2 and upgrade to 7.2.1?

If I remember correctly, I would need to uncheck the "Enable TMS Agent Data Replication" option in VCS page in TMS then proceed with the upgrade?

 

Thanks,

 

Aaron

Cisco Employee

Hi Aaron.  I do believe so

Hi Aaron.  I do believe so yes.  X7.2.1 still supports Agent Legacy.  X8.1 and onwards does not. 

The cluster creation and maint deployment guide says it the best.  Run Agent diagnostics make sure all is green, and to disable agent replication on each VCS. 

 

http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/vcs/config_guide/Cisco_VCS_Cluster_Creation_and_Maintenance_Deployment_Guide_X7-2.pdf

Hope this helps.

VR

Patrick

835
Views
0
Helpful
6
Replies