How Do I Fix the Error "The collector is not installed" When a Discovery Task Fails?

Symptom

After the MgC Agent and resource credential were associated, the deep collection failed, and the failure cause was "The collector is not installed."

Possible Causes

Possible causes are:

• The MgC Agent server's capacity is too small to run the collector. The recommended specifications are 4 vCPUs and 8 GB of memory.
• The collector was offline even though the MgC Agent server's capacity was sufficient.

Solutions

• The MgC Agent server's capacity is too small.

  Upgrade the MgC Agent server's specifications or install the MgC Agent on a server with a larger capacity. Then perform a deep collection again.

• The collector was offline.

  The following table lists the collectors integrated in the MgC Agent. The server collector is used as an example to explain the method, which applies to other collectors as well.

  Collector	Collected Resource	Process	Installation Directory
  designcenter-collector-platform	Private cloud platform Currently, only VMware environments are supported.	designcenter-collector-platform.exe	Windows: C:\MgC-Agent\tools\plugins\collectors Linux: <installation-directory>/opt/cloud/MgC-Agent/tools/plugins/collectors/
  designcenter-collector-server	Server	designcenter-collector-server.exe
  rda-collector-kubernetes	Container	rda-collector-kubernetes.exe
  rda-collector-database	Database	rda-collector-database.exe
  rda-storage-collector	Storage	rda-storage-collector.exe

  • Restarting the Windows collector
    1. Go to the bin directory in the collector installation directory on the MgC Agent server, for example, C:\MgC-Agent\tools\plugins\collectors\designcenter-collector-server\bin.
    2. Double-click start.bat to start the server collector.
    3. Open Task Manager. On the Details tab, check the status of designcenter-collector-server.exe. If the status is Running, the collector is started.
    4. Return to the MgC console, locate the source resource, and click Collect Again in the Deep Collection column to collect the resource information again.
  • Restarting the Linux collector
    1. Log in to the MgC console and check if the MgC Agent is executing any deep collection, intranet scanning, or VMware VM discovery tasks. If it is, perform subsequent operations after the tasks are complete.
    2. Log in to the Linux server where the MgC Agent is installed.
    3. Update environment variables.

       source /opt/cloud/MgC-Agent/scripts/setenv.sh

    4. Run the following command to access the bin directory in the installation directory of the server collector in the MgC Agent:

       cd /opt/cloud/MgC-Agent/tools/plugins/collectors/designcenter-collector-server/bin

    5. Run the following command to start the server collector:

       ./start.sh

    6. Check whether the collector process runs properly.

       ps -ef | grep -v grep | grep designcenter-collector-server

    7. Return to the MgC console, locate the source resource, and click Collect Again in the Deep Collection column to collect the resource information again.