Continuous messages *dtlArpTask: osapi_sem.c:1179 Failed to acqu

Kunal Parikh · ‎09-10-2013

Client have recently upgraded from 4402 WLC to 5508. They are now receiving a large number (100 000s a day) of warnings. Software Version is

7.5.102.0

2013-09-09 00:00:02 Local0.Warning 10.61.183.17 ausowlc1: *rmgrMain: Sep 09 00:00:02.769: #OSAPI-4-MUTEX_LOCK_FAILED: osapi_sem.c:1179 Failed to acquire a mutual exclusion object. invalid(NULL) pointer passed.

I have found related bug CSCui55350/ CSCuh41790

---------------------------

CSCui55350/ CSCuh41790

Continuous messages *dtlArpTask: osapi_sem.c:1179 Failed to acquire ..

Symptom:

Continuous messages:

-Traceback: 0x10c31374 0x10c8a6a4 0x10c9ea08 0x10c94748 0x10c402d8 0x12283850 0x122f634c

*rmgrMain: Aug 08 09:49:21.902: #OSAPI-5-MUTEX_UNLOCK_FAILED: osapi_sem.c:1036 Failed to release a mutual exclusion object. invalid(NULL) pointer passed.

-Traceback: 0x10c30d9c 0x10c8a7f4 0x10c9ecf8 0x10c95d4c 0x10c402d8 0x12283850 0x122f634c

*rmgrMain: Aug 08 09:49:21.902: #OSAPI-4-MUTEX_LOCK_FAILED: osapi_sem.c:1179 Failed to acquire a mutual exclusion object. invalid(NULL) pointer... more

Conditions:
AP in flex mode, 7.5 in use
Workaround:
None
Further Problem Description:

Details:

Known Affected Releases: (3)

7.5(102.0) | 7.5(1.69) | 7.4(100.0)

Known Fixed Releases: 0

Release Pending

Product: Cisco 5500 Series Wireless Controllers

-------------------------

Status of this bug is fixed but known fixed releases are 0. Please advise if this software bug and/or hardware failure and what is best workaround ?

Any help would be appreciated.

Scott Fella · ‎09-11-2013

Your better opening a TAC case and getting a direct answer from Cisco on this. Just my 2 cents. Might get your answer faster:)

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***

MICHAEL PAPAIKONOMOY · ‎10-09-2013

I have the same problem too. Did you get the answer......

Kunal Parikh · ‎10-09-2013

Hi Michael,

This error is seen due to a setting the dev team has disabled on the WLC and are expected to be fixed in 7.6. These messages are just cosmetic and have no impact.

Workaround at this point is :

These are warning messages displayed on the console. Instead of enabling warnings, errors can be enabled. So that it does not flood the console.

Kunal

MICHAEL PAPAIKONOMOY · ‎10-09-2013

Hello Kunal too.

Thanks for quickly responce.

I will change the severity. Thanks again.