Forum Discussion

Daniel_55334's avatar
Daniel_55334
Icon for Altostratus rankAltostratus
May 16, 2008

error message

We found some error messages on our 2400 platform running v9.3.1 today. Does someone have idea what they are about? Thanks.

 

 

May 16 04:31:02 bigip01 logger: 011d0003: Error parsing df -k output

 

May 16 04:31:02 bigip01 logger: 011d0003: Error parsing df -k output

 

May 16 05:01:03 bigip01 logger: 011d0003: Error parsing df -k output

 

May 16 05:01:03 bigip01 logger: 011d0003: Error parsing df -k output

 

May 16 05:31:02 bigip01 logger: 011d0003: Error parsing df -k output

 

May 16 05:31:02 bigip01 logger: 011d0003: Error parsing df -k output

 

4 Replies

  • It appears to be a diskmonitor error in the var/log/ltm file. These messages suggests a bug. I don't think it will cause any problems, but if you are on 9.3.1, there are hotfixes so they might have solve them. My suggestion is to either go AskF5 or simply call thier Tech support to be sure.

     

     

     

    CB

     

     

     

     

  • We've just started seeing similar messages on our 9.4.3 machine

     

    diskmonitor: 011d0003: Error parsing df -k output

     

    Best as I can tell, this is related to an NFS mount on the F5 in question. I'm going to unmount the share and see if the error goes away.
  • I guess these messages are benign. In diskmonitor, all lines from "df -k" have to have 6 fields ("words"). When it's not 6 fields then it'll spit out this message.

     

     

    You can run this command to see which line is causing this:

     

     

    df -k | awk 'NF != 6'