Wireless Access

last person joined: 10 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

Error message in logs - An internal system error has occurred at file sapd_sysctl.c

This thread has been viewed 59 times

  • 1.  Error message in logs - An internal system error has occurred at file sapd_sysctl.c

    EMPLOYEE
    Posted Oct 16, 2013 12:10 PM

    I'm getting the error logs filling up with these messages.

     

    Oct 16 12:47:02 <sapd 311020>  <ERRS> |AP BR-VAC-CTL-WAP029@172.16.55.7 sapd|  An internal system error has occurred at file sapd_sysctl.c function sapd_sysctl_write_param line 77 error Error opening /proc/sys/net/aruba_asap/aruba003/bw_share : No such file or directory.

     

    They are coming from all APs at one particular site.  The APs are RAPs as well.

     

    version - 6.2.1.3

     

    Should I be concerned by this?



  • 2.  RE: Error message in logs - An internal system error has occurred at file sapd_sysctl.c

    Posted Oct 16, 2013 12:42 PM
    According to the syslog message guide
    An internal system error has occurred at file [file:%s] function [function:%s] line [line:%d]
    error [error:%s].
    Description: This log indicates that we encountered an internal system error.
    Recommended Action: Contact your support provider

    Best recommendation is to contact TAC...


  • 3.  RE: Error message in logs - An internal system error has occurred at file sapd_sysctl.c

    EMPLOYEE
    Posted Oct 16, 2013 02:46 PM

    Ah yes, forgot to check that.  Case raised with TAC.

     

     



  • 4.  RE: Error message in logs - An internal system error has occurred at file sapd_sysctl.c

    Posted Oct 16, 2013 03:16 PM
    I'd be curious to know what the message means.


  • 5.  RE: Error message in logs - An internal system error has occurred at file sapd_sysctl.c

    EMPLOYEE
    Posted Oct 16, 2013 03:36 PM

    the error message contains 'bw_share' and I have bandwidth contracts for some of the ssids on those APs so I guest it has something to do with that.  I will let you know what TAC say.



  • 6.  RE: Error message in logs - An internal system error has occurred at file sapd_sysctl.c

    Posted Oct 16, 2013 03:48 PM
    I figured as much. Are you using bandwitdth contracts in split-tunnel? Just curious.


  • 7.  RE: Error message in logs - An internal system error has occurred at file sapd_sysctl.c

    EMPLOYEE
    Posted Oct 16, 2013 03:50 PM

    the bandwidth contracts on the tunnelled ssids.  Another ssid is bridge but no bw contract on that one.



  • 8.  RE: Error message in logs - An internal system error has occurred at file sapd_sysctl.c

    EMPLOYEE
    Posted Oct 29, 2013 06:14 AM

    Support have said the message is inocuous.

     

    Explanation Provided:

     

    • Also that I did a research on these messages & I only see these messages to be more of an internal or background process related message.
    • The same cannot be manually disabled & that we have it fixed in 6.3.X.X.

     

    All good then.  :smileyhappy: