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 ...How to manually download and enable the Network Module in an On-Premise Poller
Please follow the steps given below to manually download and enable the Network Module for the On-Premise Poller: Stop the On-Premise Poller service. Ensure that there are no existing processes in the On-Premise Poller . Check if there is a folder ...Prerequisites for installing the On-Premise Poller
To monitor your internal network and resources behind a firewall, you need to install the On-Premise Poller within your network. You can install the On-Premise Poller on physical or virtual machines. System requirements: The machine on which the ...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 ...Manage log files filling up on an On-Premise Poller
The limit for a single log file is 10 MB. Beyond this, we will rotate the logs up to 10 files, giving a maximum of 100 MB for a single module. Likewise, we have 7-8 modules. This depends on the customer's usage of Poller and the number of monitors ...