Hi on a new install vcloud dir 8.0 i get this error - when trying to connect and run firsttime setup - have you seen this before?
Problem accessing /. Reason:
Powered by Jetty://
Way too vague to make any sort of response to.
Can you give an overview of what you have installed (cell OS, DB, service status)?
Second, make sure you meet all minimum requirements (like forward & reverse DNS).
Most likely something was missed during initial setup/deployment.
worst case, I'd need to see logs.
Can you please make sure that vmware-vcd and watchdog services are running.
Sometime i have seen that services dies but PID exists and that causes issue.
Please share the status of service vmware-vcd status and tail -f /opt/vmware/vcloud-director/logs/cell.log
As pin-pointed by Jonathan make sure your forward and reverse DNS are setup correctly. I have seen one such issue in past where DNS was causing service unavailable issue.
For better troubleshooting can you share following info:
1: vCloud director version and build number
2: Database info ( MSSQL or any other DB)
3: DNS name resolution on all components like vCD, DB server, vCenter Server (it can be excluded if you have not set environment yet)
3: Attach following log files: vcloud-container.debug.log and vcloud-container.info.log
Same here, weird enough I have it running in a lab kit for a vCloud Director class I host for SPs this week.
Approx. 50% of the kits have the issue.
So far I could debug that it starts up to 40% according to cell.log and the starts again. Restart etc. no change...
As the conbfig on the other 50% of the kits is the same (they are clones of each other) it can't be config in general...
For some a restart helped, others still same problem... Any feedback would be great...
I had same error previously due to the DNS/naming resolution in the vCD Cell OS.
It requires to resolve both FQDN and short name.
In my case, short name was not resolved and it was fixed after I have added the search domain in the OS.
I had the same problem and mine was 2-fold ..
One was down to the host file and one to the NFS spooling area.