Search the VMware Knowledge Base (KB)
View by Article ID

VIC port-layer service fails to start (2151379)

  • 0 Ratings

Symptoms

  • When using the --ops-user option with vic-machine utility to create a VCH, the docker API check fails with a timeout error similar to:

    INFO vSphere API Test: https://vcenter-ip-fqdn/ vSphere API target responds as expected
    ERROR Connection failed with error: i/o timeout
    INFO Docker API endpoint check failed: failed to connect to https://VCH-IP-FQDN:2376/info : i/o timeout
    ### lines omitted for brevity ###
    ERROR --------------------
    ERROR vic-machine-linux create failed: Docker API endpoint check failed: failed to connect to https://VCH-IP-FQDN:2376/info : i/o timeout
  • The port-layer log on the VCH endpoint VM, located at /var/log/vic/port-layer.log reports error similar to:

    DEBUG Error count populating vSphere cache: (1)
    FATAL configure_port_layer ERROR: Failure finding ds (DatastoreName): datastore 'DatastoreName' not found

    Note: The log can be accessed using the following options:

    Browser: https://VCH-IP-FQDN:2378/logs/port-layer.logShell
    Shell: Enable the shell using vic-machine debug. For more information, see  VCH Debug Options. After this is enabled, connect a SSH session and run this command:
    vi /var/log/vic/port-layer.log
  • Docker personality log located at /var/log/vic/docker-personality.log on the VCH endpoint VM reports similar to:

    INFO Waiting for portlayer to come up

    Note: The log can be accessed using the following options:

    Browser
    : https://VCH-IP-FQDN:2378/logs/docker-personality.log

    Shell: Enable the shell using vic-machine debug. For more information, see  VCH Debug Options. After this is enabled, connect a SSH session and run this command:
    vi /var/log/vic/docker-personality.log
  • Attempts to connect to the VCH endpoint VM with the docker client results with this error:

    Cannot connect to the Docker daemon at tcp://VCH-IP-FQDN:2376. Is the docker daemon running?
  • Booting up the VCH endpoint VM and the services do not all start with the same error messages in port-layer and docker-personality logs.

Cause

The user used for the --ops-user option does not have the permissions needed to query vCenter for datastores.

Resolution

To resolve this issue, validate the user used with --ops-user option has the vCenter permissions needed to query datastores. For more information on which permissions are required, see Use Different User Accounts for VCH Deployment and Operation.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 0 Ratings
Actions
KB: