Verifying and ending existing processes in On-Premise Poller

Verifying and ending existing processes in On-Premise Poller

When the network module continues to initialize, you might have to end an existing process to fix this.

Linux
  1. Navigate to  /opt/Site24x7OnPremisePoller
  2. Stop the On-Premise Poller by executing the command:
    sudo   sh StopServer.sh  
  3. Kill the existing processes, if any, by executing the commands:
    1. sudo kill -9 $(ps aux | grep "[/]opt/Site24x7OnPremisePoller/NetworkPlus/bin" | awk '{print $2}')
    2. sudo kill -9 $(ps aux | grep "[/]opt/Site24x7OnPremisePoller/NetworkPlus/jre/bin/java" | awk '{print $2}')
  4. Navigate to  /opt/Site24x7OnPremisePoller/NetworkPlus/bin
  5. Kill the Postgres processes, if any, by executing any one of these commands:
    Command 1: sudo sh killPgSQL.sh
    Command 2:     sudo sh stopPgSQL.sh
  6. Navigate back to  /opt/Site24x7OnPremisePoller/  and  start the On-Premise Poller using the command:
    sudo sh StartServer.sh &  

Windows
  1. Navigate to Start > Settings > Control Panel . Under Administrative Tools , click Services . You can also navigate to services.msc from Run.

  2. Stop the Site24x7 On-Premise Poller service as an administrator.

  3. Open Task Manager and go to the Details tab.
  4. Check for any java.exe and javaw.exe processes.

  5. If found, right-click and go to Properties .

  6. Check if the location is
    C:\Program Files (x86)\Site24x7OnPremisePoller\NetworkPlus\jre\bin 
  7. If yes, right-click and select End task to end the process. 

  8. Navigate to  C:\Program Files (x86)\Site24x7OnPremisePoller\NetworkPlus\bin
  9. Run the file killpgsql.bat or stoppgsql.bat as Administrator.
  10. Start the Site24x7 On-Premise Poller service.
If there is no java.exe process or if the location is different , you need not end the process. Just start the Site24x7 On-Premise Poller service .