Resolving huge disk space issues with the On-Premise Poller and Network Module

Resolving huge disk space issues with the On-Premise Poller and Network Module

Often huge disk space results from the heap dump files in the NetworkPlus/bin directory of the On-Premise Poller. 

What are HPROF files?

HPROF files are used to store Java virtual machine (JVM) memory dumps. When a JVM runs out of memory (OOM), it throws an OOM exception, and creates the .hprof heap dump files to analyze potential memory issues. The Network Module automatically restarts when it crashes due to the OOM error, creating a huge number of HPROF files in the NetworkPlus/bin folder.

Fixing the heap dump issue

You have to delete all the files with .hprof extension in the NetworkPlus/bin directory to fix this. Please note that deleting these files is safe and will not affect any of your current configurations.

Also, the Network Module requires a certain amount of free RAM (excluding the memory used by the OS and other processes) based on the number of your devices and interfaces for proper functioning. Ensure that you free up the RAM for Network Module to function properly. Refer to this document for the minimum RAM requirements.

To fix the disk space issues:
  1. Stop the On-Premise Poller service.
  2. Ensure there are no existing processes
  3. Check the free memory available in your On-Premise Poller and ensure that they meet the minimum requirements prescribed above.
  4. Navigate to the NetworkPlus/bin directory.
  5. Delete all the files with .hprof extension.
  6. Increase the free memory by ending the stale processes, stopping the other applications or processes that run in the On-Premise Poller machine, and by increasing the RAM to the specified minimum requirements.
  7. Start the On-Premise Poller service.
  8. Check if the Network Module has started properly. If not, share the On-Premise Poller logs and Network Module logs with support@site24x7.com for further debugging.