MCC for ISP : edgeHub and MCC containers won't start

Hello,

You're right, MCC is Microsoft Connected Cache, in this case the ISP version (linux)

Here is the guide used :

https://learn.microsoft.com/en-us/windows/deployment/do/mcc-isp-create-provision-deploy

Installation is done on a fresh ubuntu 20.04 server with :

./provisionmcc.sh customerid="xxxxxxxxxxxxx" cachenodeid="xxxxxxxxxxxxx" customerkey="xxxxxxxxxxxxx" registrationkey="xxxxxxxxxxxxx" drivepathandsizeingb="/datadrive,490,"

I tried on Redhat9 (I change the script to trust "CentOS Stream 9" instead of "Redhat 9") and the result was the same : edgeHub never start.

The last iotedge check :

> # iotedge check
> Configuration checks (aziot-identity-service)
> ---------------------------------------------
> √ keyd configuration is well-formed - OK
√ certd configuration is well-formed - OK
√ tpmd configuration is well-formed - OK
√ identityd configuration is well-formed - OK
√ daemon configurations up-to-date with config.toml - OK
√ identityd config toml file specifies a valid hostname - OK
‼ aziot-identity-service package is up-to-date - Warning
    Installed aziot-identity-service package has version 1.4.5 but 1.4.8 is the latest stable version available.
    Please see [https://aka.ms/aziot-update-runtime]() for update instructions.
√ host time is close to reference time - OK
√ preloaded certificates are valid - OK
√ keyd is running - OK
√ certd is running - OK
√ identityd is running - OK
√ read all preloaded certificates from the Certificates Service - OK
√ read all preloaded key pairs from the Keys Service - OK
√ check all EST server URLs utilize HTTPS - OK
√ ensure all preloaded certificates match preloaded private keys with the same ID - OK
Connectivity checks (aziot-identity-service)
> --------------------------------------------
> ‼ host can connect to and perform TLS handshake with iothub AMQP port - Warning

Could not retrieve iothub_hostname from provisioning file.
Please specify the backing IoT Hub name using --iothub-hostname switch if you have that information.
Since no hostname is provided, all hub connectivity tests will be skipped.
    ‼ host can connect to and perform TLS handshake with iothub HTTPS / WebSockets port - Warning
    Could not retrieve iothub_hostname from provisioning file.
    Please specify the backing IoT Hub name using --iothub-hostname switch if you have that information.
    Since no hostname is provided, all hub connectivity tests will be skipped.
‼ host can connect to and perform TLS handshake with iothub MQTT port - Warning
    Could not retrieve iothub_hostname from provisioning file.
    Please specify the backing IoT Hub name using --iothub-hostname switch if you have that information.
    Since no hostname is provided, all hub connectivity tests will be skipped.
√ host can connect to and perform TLS handshake with DPS endpoint - OK
Configuration checks
> --------------------
> √ aziot-edged configuration is well-formed - OK
√ configuration up-to-date with config.toml - OK
√ container engine is installed and functional - OK
√ configuration has correct URIs for daemon mgmt endpoint - OK
‼ aziot-edge package is up-to-date - Warning
    Installed IoT Edge daemon has version 1.4.16 but 1.4.33 is the latest stable version available.
    Please see [https://aka.ms/iotedge-update-runtime]() for update instructions.
√ container time is close to host time - OK
√ DNS server - OK
√ production readiness: logs policy - OK
‼ production readiness: Edge Agent's storage directory is persisted on the host filesystem - Warning
    The edgeAgent module is not configured to persist its /tmp/edgeAgent directory on the host filesystem.
    Data might be lost if the module is deleted or updated.
    Please see [https://aka.ms/iotedge-storage-host]() for best practices.
× production readiness: Edge Hub's storage directory is persisted on the host filesystem - Error
    Could not check current state of edgeHub container
√ proxy settings are consistent in aziot-edged, aziot-identityd, moby daemon and config.toml - OK
Connectivity checks
> -------------------
> 24 check(s) succeeded.
> 6 check(s) raised warnings. Re-run with --verbose for more details.
> 1 check(s) raised errors. Re-run with --verbose for more details.
> 7 check(s) were skipped due to errors from other checks. Re-run with --verbose for more details.
> 

Hi @Julien Greetings! Welcome to Microsoft Q&A forum. Thank you for posting this question here.

I wanted to make sure if you have mounted a disk on the server before setting up the module. There is a note on the document that mentions MCC will not be successfully installed without mounting your disk. Before provisioning your server, ensure your disk is correctly mounted by following the instructions here: Attach a data disk to a Linux VM.

Also, before running the script you would have to change the permissions on the downloaded script using the following command sudo chmod +x provisionmcc.sh

If you have verified the above steps and still face the issue, please file a support request @ https://aka.ms/azsupt?