WLC 4404 %OSAPI-3-FILE_OPEN_FAILED

the WLC 4404 present this logs:
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-FILE_OPEN_FAILED:  osapi_file.c:370 Failed to open the file : /proc/927/stat.(erno 24)
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-TASK_GETTIME_FAILED:  osapi_task.c:3431 Failed to retrieve statistics  (/proc/<pid>/stats) for task 'gccp_t'
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-FILE_OPEN_FAILED:  osapi_file.c:370 Failed to open the file : /proc/926/stat.(erno 24)
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-TASK_GETTIME_FAILED:  osapi_task.c:3431 Failed to retrieve statistics  (/proc/<pid>/stats) for task 'dot1dTimer'
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-FILE_OPEN_FAILED:  osapi_file.c:370 Failed to open the file : /proc/925/stat.(erno 24)
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-TASK_GETTIME_FAILED:  osapi_task.c:3431 Failed to retrieve statistics  (/proc/<pid>/stats) for task 'dot1dRecv'
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-FILE_OPEN_FAILED:  osapi_file.c:370 Failed to open the file : /proc/921/stat.(erno 24)
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-TASK_GETTIME_FAILED:  osapi_task.c:3431 Failed to retrieve statistics  (/proc/<pid>/stats) for task 'fdbTask'
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-FILE_OPEN_FAILED:  osapi_file.c:370 Failed to open the file : /proc/920/stat.(erno 24)
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-TASK_GETTIME_FAILED:  osapi_task.c:3431 Failed to retrieve statistics  (/proc/<pid>/stats) for task 'nPCSL_timer'
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-FILE_OPEN_FAILED:  osapi_file.c:370 Failed to open the file : /proc/916/stat.(erno 24)
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-TASK_GETTIME_FAILED:  osapi_task.c:3431 Failed to retrieve statistics  (/proc/<pid>/stats) for task 'tFrameReceive'
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-FILE_OPEN_FAILED:  osapi_file.c:370 Failed to open the file : /proc/913/stat.(erno 24)
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-TASK_GETTIME_FAILED:  osapi_task.c:3431 Failed to retrieve statistics  (/proc/<pid>/stats) for task 'tFrameReceive'
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-FILE_OPEN_FAILED:  osapi_file.c:370 Failed to open the file : /proc/917/stat.(erno 24)
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-TASK_GETTIME_FAILED:  osapi_task.c:3431 Failed to retrieve statistics  (/proc/<pid>/stats) for task 'tFrameSend'
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-TASK_GETTIME_FAILED:  osapi_task.c:3431 Failed to retrieve statistics  (/proc/<pid>/stats) for task 'Gmac Link Task'
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-FILE_OPEN_FAILED:  osapi_file.c:370 Failed to open the file : /proc/905/stat.(erno 24)
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-TASK_GETTIME_FAILED:  osapi_task.c:3431 Failed to retrieve statistics  (/proc/<pid>/stats) for task 'tDapiTxTask'
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-FILE_OPEN_FAILED:  osapi_file.c:370 Failed to open the file : /proc/904/stat.(erno 24)
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-TASK_GETTIME_FAILED:  osapi_task.c:3431 Failed to retrieve statistics  (/proc/<pid>/stats) for task 'RMONTask'
*osapiReaper: Oct 02 14:55:11.152: %OSAPI-3-FILE_OPEN_FAILED:  osapi_file.c:370 Failed to open the file : /proc/903/stat.(erno 24)
when present this loggs the device present those symptoms:
lost GUI session
Lost console conection
Lost SSH and Telnet conecction
the WLC 4404 not work is stopedd

Almost looks like it could be defect ID CSCtx02515.  SHows that it's fixed in 7.2.110.0, but if you have a 4404, you can't run 7.2 code.
Symptom:
High CPU on webJavaTask
Alternatively: large number of TCP connections, leading to file descriptor problems like:
osapi_file.c:370 Failed to open the file : /proc/1054/stat.(erno 24)
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtx02515
HTH,
Steve
Please remember to rate useful posts, and mark questions as answered

