Esxi - Failed to establish a new connection

Troubleshooting
,
1

Hello everyone,

i am having troubles connecting my Esxi Host to Checkmk Raw 2.0.0p11 edition of Checkmk.

I’ve followed this instructions Monitoring VMWare ESXi

I have created an user with only-read permission on the esxi host and also in my vsphere center. Also I’ve created new host with hostname, ipv4 address, checkmk agent, label where the server is located

Under Setup>Agents>VM, Cloud, Container>VMWare ESX via vSphere I created rule with the read-only user and password that I have created on the Esxi Host itself (I tried both combinations also with vsphere center user that I have created). I also activated “explicit hosts” and put the name of the host that i previously created.

Connection Test:

checkmk
checkmk803×562 21.9 KB

So ping works but I cannot connect to agent because of “temporary failure in name resolution” I am asking myself why is it even trying over DNS if there is IP address of host and ping to that ip address works?

I also tried following commands:

cmk -D HOSTNAME (everything looks fine, I get type of agent and I can see credentials)
cmk --debug --discover-marked-host -vv (Nothing to do)
cmk --debug --check-discovery -vv HOSTNAME (failed to lookup IPv4 address of -vv via DNS: [Errno -2] Name or service not known)

I saw an topic here where someone deactivated SSL and then it worked for similar problem. Do I need to deactivate SSL on the Esxi Host or where?

Thank you for helping,

regards

2

Can you post the complete command for the special agent shown with “cmk -D hostname”?

3

Sure. This was output:

checkmk2
checkmk21432×355 145 KB

4

Perhaps try an explicit entry in /etc/hosts?

But in my opinion, working DNS is essential. VMware also states working forward and reverse DNS in the system requirements for just about any of their product.

5

Okay I am making progress, that worked. For testing purposes I am going to leave it like that and later I’ll try to fix this dns problem.

Now I get this error:

checkmk3
checkmk3800×182 8 KB

6

The problem is that you said the special agent should check the certificate. Then CMK uses the name “buwesx1” in your case to call the target server. I can guarantee that this is not the name inside your ESX cert :slight_smile:

7

You were right! I disabled SSL checking and now it works. Thank you! Now I need to configure everything.

8

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.