For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

jet550_301068's avatar
jet550_301068
Icon for Nimbostratus rankNimbostratus
Apr 05, 2017

Syslogd message - File Does not Exist

I am monitoring some F5 devices through an NMS and receive the following syslog message every once in a while. I haven't found any documentation for this specific message so am coming to the F5 community. Any clue as what it is and if it isn't something I should be worried about, how to mitigate the messages coming in without turning away the local6 err messages?

 

Message: err httpd[16873]: [error] [client 192.168.240.21] File does not exist: /usr/local/www/wsman

 

application delivery
BIG-IP

2 Replies

  • Greg_Jewett's avatar
    Greg_Jewett
    Icon for Cirrus rankCirrus
    Nov 22, 2019

    +1 (me too); I started seeing these in my logs. What does this mean? If you search for the path alone in Google, you get information about Windows OS, PowerShell and "WSman" service.

  • jaikumar_f5's avatar
    jaikumar_f5
    Icon for Noctilucent rankNoctilucent
    Nov 23, 2019

    From my understanding, /usr/local/www/ is the path where the login page exists and has the banner files. This is like the apache home directory where your required files exist. So this location contains the items what you see on the GUI or the browser.

     

    Here's what I think could have happened, that folder or the file existed on your previous version, but not in the latest code. This could have been because of the upgrade on the bigip.

     

    And its obvious why you are seeing it on local6, because local6 file logs the details of httpd, again Apache related.

     

    But what wsman is about, I have no clue.