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
- Stop the On-Premise Poller
- Navigate to /opt/Site24x7OnPremisePoller
- Stop the On-Premise Poller by executing the command:
sudo sh StopServer.sh - Kill existing processes
- Terminate leftover Java and On-Premise Poller processes: Kill the existing processes, if any, by executing the commands:
- sudo kill -9 $(ps aux | grep "[/]opt/Site24x7OnPremisePoller/NetworkPlus/bin" | awk '{print $2}')
- sudo kill -9 $(ps aux | grep "[/]opt/Site24x7OnPremisePoller/NetworkPlus/jre/bin/java" | awk '{print $2}')
- Navigate to /opt/Site24x7OnPremisePoller/NetworkPlus/bin
- Kill Postgres processes, if any:
- Command 1: sudo sh killPgSQL.sh
- Command 2: sudo sh stopPgSQL.sh
- Restart the On-Premise Poller
- Navigate back to /opt/Site24x7OnPremisePoller/ and start the On-Premise Poller using the command:
sudo sh StartServer.sh & - Verify processes
Check if any On-Premise Poller, Java, and Postgres processes are running:
ps aux | grep Site24x7OnPremisePoller
Windows
- 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.
- Stop the Site24x7 On-Premise Poller service as an administrator.
- Kill existing processes
- 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.
- Check for any javaw.exe (Zulu) and wrapper.exe processes.
- Check if the location is \Site24x7OnPremisePoller\NetworkPlus\jre\bin in the command line field or right-click and select Properties to verify.
- If yes, right-click and select End task to end the process.
- Then, navigate to C:\Program Files (x86)\Site24x7OnPremisePoller\NetworkPlus\bin.
- Run the file killpgsql.bat or stoppgsql.bat as Administrator.
-
Restart the On-Premise Poller
-
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 .
-
Verify processes
-
Open Task Manager and check if any On-Premise Poller, Java, and Postgres processes are running.
Related Articles
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 ...Synthetic browser module prerequisite and troubleshooting guide for On-Premise Pollers
Introduction This document provides a structured troubleshooting guide for resolving issues encountered during the download process of On-Premise Poller for Synthetic (Browser) Module. It covers possible statuses, check-up steps, remedies, and ...Monitors that require On-Premise Pollers in Site24x7
Certain monitor types in Site24x7 require the use of On-Premise Pollers for data collection, especially when monitoring internal, firewall-restricted, or private resources. Depending on the type of monitoring, additional modules like the Network ...Exclude the selective SSH algorithms in On-Premise Poller during SFTP Transfer monitoring
By excluding SSH algorithms, you can restrict Site24x7 SSH Client from using the excluded algorithm while connecting to the SSH server during SFTP Transfer monitoring. Follow the steps mentioned below for SSH algorithm exclusion in On-Premise Poller ...How to set up alerts for network device data collection issues
When your network monitoring interfaces are not collecting data due to issues in the Network Module, you'll want to be alerted. To set up alerts, you need to add or edit the threshold and availability profile of the On-Premise Poller, which is used ...