Setup page not working after fresh insall of vCD 8.1

[virtualg_uk]

After installing vCD I'm unable to navigate to the configured hostname/port to finish the setup. I'm getting a 404 page.

I noticed that the services had not started so I did this via:

service vmware-vcd start

But after this I have the same issue.

The cell.log file shows

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0

Bootstrap application: start

Bundle-Id: 214, Bundle-SymbolicName: jline, Bundle Location: initial@reference:file:jline/jline-2.7.jar/ - Unable to resolve bundle due to the following unsatisfied constraints: [Missing imported package org.fusesource.jansi.internal_0.0.0

]

Bundle-Id: 225, Bundle-SymbolicName: client-toolkit, Bundle Location: initial@reference:file:com/vmware/vcloud/client-toolkit/1.0.0/client-toolkit-1.0.0.jar/ - Unable to resolve bundle due to the following unsatisfied constraints: [Missing imported package com.vmware.vim.query.client_[0.0.0,1.0.0)

]

Bundle-Id: 248, Bundle-SymbolicName: cell-management-tool-vcd-client, Bundle Location: initial@reference:file:com/vmware/vcloud/cell-management-tool-vcd-client/1.5.0/cell-management-tool-vcd-client-1.5.0.jar/ - Unable to resolve bundle due to the following unsatisfied constraints: [Missing imported package com.vmware.vcloud.clienttoolkit.vc_0.0.0

]

All required system properties are present

An unspecified error occurred during application start

All required local configuration properties are present

Successfully bound network port: 80 on host address: 192.168.1.1

Successfully bound network port: 443 on host address: 192.168.1.1

Successfully bound network port: 8999 on host address: 192.168.1.1

All required local configuration properties are present

Successfully initialized system cryptography

Successfully configured HTTP SSL Connector from certificate store: /opt/vmware/vcloud-director/etc/certificates

Current locale "en" verified successfully.

Bootstrap application: complete

Application startup event: Waiting for subsystem 'com.vmware.vcloud.common.core'

Application startup event: Waiting for subsystem 'com.vmware.vcloud.cloud-proxy-server'

Application startup event: Waiting for subsystem 'com.vmware.vcloud.computeservice.broker'

Application startup event: Waiting for subsystem 'com.vmware.vcloud.consoleproxy'

Application startup event: Subsystem 'com.vmware.vcloud.cloud-proxy-server' startup initiated.

Application startup begins: Subsystem 'com.vmware.vcloud.cloud-proxy-server' at 27/02/17 17:29

Application startup event: Subsystem 'com.vmware.vcloud.common.core' startup initiated.

Application startup begins: Subsystem 'com.vmware.vcloud.common.core' at 27/02/17 17:29

Successfully connected to database: jdbc:jtds:sqlserver://192.168.1.2:1433/vcloud;socketTimeout=90

Successfully initialized system cryptography

Application Initialization: 'com.vmware.vcloud.common.core' 4% complete. Subsystem 'com.vmware.vcloud.common-cell-impl' started

Application Initialization: 'com.vmware.vcloud.cloud-proxy-server' 20% complete. Subsystem 'com.vmware.vcloud.common-cell-impl' started

Application Initialization: 'com.vmware.vcloud.cloud-proxy-server' 40% complete. Subsystem 'com.vmware.vcloud.cloud-proxy-services' started

Application Initialization: 'com.vmware.vcloud.cloud-proxy-server' 60% complete. Subsystem 'com.vmware.vcloud.hybrid-networking' started

Application Initialization: 'com.vmware.vcloud.cloud-proxy-server' 80% complete. Subsystem 'com.vmware.vcloud.hbr-aware-plugin' started

Application Initialization: 'com.vmware.vcloud.cloud-proxy-server' 100% complete. Subsystem 'com.vmware.vcloud.cloud-proxy-web' started

Application Initialization: 'com.vmware.vcloud.cloud-proxy-server' complete. Server is ready in 0:44 (minutes:seconds)

Application startup event: Subsystem 'com.vmware.vcloud.consoleproxy' startup initiated.

Successfully configured Console Proxy SSL Connector from certificate store: /opt/vmware/vcloud-director/etc/proxycertificates

