Monitoring CloudView Processes

This section details how to monitor processes in your CloudView platform.

This page discusses:

See Also
Checking System Health and Performance
Configuring CloudView Logs
Fixing Out of Memory Issues
Volumic Search Troubleshooting

Check Status

The critical processes to check are searchserver and index.

Processes may be in the following statuses:

  • started
  • starting
  • stopping
  • stopped
  • dead

To check processes:

  1. Go to <INSTALLDIR>\<OS>\cv\data\bin.
  2. Run:
    cvinit.bat|sh status
    The output displays the process name, status, PID, and start date: 
    NAME                  STATUS PAYLOAD  PID         STARTDATE
consolidationserver-cs0     started - 7332  2016-10-07  11:15:55+0200
searchserver-ss0            started - 2260  2016-10-07  11:15:55+0200
master                      started - 9240  2016-10-07  09:48:38+0200
index6-bg0-i0               started - 9236  2016-10-07  09:48:38+0200
gateway                     started - 9250  2016-10-07  09:48:38+0200
indexingserver-bg0          started - 9239  2016-10-07  09:48:38+0200
connectors-java0            started - 23311 2016-10-07  10:49:01+0200
convert-c0                  started - 9231  2016-10-07  09:48:38+0200
crawler-exa0                started - 2213  2016-10-07  11:15:52+0200

Look for Unexpected Restarts

  1. Go to http://<HOSTNAME>:<BASEPORT+11>/mami/deploy/getDeploymentStatus.
  2. Look for nbUnexpectedRestarts, nbConsecutiveUnexpectedRestarts, and loopCrashing="true".