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. Stop the On-Premise Poller
    1. Navigate to  /opt/Site24x7OnPremisePoller
    2. Stop the On-Premise Poller by executing the command:
      For older On-Premise Poller versions, use:
sudo sh StopServer.sh
      For On-Premise Poller version 6.7.9 and later (installed as a service), use: sudo systemctl stop site24x7-onpremise-poller
  2. Kill existing processes
    1. Terminate leftover Java and On-Premise Poller processes: 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}')
    2. Navigate to  /opt/Site24x7OnPremisePoller/NetworkPlus/bin
  3. Kill Postgres processes, if any:
    1. Command 1: sudo sh killPgSQL.sh
    2. Command 2: sudo sh stopPgSQL.sh
  4. Restart the On-Premise Poller
    1. Navigate back to  /opt/Site24x7OnPremisePoller/ and start the On-Premise Poller using the command:
      For older On-Premise Poller versions, use:
      sudo nohup ./StartServer.sh >> logs/shell_script.log 2>&1 &
      For On-Premise Poller version 6.7.9 and later (installed as a service), use:
      sudo systemctl start site24x7-onpremise-poller
  5. Verify processes
    Check if any On-Premise Poller, Java, and Postgres processes are running:
    ps aux | grep Site24x7OnPremisePoller
Windows
  1. Stop the On-Premise Poller: Navigate to Start > Settings > Control Panel. Under Administrative Tools, click Services. You can also navigate to services.msc from Run. Make sure that you open Run as an administrator. 
  2. Stop the Site24x7 On-Premise Poller service as an administrator.

  3. Kill existing processes
    1. Open Task Manager and go to the Details tab. Ensure the Command line column is visible. If it isn’t, right-click on any column header, click Select Columns, check Command line, and click OK.
    2. Check for any javaw.exe (Zulu) and wrapper.exe processes.
    3. Check if the location is \Site24x7OnPremisePoller\NetworkPlus\jre\bin in the command line field or right-click and select Properties to verify.
    4. If yes, right-click and select End task to end the process. 
    5. Then, navigate to  C:\Program Files (x86)\Site24x7OnPremisePoller\NetworkPlus\bin.
    6. Run the file killpgsql.bat or stoppgsql.bat as Administrator.
  4. Restart the On-Premise Poller
    1. Start the Site24x7 On-Premise Poller service.
      Notes
      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 .
  5. Verify processes
    1. Open Task Manager and check if any On-Premise Poller, Java, and Postgres processes are running.