hi everybody,
i have just installed to VCSA 6.0 on my environment after first boot i got this error on home screen """failed to start servies. Firstboot Error."
and i can ping but i cant connect it via web browser, i thought some services dosent start but i am not sure how can i check it ?
which tool is more usefull ? Putty or PowerCLI ?
You can use putty to go through the firstboot logs. If possible kindly provide the firstboot logs...
You can use putty to go through the firstboot logs. If possible kindly provide the firstboot logs...
which command i should run firstly to check it ?
Firstboot script execution Error.
The supplied System Name vcenter01.domain.local is not valid. -- ? what is not valid ?
Logs can be found at C:\Users\user\AppData\Roaming\VMware\vSphere\vcsa\sessions\session
i just fixed it...it is about DNS records...i set host a record on dns before install it and now it works well...
thank you.
Oh come on VMware... nobody got this error on testing? Same issue, same fix...
Stupid little things like this are exactly why I'm demoing the product and not installing it on production.
They are just no-brainers but they still get missed.
dbutch1976 wrote:
Oh come on VMware... nobody got this error on testing? Same issue, same fix...
Same here, can't get it to work ... During boot - you can hit ESC to see the console session during bootup - and a lot, if not all services, are failing .. .
That is with a fresh deployment ... Clearly something is dodgy ...
Thanks for posting. I just had that same exact issue (did not create the DNS record for the FQDN I gave the appliance before install).
DNS record for the FQDN worked for me too!
For the record guys, this is in the release notes under the Upgrade/Install Section. https://www.vmware.com/support/vsphere6/doc/vsphere-esxi-vcenter-server-60-release-notes.html#instal... . We're working on getting it sorted out.
Just for information,
I don't have any DNS in my new infrastructure, So an other way to get it work is to set the name machine as "localhost" during the installation process.
try using the hosts file on the machine your deploying it from
Pricing, abominable certification experience and crap like this makes me look at Hyper-V to replace VMware in the short term, meaning as soon as I get my hands on a couple of servers we just decommissioned. vSphere has been nice but VMware dropped the ball too many times, I'm not waiting to see them pick it up again.
Thank you malasfar - This worked for me - adding manual entry into local hosts file of Windows machine that I was deploying the PSC from - even though domain DNS was resolving 100%, forward + reverse for the appliance name/IP.
Now PSC appliance deploys successfully, and starts without the firstboot error = happy days!
Hi Firstbyte, can you tell me what you did in the hosts file and in which machine? i have the same error and i cannot fix it. i am new with VMWare.
Someone can explain me what i need to do in the hosts file and in which machine to fix this issue? i am new and i am trying to understand.
Having same issue. Let us know what needs to be added to the hosts file.
Additional things to check if the hosts file is not working for you...disable IPv6 on the client station you are installing VCSA from...if it's not in use...to ensure dns does not try to resolve via IPv6, which will return a null result if you don't have it setup. Also, if you are installing into a nested environment, ensure promiscuous mode is enabled on the vswitch port group and that the portgroup vlan is correct.
i just added the ip for the system name instead of a name and it worked
step 9