vSphere special agent not working after update to 1.6.0p12

Hello,

I just updated to p12 but my vSphere host reports “[special_vsphere] Agent exited with code 1: Error while processing received data

Executing the script directly on console throws this error:
Connecting to MYIP:443…Cannot login to vSphere Server. Login response is not ‘OK’. Please check the credentials.

But I haven’t changed the credentials, it worked minutes before the update…

Any thoughts?

What version is your ESX host?
I have upgraded two systems the last 2 days and had no problems with ESX hosts.

I’m running the following versions:
vSphere 6.7.0 Build 14792544 (10/24/2019)
ESXi 6.7.0 Build 14320388 (08/20/2019)

That should work. What OMD version you used before the upgrade?
You can also have a look at your host on the command line with ‘cmk -D hostname’ and use the special agent command with the debug switch or post the used command without the password.

I used p11 before.

Here is the output of the special agent:

OMD[MYSITE]:~$ /omd/sites/MYSITE/share/check_mk/agents/special/agent_vsphere --debug -u ‘checkmk@vsphere.local’ -s ‘MYPASSWORD’ -i hostsystem,virtualmachine,datastore,counters,licenses --spaces underscore --vm_piggyname alias --no-cert-check ‘MYIP’
Connecting to MYIP:443…Cannot login to vSphere Server. Login response is not ‘OK’. Please check the credentials.

I used the debug option, but can’t see any debug output :man_shrugging:

The “real” debug option is the tracefile written by this special agent.
You can define the tracefile location manually.
–debug is only good for Python errors inside the script.

1 Like

Found the solution… the password of the account was expired in vSphere.
Looks like it just expired the same time I updated checkmk :man_facepalming:

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.