I am trying to put down the issues and there resolutions which comes up during daily activities that will help me and also save someone’s day.
So lets start….
Issue: Appstack and writable volume attachment getting failed.
I started getting calls of user’s saying they are not getting Appstacks and Writable Volumes are also not getting attached.
So the first thing came in mind to check the VMware Appvolume Manager Logs, so logged into to the Web of Appvolume Manager and went to activity tab and then checked the System logs and below is the snippet of the logs.
Logs checked:
Appvolume Manager System logs:Apr 02 2019 10:43PM
Validating SSL certificate for “esxi1.virtgeek.local”: Rejected because certificate is neither verified nor trusted
Apr 02 2019 10:43PM
Unable to establish connection to Hypervisor <VMware ESX#25905900 root@esxi1.virtgeek.local>
Apr 02 2019 10:43PM
Failed to connect to vSphere at “root@esxi1.virtgeek.local”: SSL_connect returned=1 errno=0 state=error: certificate verify failed
Apr 02 2019 10:43PM
Validating SSL certificate for “esxi1.virtgeek.local”: Rejected because certificate is neither verified nor trusted
Apr 02 2019 10:43PM
Validating SSL certificate for “esxi1.virtgeek.local”: Rejected because certificate is neither verified nor trusted
Apr 02 2019 10:43PM
Unable to establish connection to Hypervisor <VMware ESX#25905900 root@esxi1.virtgeek.local>
Apr 02 2019 10:43PM
Failed to connect to vSphere at “root@esxi1.virtgeek.local”: SSL_connect returned=1 errno=0 state=error: certificate verify failed
Apr 02 2019 10:43PM
Validating SSL certificate for “esxi1.virtgeek.local”: Rejected because certificate is neither verified nor trusted
Apr 02 2019 10:43PM
Validating SSL certificate for “esxi1.virtgeek.local”: Rejected because certificate is neither verified nor trusted
Apr 02 2019 10:43PM
Unable to locate “Machine <VDIVM-02> (50048335-d1cc-e853-78f0-2f494c06d9b0)” on “esxi1.virtgeek.local” — Using default hypervisor instead
I was frequently seeing a single Esxi host i.e. esxi1.virtgeek.local with error Rejected because certificate is neither verified nor trusted.
Now we have seen the issue and also the logs, so it’s time to get it resolved as quickly as possible.
Here is what i did to get it resolved :
1) First check the credential which is given in Appvolume Manager for ESXi host and Actual Credential of ESXi host is same. If not you have to change the password of ESXi.
You need to check the credential of the hosts which is coming up in the logs.
2) If credentials are same for host in Appvolume Manager and ESXi host, go to next step.
3) Login to Appvolume webpage
4) Go to Configuration Tab –> Machine Managers —> Expand vCenter and Click on Edit.
5) Uncheck Mount on host and mount on local.
6) Enter vCenter credentials and click on Save.
7) Wait for couple of Minutes
8) Again go to Machine Managers, click on Mount on host and give ESXi credentials and for vCenter give vCenter credential.
Woooohoooo !!!!! The issue should get resolved with this.
You owe me a beer 🙂 if this helps you someday 😉
If you want to know what caused it to resolve, please read below :
Unchecking the mount on host will remove the host certificate from appvolume database and thereafter again checking the mount on host option will update the host certificates in the database and thereafter appvolume will start proper communication with the host and this helped to resolve the problem.
I would be more than happy to reply to your queries.
Rajesh Poojary
Where to find me 😉
Twitter : @RajjeshPoojary
Mail : Rajjesh.poojary@gmail.com