Similar Messages

  • %OSAPI-3-FILE_OPEN_FAILED

    Help
    I have a Cisco WLC 4404 with version software 7.0.230.0 and it gived me a this logg
    Oct 9 15:43:08 192.168.122.34 WLC_4404_CC: *osapiReaper:
    Oct 09 15:41:49.549: %OSAPI-3-FILE_OPEN_FAILED: osapi_file.c:370 Failed to open the file : /proc/895/stat.(erno 24)
    Please helpme .I do not understand this logg

    So the effect of the logg are:
    Lost console conection
    Lost SSH and Telnet conecction
    the WLC 4404 not work is stopedd

  • What settings need to be set for the fastest roaming on my wlc 4404

    Hi all
    I notice that on my WLC 4404 when walking around with my laptop, I am dropping pings when it roams to another access point, Is there anything on the controller I need to check, and can I optimize these settings for roaming?
    cheers
    carl

    Hello Carl,
    to have romaing working fine you need to be sure of following:
    1) RF designed correctly , and enough overlapping is availble between the AP's.
    in addition for environment to be free from external noise..
    this can be confirmed with spectrum expert site survey
    2) what authentication and encryption used ( WEP , or WPA-PSK no need to check this point ->> skip :-) )
    if you are using any authentication like 802.1x ->> then enable CCKM on the WLAN to make more seamless roaming.
    3) if more than one WLC availble on site , configure mobility group between them,
    so if client roam from one AP in WLC 1 to AP on WLC 2 ->> no disocnnection observed....
    Kind regards
    Talal
    ===========
    please rate answers that you find useful , and mark as answered - when it is :-) - so others can find it easily

  • WLC 4404 Wireless users getting disabled

    Currently Being Moderated
    Wireless users getting disabled
    Hi,
    I have WLC 4404 with 7.0.116.0 version. I was getting following messages for particular APs
    *Dec 20 14:11:13.875: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Dec 20 14:11:13.908: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Dec 20 14:11:29.383: %LWAPP-5-RLDP: RLDP stopped on slot 0.
    *Dec 20 14:11:29.674: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
    *Dec 20 14:11:29.678: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Dec 20 14:11:29.700: %LWAPP-5-RLDP: RLDP started on slot 0.
    *Dec 20 14:11:29.707: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Dec 20 14:11:29.752: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
    *Dec 20 14:11:29.757: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Dec 20 14:11:29.790: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Dec 20 14:11:45.396: %LWAPP-5-RLDP: RLDP stopped on slot 0. *Dec 20 14:11:13.875: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    After seeing one of the cisco forum, I have disabled RLDP for that particular APs
    so above messages are rectified.
    But right now we are not able to identify Rogue IP and it is not contained.
    So please give any suggetion so that i can rectify the above messages as well as i can identify the rogue IP.
    Thanks & Regards
    Gaurav Pandya

    Hi Scott,
    You are right i am not able to detect rogue APs because i disabled the RLDP. but when i enable the RLDP for that particular AP. i got the following messages with interface go up and down
    *Dec 20 14:11:13.875: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Dec 20 14:11:13.908: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Dec 20 14:11:29.383: %LWAPP-5-RLDP: RLDP stopped on slot 0.
    *Dec 20 14:11:29.674: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
    *Dec 20 14:11:29.678: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Dec 20 14:11:29.700: %LWAPP-5-RLDP: RLDP started on slot 0.
    So please suggest me the mid way so that i can enable the RLDP (Detect the rogue APs) with out interface going up and down frequently.
    Regards
    Gaurav

  • Wireless clients load balancing on the APs on WLC 4404

    Hi Experts,
    I'm just wondering if the WLC 4404 with firmware 4.2.207.0 can load balance the wireless clients on different WAPs. Let's say that an AP is already handling 15 Wireless devices. When the 16th is trying to join, the controller somehow puts it on another nearby AP, even the signal from this AP is weaker. I heard the similar feature on other Wireless solution vendors. I'm just wondering if Cisco has the similar feature or not.
    Thanks!

    Yes it is known as aggressive load balancing sending a code 17 making the wireless client to loook at another nearby AP.
    here it is the documentation:
    http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a00809c2fc3.shtml

  • WLC 4404 - Clearing the Load Balancing Statistics?

    Does anyone know of a way to clear the load balancing statistics from a WLC 4404?  I've looked through the gui and CLI and can't seem to find a way to do it.
    Thanks,
    Rob

    You can do a 'show summary' to see the number of connections that have been sent to each servers.
    You can't see the number of bytes so.
    I would suggest to collect this info on the server.
    Regards,
    Gilles.

  • Replacing WLC 4404 with 5508

    Hi Friends,
    I am new to Cisco wireless and would appreicate any help with replacing WLC 4404 with 5508. I mean any link or doc (best practices).
    Thansk,
    Nav
    [email protected]

    Yup, what said Scoot said .. Add the 5508 to the aps high availability. If you have WCS/NCS you can push this to the APs.
    "Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
    ‎"I'm in a serious relationship with my Wi-Fi. You could say we have a connection."

  • Decrypt Errors - WLC 4404

    Hello,
    We recently had a few clients being locked down with countermeasures by our WLC 4404 due to TKIP-MIC errors. After doing some reading on the benefits of AES over TKIP I switched our WLAN security settings to AES, and pushed a new wireless policy to our client machines. Every thing appeared to work well, except now the trap log on the 4404 is showing a LOT of WPA decrypt errors. I've checked a few of the clients that appear to have problems, but they've got the right policy and WPA settings to match what is on the WLC.
    It's not one particular NIC, it's various clients.
    Any thoughts on how I might clear these up?
    Rob

    One reason for that is configuration of two WEP keys on a single WLAN is not supported. Currently WLAN can only take one WEP key.

  • Wlc 4404 upgrade

    Hi, looking for advice on which code to upgrade to. We have a wlc 4404 using mostly AIR-AP1231G-A-K9 access points. The current code is 4.2.130.0. We would like to use some of the 1141 APs and I understand they need at least 5.2. My plan would be to go to 6. I believe I need to go to 4.2.176.0 first and then to 6. The question would be what version of 6 would be the best?  Right now 6.0.182.0 (ED), 6.0.188.0 (ED), and 6.0.196.0 (ED) are available.

    Well that is a tricky question and really depends on a lot of variables.  We have installs with all three versions of the software.  Currently I would have to say that 6.0.188.0 is one to try.  We have upgraded some clients to 6.0.196.0 because of issue with the 6.0.188..0, but again, it all depends what equipment you have and if you see any issues with the 6.0.188.0.  Some people I know have just went right to the 6.0.196.0 code and have not seen any issues.  The 6.x is still pretty new in my book, but like you already did..... review the caveats on the different versions and if you have a spare WLC,do some testing.

  • Upgrade BootLoader on Cisco WLC 4404

    What is the latest Bootloader for the Cisco WLC 4404?  And where can I download it?
    My current versions are:
    Product Version.................................. 5.2.178.0
    RTOS Version..................................... 5.2.178.0
    Bootloader Version............................... 4.0.206.0
    Also is there a reason to upgrade the bootloader image?
    On this webpage http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00805f381f.shtml it shows the steps to upgrade WLC are :
    This sequence is recommended for your WLC software upgrade:
    Upload a backup of your controller configuration to a TFTP server.
    Disable the 802.11a and 802.11b/g networks on your controller.
    Upgrade the primary image on your controller.
    Upgrade the boot image on your controller.
    Note: This is a required step for upgrades to 4.1 on the WiSM, 3750G Wireless LAN Controller, and 4400 Series Controllers.
    Re-enable the 802.11a and 802.11b/g networks on your controller.
    I get the primary image is just going to be AIR-WLC4400-K9-6-0-196-0.aes.  But where do i download the Bootloader and it looks like i just do the same thing i did with the primary image.
    I think I am missing something.
    Thanks

    The boot software image consists of the controller boot kernel and           boot menu script. that is.. when you use the WLC for the first time. then you will be able to use this while entering the username, mobility information.. interfaces informations etc.. the Software version is the one which you issue CLI  commands...or even simple example wil be.. reboot the WLC and hit ESC.. the software that you access at this time will be boot loader..
    to upgrade the bootloader...
    http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00805f381f.shtml#hw
    Regards
    Surendra

  • Wlc 4404 strange behaviour

    Hello,
    I have to manage a wlc 4404. According to me he acts strange.
    Only ports 1,2 and 3 are connected. The ap-manager and the management are linked at port 1. So far so good.
    If I look at the wireless-tab I see all AP's are connected at port 3 !!
    All the 3 ports are connected to the same switch and VLAN.
    AP=Cisco Aironet 1130AG with a default config
    Could someone explain me why all AP's are connected on port 3, while the ap-manager is linked at port 1.
    Thanks in advance,
    Carlo

    The Cisco docs clearly state that you can only have 48 APs associated to each ap-manager interface. If you are not running LAG, and I can't think of a good reason not to, then you will need 3 physical interfaces to be configured with unique ap-manager ip addresses in order to register 100 APs. Since the APs point to the management ip (via DNS or DHCP) to get the ap-manager interface, they will automatically load balance.
    Note that unless you are running VERY recent code, there are significant ARP bugs related to the additional ap-manager interfaces responding to ARP requests. The best-practice is to add a static ARP entry in the router/L3 switch that is the ap-manager's default-gateway. This is an artifact of the ap-manager interfaces not responding to any traffic accept LWAPP, including ARP. This has been a serious problem for a lot of enterprise customers because this impacts most CEF switching devices like the Catalyst 6500 since most IOS versions also have a CEF adjacency/ARP timeout bug.

  • Snmp monitoring for wlc 4404

    Hi,
    we use a snmp monitoring software called Nagios in our LAN. Now we have two WLC 4404. Is it possible to monitor values via snmp? Is someone else doing it so?
    Witch values can be monitored and for what values is it wise or practicable to monitor it?
    Regards
    Christian

    There are some threads in this forum regarding this already. It is not as easy as monitoring a switch or router. the controllers combine the AP mac with the oid for unique lines. You can glean some snmp info off the controllers by using some of the generic OIDs and controller specific OIDs, but you will need an snmp monitoring program that you can load the WLC MIBs into and then tailor your monitoring of the controller based on that. I use Cacti, which is really awesome, but I would need to grab the complete OID off each controller based on the APs on it, which is fine as long as the AP is on that particular controller and not another one. snmpwalk is your friend in this case.
    OID+mac = results

  • WLC 4404 port reset?

    Hi,
    We have a WLC 4404 and had a dodgy Gbic that caused the port to go down, but now we can't get the port to come back up.
    Do you think reloading the firmware will reset everything?
    Thanks

    Removing the GBIC and reloading the controller should help you in this case. Software has not got anything to do since it the problem is with the physical connection.

  • WLC 4404-100 with CAP1550E

    Currently I have a WLC 4404-100 and 96 nos. LWAP 1250 installed at site. I need to add CAP1550E (4 Nos.) to this existing setup. Out of this CAP1550E, 2 needs to be configured as root, and the remaining 2 has to be connected through 802.11a/n backhaul and meshed.
    Can I achieve this scenario, without adding a new controller??
    Thanks to all in advance.....

    jerrick,
    Yes you can. Mesh and non-mesh functionality has been merged for quite some time now. Use more recent code (7.0.x) or higher for best results.
    If you are unfamiliar with configuring mesh, consider spending some time scanning the 7.2 mesh design guide. Mesh works a little bit differently than your traditional local-mode APs and you need to do some additional configuration on the controller to tune it to your environment.
    7.2 Mesh Design Guide: http://www.cisco.com/en/US/docs/wireless/technology/mesh/7.2/design/guide/MeshAP_72.html
    One thing the guide doesn’t say (I don’t think): Get it working on the ground first, then hang your APs. It will save you a lot of time and frustration.
    Justin

  • Wlc 4404 and high avaibility

    If i have 2 WLC 4404 that support 100 Access Points for one and i have installed 110 Access Point, can i you decide when a WLC go down which are the 10 Access Point that must stay down?
    thanks for your help
    fcostalunga

    Let me understand your question.
    You have two WLC and each can support 100 AP. You have 110 APs. If one of the WLC should go down, how can you configure or tell which 10 AP's will be unable to join?
    If this is your question, here are some solutions I can think of.
    1. H-REAP. If you enable H-REAP to all your AP's, when one or ALL of your WLCs should go down, the AP's will be able to operate as if the WLC were up. The exception-to-the-rule is DO NOT reload the AP's and this should be fine.
    2. You can configure, via CLI only, 100 AP's the primary and secondary controller. 10 AP's will have no config so they will go into "limbo".
    Hope this helps.

Maybe you are looking for