Troubleshooting steps when the Network Module does not start properly

Follow the steps below to fix Network Module-related issues. If the issue is not resolved by the first step, try the subsequent steps until the issue is resolved.

Step 1:

Stop the On-Premise Poller and restart it with administrator or root privileges. The On-Premise Poller will start running within ten minutes. 

Step 2:

Check if the Network Module is downloaded properly.

1. Log in to the Site24x7 web client, and navigate to Admin > On-Premise Poller.
2. If the status of the Network Module is Download failed , download it manually .

Step 3:

For the Network Module to function properly, there should be a certain amount of minimum space available in your disk and memory. Check if your system configurations meet the system requirements for network monitoring . 

Step 4:

To run the Network Module without any glitches, you must have administrator or root privileges in the system where it is installed. 

If you're using Linux, log in as a root user or as a user who is added to the sudo users' group.

To check if you have been added to the sudo users' group:

1. Execute the command in your terminal:
   
   getent group sudo | cut -d: -f4
2. Verify if the output contains your username. If not, please get in touch with your sysadmin to get it added to the sudo users' group.

If you're using Windows, validate that you have administrator privileges. 

Step 5: 

Even after stopping the On-Premise Poller, some processes may still be running. Check and kill all Java and Postgres processes related to the On-Premise Poller.  

Step 6:

If the above steps don't resolve your issue, the database may be corrupted. If so, reinitialize the database.  

Follow the next step only if you've newly installed an On-Premise Poller and there are no devices being monitored from that On-Premise Poller. Do not try these if there are devices already being monitored from the On-Premise Poller.

1. Stop the On-Premise Poller . 
   
2. Open Command Prompt , and navigate to the home directory of the On-Premise Poller.
   
3. From there, navigate to NetworkPlus > bin folder. 
   
4. Execute the file reinitDB.sh (Linux) or reinitDB.bat (Windows) with root/administrator privileges.
5. Start the On-Premise Poller with root/administrator privileges. 
   

If the issue still persists, contact support@site24x7.com with the following details:

1. Name of the On-Premise Poller
   
2. Logs from the following directories:
   
1. Site24x7OnPremisePoller\logs
   
2. Site24x7OnPremisePoller\NetworkPlus\logs
   

• Related Articles

• Troubleshooting steps for On-Premise Poller

  Prerequisites and basic details: Prerequisites for installing On-Premise Poller Necessary ports to allow access to the installed On-Premise Poller How secure is On-Premise Poller Amount of bandwidth consumed by the On-Premise Poller software Adding ...

• Troubleshooting steps to start the On-Premise Poller in case of system restart/crash

  Please follow the below steps to confirm if the On-Premise Poller is running, or to start the On-Premise Poller, in case of system restart/crash because of power failure, etc. For Windows: Check if the On-Premise Poller service is up and running - ...

• What are the prerequisites for running the Network Module in Windows?

  To run the Network Module without any glitches, you must have administrator privileges in the system where it is installed. Here are the steps to check if you have administrator privileges: From your Windows machine, navigate to the On-Premise ...

• 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 ...

• Troubleshooting steps if the data collection stops for a network device

  Case 1: The On-Premise Poller is Down and/or the Network Module is Disabled. Go to Admin > On-Premise Poller. Check if the state of the On-Premise Poller is active. If not, activate it. Check if the status of the On-Premise Poller is up. If it's ...