Cloud Probe service does not start after the installation

Problem

Reason

Workaround

After you install the Real User Cloud Probe or change its settings in the Maintenance Tool — the Cloud Probe service might not start.

The Real User Cloud Probe did not start.

  1. View the installation logs and try to find what is the problem. If you don’t see any error in logs, In the BMC Real User Cloud Probe service properties, copy the command for running Cloud Probe, as shown on a figure below:

    Copying the Cloud Probe Running Command

     cloud-probe-service.png

  2. Run the copied command in the Windows command line.The service will start. If it doesn't start, you will receive the error description in the command line screen.

WinPcap tool is not installed on your Windows machine.

  1. Downloadhttp://docs.bmc.com/docs/download/resources/net.customware.confluence.plugin.linking:link-to/img/newwindow.png and install latest version of WinPcap.
    WinPcap is a packet capture driver that is necessary for correct functioning of Cloud Probe under Windows.

The Network Card was not properly configured during the Cloud Probe installation.

  1. Open the epx_properties.conf file located in CloudProbeInstallationDir\cloudprobe\conf.

  2. Provide the name of the Network Card which you want the Cloud Probe to monitor:
    SYSTEM.PROPERTIES.EPX.global.capture_interface=“network_card_name”

    Use ipconfig (Windows) or ifconfig (Linux) command to get the Network card name.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*