2 Replies Latest reply on Jul 21, 2008 12:51 PM by Alessandro Iacopetti

    Sporadic ntfs_filesystem.nsh EO Compliance Failure

    Valerian Jone



      We keep getting this error sporadically on different servers when we run a compliance check that is basically calling the ntfs_filesystem.nsh extended object. We'll run this compliance check once, and it'll be successful against ServerA (for example), and then literally 2 minutes later, when we run the compliance check one more time against the exact same server, ServerA, it'll fail with the below error.


      This sounds like a network issue from the "java.net.SocketException: Connection reset by peer: socket write error" piece of the error, but I'm wondering, what's the best way to for sure determine that.


      Some type of constant network trace or something?


      error occured evaluating compliance rules on component McAfee Pre-Release Check (intweb17) : com.bladelogic.mfw.util.BlException: Caught exception running command - nsh -c "/C/Program Files/BladeLogic/OM/share/sensors/extended_objects/ntfs_filesystem.nsh" intweb17

      Error: error during JRMP connection establishment; nested exception is:

      java.net.SocketException: Connection reset by peer: socket write error