Application Initialization: 'com.vmware.vcloud.common.core' 8% complete. Subsystem 'com.vmware.vcloud.common-util' started

Application Initialization: 'com.vmware.vcloud.common.core' 13% complete. Subsystem 'com.vmware.vcloud.common-sso-patch' started

Application Initialization: 'com.vmware.vcloud.common.core' 17% complete. Subsystem 'com.vmware.vcloud.api-framework' started

Application Initialization: 'com.vmware.vcloud.common.core' 21% complete. Subsystem 'com.vmware.vcloud.common-vmomi' started

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

Application Initialization: 'com.vmware.vcloud.common.core' 30% complete. Subsystem 'com.vmware.pbm.placementengine' started

Application Initialization: 'com.vmware.vcloud.common.core' 34% complete. Subsystem 'com.vmware.vcloud.vim-proxy' started

Application Initialization: 'com.vmware.vcloud.common.core' 39% complete. Subsystem 'com.vmware.vcloud.fabric.foundation' started

Application Initialization: 'com.vmware.vcloud.common.core' 43% complete. Subsystem 'com.vmware.vcloud.imagetransfer-server' started

Application Initialization: 'com.vmware.vcloud.common.core' 47% complete. Subsystem 'com.vmware.vcloud.fabric.storage' started

Application Initialization: 'com.vmware.vcloud.common.core' 52% complete. Subsystem 'com.vmware.vcloud.fabric.compute' started

Application Initialization: 'com.vmware.vcloud.common.core' 56% complete. Subsystem 'com.vmware.vcloud.backend-core-base' started

Application Initialization: 'com.vmware.vcloud.common.core' 60% complete. Subsystem 'com.vmware.vcloud.fabric.net' started

Application Initialization: 'com.vmware.vcloud.common.core' 65% complete. Subsystem 'com.vmware.vcloud.service-extensibility' started

Application Initialization: 'com.vmware.vcloud.common.core' 69% complete. Subsystem 'com.vmware.vcloud.backend-core' started

Application initialization detailed status report: 69% complete

    com.vmware.vcloud.common-cell-impl                           Subsystem Status: [COMPLETE]

    com.vmware.vcloud.common-util                                Subsystem Status: [COMPLETE]

    com.vmware.vcloud.common-sso-patch                           Subsystem Status: [COMPLETE]

    com.vmware.vcloud.api-framework                              Subsystem Status: [COMPLETE]

    com.vmware.vcloud.common-vmomi                               Subsystem Status: [COMPLETE]

    com.vmware.vcloud.jax-rs-activator                           Subsystem Status: [COMPLETE]

    com.vmware.pbm.placementengine                               Subsystem Status: [COMPLETE]

    com.vmware.vcloud.vim-proxy                                  Subsystem Status: [COMPLETE]

    com.vmware.vcloud.fabric.foundation                          Subsystem Status: [COMPLETE]

    com.vmware.vcloud.imagetransfer-server                       Subsystem Status: [COMPLETE]

    com.vmware.vcloud.fabric.storage                             Subsystem Status: [COMPLETE]

    com.vmware.vcloud.fabric.compute                             Subsystem Status: [COMPLETE]

    com.vmware.vcloud.backend-core-base                          Subsystem Status: [COMPLETE]

    com.vmware.vcloud.fabric.net                                 Subsystem Status: [COMPLETE]

    com.vmware.vcloud.service-extensibility                      Subsystem Status: [COMPLETE]

    com.vmware.vcloud.backend-core                               Subsystem Status: [COMPLETE]

    com.vmware.vcloud.vapp-lifecycle                             Subsystem Status: [WAITING]

    com.vmware.vcloud.content-library                            Subsystem Status: [WAITING]

    com.vmware.vcloud.presentation-api-impl                      Subsystem Status: [WAITING]

    com.vmware.vcloud.metrics-core                               Subsystem Status: [WAITING]

    com.vmware.vcloud.rest-api-handlers                          Subsystem Status: [WAITING]

    com.vmware.vcloud.jax-rs-servlet                             Subsystem Status: [WAITING]

    com.vmware.vcloud.ui-vcloud-webapp                           Subsystem Status: [WAITING]

