*Steps 2 through 10 must be run on each of the Filr Search Server(s) in your Filr deployment.
2. On the Search Server, stop the index service.
3. Edit /opt/novell/search/indexserver/etc/vibe.management.properties file.
4. Identify the following line and uncomment it (also make sure to get rid of the extra leading space).
5. Save the file and exit.
6. Having made these configuration changes to the index server, make sure to clear/move all existing log files at /opt/novell/search/indexserver/logs before re-starting the index server.
mv /opt/novell/search/indexserver/logs/*.* /opt/novell/search/indexserver/logs/oldlogsJC
7. Restart the Index service.
8. Temporarily stop firewall on Search Appliance by using this command.
9. In order for the monitor to work, you will need to open port 8642 for incoming traffic through the firewall using Yast.
- Click on Security and Users > Firewall.
- Select the Allowed Services tab and click Advanced.
- Add port 8642 to TCP list.
- Click OK to close the Advanced dialog box.
- Click Next and review the summary of your changes.
- Click Finish to apply your changes and then quit.
10. Start Firewall.
*Steps 11 through 14 should be performed on the monitoring client machine that has the JDK installed.
11. On the client machine install Java JDK 1.8 or newer (not JRE).
12. On the client machine, start JConsole.
13. Click “Remote Process” radio button in the “JConsole: New Connection” dialog. Enter <index server hostname>:8642 in the text box (leave username and password as blank) and press Connect button. Select the “Memory” tab and then the “Heap Memory Usage” Chart.
14. Keep this window open for continued monitoring of the Java heap space usage over time. You may have to take periodic screen captures of the chart to save the data for review.