This week I was teaching the “What’s New” class. This is a two day course which is about upgrading ESX 2.x.x/VirtualCenter...
1.x.x to ESX 3.x.x/VirtualCenter 2.x.x. It’s also about updating people skills to the new features in Vi-3. Anyway, we had an interesting error message come up on the second day, when trying to connect the Vi Client Console to a virtual machine. The error message said “Error connecting: Error connecting to /usr/lib/vmware/bin/vmware-vmkauthd-start process. Do you want to try again?”. On checking the log files you could see the error happening:
Found vmkauthd: /usr/lib/vmware/bin/vmware-vmkauthd-start
vmware-authd: Redirected mks to 10.0.0.1:903
xinetd: START: vmware-authd pid=22871 from=10.0.0.2
vmware-authd: login from 10.48.114.182 as 527a7bfc-3d21-989c-9983-b7c10c8cb2e0
vmware-authd: Found vmkauthd: /usr/lib/vmware/bin/vmware-vmkauthd-start
vmware-authd: Failed to spawn vmkauthd (path=’/usr/lib/vmware/bin/vmware-vmkauthd-start’, loader=’(null)’)
vmware-authd: Failed to redirect mks: failed to spawn vmware-vmkauthd
mks stands for mouse, keyboard, and screen – or KVM to you and me.
Anyway, trying again didn’t seem to help. It felt a lot like some kind of timeout, perhaps with authentication. Searching on VMware’s KB didn’t raise up and immediate answers. So guy from the course (Dan Nicholas, and he works at Eli Lilly…) had a look on the VMTN Forums as he remembered seeing this problem a few months ago – apparently it affected his upgrade and his clean installations. He pretty quickly found the forum post that fixed this issue. This is it here:
First you edit the /etc/vmware/config file - and add the line vmauth.server.alwaysproxy=TRUE
then restart the vmware-vmkauthd service with service vmware-vmkauthd restart
Problem solved… Many thanks to Dan for remembering the forum post and this problem!