Application Initialization: 'com.vmware.vcloud.common.core' 73% complete. Subsystem 'com.vmware.vcloud.vapp-lifecycle' started

Application Initialization: 'com.vmware.vcloud.common.core' 78% complete. Subsystem 'com.vmware.vcloud.content-library' started

Application Initialization: 'com.vmware.vcloud.common.core' 82% complete. Subsystem 'com.vmware.vcloud.presentation-api-impl' started

Application Initialization: 'com.vmware.vcloud.common.core' 86% complete. Subsystem 'com.vmware.vcloud.metrics-core' started

Application Initialization: 'com.vmware.vcloud.common.core' 91% complete. Subsystem 'com.vmware.vcloud.rest-api-handlers' started

Application startup event: Subsystem 'com.vmware.vcloud.computeservice.broker' startup initiated.

Application startup begins: Subsystem 'com.vmware.vcloud.computeservice.broker' at 27/02/17 17:31

Application Initialization: 'com.vmware.vcloud.computeservice.broker' 50% complete. Subsystem 'com.vmware.vcloud.backend-core-base' started

Application Initialization: 'com.vmware.vcloud.computeservice.broker' 100% complete. Subsystem 'com.vmware.vcloud.computeservice.broker' started

Application Initialization: 'com.vmware.vcloud.computeservice.broker' complete. Server is ready in 0:00 (minutes:seconds)

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. Server is ready in 2:11 (minutes:seconds)

Successfully handled all queued events.

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

and the vcloud-container-debug.log file shows:

2017-02-27 17:31:02,894 | WARN     | pring Context: com.vmware.vcloud.backend-core-base | BrokerRegistry                 | Broker localhost not started so using 53bb3a3e-43eb-41a5-a92d-840adbcb4535 instead |

2017-02-27 17:31:03,669 | WARN     | pring Context: com.vmware.vcloud.backend-core-base | BrokerRegistry                 | Broker localhost not started so using 53bb3a3e-43eb-41a5-a92d-840adbcb4535 instead |

2017-02-27 17:31:03,692 | WARN     | pring Context: com.vmware.vcloud.backend-core-base | BrokerRegistry                 | Broker localhost not started so using 53bb3a3e-43eb-41a5-a92d-840adbcb4535 instead |

2017-02-27 17:31:04,081 | WARN     | pring Context: com.vmware.vcloud.backend-core-base | BrokerRegistry                 | Broker localhost not started so using 53bb3a3e-43eb-41a5-a92d-840adbcb4535 instead |

2017-02-27 17:31:04,096 | WARN     | pring Context: com.vmware.vcloud.backend-core-base | BrokerRegistry                 | Broker localhost not started so using 53bb3a3e-43eb-41a5-a92d-840adbcb4535 instead |

2017-02-27 17:31:34,290 | WARN     | Spring Context: com.vmware.vcloud.vapp-lifecycle | StorageProfileValidationJob    | Storage profile job already scheduled. |

2017-02-27 17:31:34,885 | WARN     | Spring Context: com.vmware.vcloud.content-library | BrokerRegistry                 | Broker localhost not started so using 53bb3a3e-43eb-41a5-a92d-840adbcb4535 instead |

2017-02-27 17:31:51,072 | WARN     | pool-async-email-sender-17-thread-1 | EmailManager                   | Failed to send email because SMTP server is not configured. |

2017-02-27 17:31:54,524 | WARN     | Quartz-pool-1-thread-1    | EventDispatcherImpl            | No transaction enclosing call to postTransactionalEvent: eventType=com/vmware/vcloud/event/cell/failover |

Perhaps something has been missed on the installation?

[Sreec · Accepted solution]

DB connection and certificate mapping looks fine from the logs. Is this a centos installation, what version is it ? . Can you also ensure from network side everything is configured/working properly.

Do a nslookup against vcd console/http Ip's

Check if DNS is working correctly

Finally check centos firewall tables,if possible stop it and start the vcd service

[virtualg_uk]

CentOS 7.

nslookup, DNS all good.

Checked the firewall rules and made a small change to that and to routes and rebooted.

All good now, suspect the issue was the firewall, not sure what those errors are all abut in the logs but thanks for the assistance!