Skip to main content

vCD portal is not accessible after the installation

 I wanted to share my experience in fixing NFS issue during vCD 9.7 Linux based installation. 

It is my first cell in the server group with CentOS 7 as operating system. The NFS server(centos) and client versions are v4. After configuring the first cell in the environment, the vCD service started successfully however when I tried to access vCD web port it was not accessible. 


 

vCD service status as below 

# service vmware-vcd status

vmware-vcd-watchdog is running

vmware-vcd-cell is running

 cell.log

======

Application Initialization: 'com.vmware.vcloud.common.core' 95% complete. Subsystem 'com.vmware.vcloud.jax-rs-servlet' started

Application Initialization: 'com.vmware.vcloud.common.core' 100% complete. Subsystem 'com.vmware.vcloud.ui-vcloud-webapp' started

Application Initialization: 'com.vmware.vcloud.common.core' complete.

Successfully handled all queued events.

Successfully verified transfer spooling area: /opt/vmware/vcloud-director/data/transfer

Cell startup completed in 0m 48s

 

While checking my installation prereqs noticed the transfer share directory was mounted and had ownership as nobody:nobody instead of vcloud user and group.


 Troubleshooting steps followed are 

  • Changed the ownership to vcloud:vcloud using command chown -R vcloud:vcloud /opt/vmware/vcloud-director/data/transfer
  • Confirmed the nfs share is set to no_root_squash
  • Created new share in nfs server
  • Unmounted and remounted transfer share directory
  • Created Windows share still it mounted with permission as nobody:nobody on client machine
  • Configured domain name in /etc/idmapd.conf file in both nfs server and client and then restarted rpcidmapd & nfs service

Solution: 

 The solution eventually is to mount nfs volume with version 3

  • mount -t nfs -o vers=3 nfs_ip:/nfs_folder /opt/vmware/vcloud-director/data/transfer 

The ownership changed to vcloud user after that and vCD portal is accessible. It is good now to proceed with additional cell installation in the server group.

Labels:

Comments

Post a Comment

Popular posts from this blog

Deleting stale kubernetes clusters in vCD

Unlike the previous version the CSE 4.x is a stateless appliance and its data is stored in VMware Cloud Director Database.  The cluster creation and deletion compared with CSE 3.x version has improved. Besides, there are some scenarios where the cluster deletion is failing even when the "Force Delete" option is chosen. We can use vCD API explorer to delete it, the following are the API queries you can execute  Under definedEntity POST /1.0.0/entities/{id}/resolve DELETE /1.0.0/entities/{id}
Post a Comment
Read more

Manage RabbitMQ using VCP LCM

I have been working in vCD for quite some time, and most of the implementation engineers or consultants faced issues during the deployment or upgrade of RabbitMQ for the vCD message queuing service. From vCD 10.2.2, we can use the built-in MQTT client instead of RabbitMQ however, for VCD multisite configuration or some 3rd party applications need RabbitMQ, such as Veeam or VMware HCX. Using the VCP LCM, we can create a new RabbitMQ environment or manage an existing environment. The reason for this blog is that none of the VMware documentation has the information that registering an existing RMQ instance is only going to work if the RMQ instance was previously deployed by the VCP LCM (or at least, if it is a similar setup based on a Bitnami RMQ VM). Other RMQ instances (e.g., running in CentOS) are not supported and cannot be imported into the VCP LCM 1.5. I hope this information will be useful for someone who is performing green field deployment or upgrading an existing setup.  
Post a Comment
Read more