Hello Team,
We are monitoring Vcentre and ESXi hosts using Vmware Virtualization Wizard. From last few days, we are getting below error for some hosts.
UNKNOWN: Server version '' at 'https://10.16.0.50:443/sdk/vimService.wsdl' unsupported.
UNKNOWN: Server version '' at 'https://10.30.0.50:443/sdk/vimService.wsdl' unsupported.
We are not sure why this error is coming.
Our nagios XI version is 5.7.3.
Could you please help us on it?
ESXi and Vcentre monitoring
-
kalyanpabolu
- Posts: 246
- Joined: Fri Jul 03, 2020 4:18 am
ESXi and Vcentre monitoring
You do not have the required permissions to view the files attached to this post.
Re: ESXi and Vcentre monitoring
What is the output of the following command:
Be sure to enter in the same USERNAME and PASSWORD that the check is configured to use.
Also:
What version of ESXi is this and what version for the VMware SDK is installed on the XI server?
Code: Select all
/usr/lib/vmware-vcli/apps/general/connect.pl --server 10.16.0.50 --username USERNAME--password PASSWORDAlso:
Code: Select all
curl 'https://10.16.0.50:443/sdk/vimService.wsdl' -kAs of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
-
kalyanpabolu
- Posts: 246
- Joined: Fri Jul 03, 2020 4:18 am
Re: ESXi and Vcentre monitoring
Hello,
Below is the output:
vi-admin@VMA-NAGIOS:~> /usr/lib/vmware-vcli/apps/general/connect.pl --server 10.16.0.50 --username [email protected] *********
Enter password:
vi-admin@VMA-NAGIOS:~> /usr/lib/vmware-vcli/apps/general/connect.pl --server 10.16.0.50 --username [email protected] --password **********
Server version '' at 'https://10.16.0.50:443/sdk/vimService.wsdl' unsupported.
vi-admin@VMA-NAGIOS:~> curl 'https://10.16.0.50:443/sdk/vimService.wsdl' -k
<HTML><BODY><H1>503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http16LocalServiceSpecE:0x00007f352c04c1a0] _serverNamespace = /sdk action = Allow _port = 8085)</H1></BODY></HTML>vi-admin@VMA-NAGIOS:~>
vi-admin@VMA-NAGIOS:~>
vi-admin@VMA-NAGIOS:~>
We didint use sdk, we are using box_293 plugin.
Below is the output:
vi-admin@VMA-NAGIOS:~> /usr/lib/vmware-vcli/apps/general/connect.pl --server 10.16.0.50 --username [email protected] *********
Enter password:
vi-admin@VMA-NAGIOS:~> /usr/lib/vmware-vcli/apps/general/connect.pl --server 10.16.0.50 --username [email protected] --password **********
Server version '' at 'https://10.16.0.50:443/sdk/vimService.wsdl' unsupported.
vi-admin@VMA-NAGIOS:~> curl 'https://10.16.0.50:443/sdk/vimService.wsdl' -k
<HTML><BODY><H1>503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http16LocalServiceSpecE:0x00007f352c04c1a0] _serverNamespace = /sdk action = Allow _port = 8085)</H1></BODY></HTML>vi-admin@VMA-NAGIOS:~>
vi-admin@VMA-NAGIOS:~>
vi-admin@VMA-NAGIOS:~>
We didint use sdk, we are using box_293 plugin.
Re: ESXi and Vcentre monitoring
Is traffic from the VMA going through a proxy? The response code is a 503 which can be caused by a proxy. What is the full output of the curl command if you run it with the verbose(-v) option ?
Is port 8085 a proxy port?
Code: Select all
curl 'https://10.16.0.50:443/sdk/vimService.wsdl' -k -vAs of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
-
kalyanpabolu
- Posts: 246
- Joined: Fri Jul 03, 2020 4:18 am
Re: ESXi and Vcentre monitoring
Hello,
I am not sure about the proxy part.
vi-admin@VMA-NAGIOS:~> curl 'https://10.16.0.50:443/sdk/vimService.wsdl' -k -v
* About to connect() to 10.16.0.50 port 443 (#0)
* Trying 10.16.0.50... connected
* Connected to 10.16.0.50 (10.16.0.50) port 443 (#0)
* successfully set certificate verify locations:
* CAfile: none
CApath: /etc/ssl/certs/
* TLSv1.0, TLS handshake, Client hello (1):
* TLSv1.0, TLS handshake, Server hello (2):
* TLSv1.0, TLS handshake, CERT (11):
* TLSv1.0, TLS handshake, Server key exchange (12):
* TLSv1.0, TLS handshake, Server finished (14):
* TLSv1.0, TLS handshake, Client key exchange (16):
* TLSv1.0, TLS change cipher, Client hello (1):
* TLSv1.0, TLS handshake, Finished (20):
* TLSv1.0, TLS change cipher, Client hello (1):
* TLSv1.0, TLS handshake, Finished (20):
* SSL connection using ECDHE-RSA-AES256-SHA
* Server certificate:
* subject: CN=pcda-vcsa.vsphere.local; C=US
* start date: 2020-03-16 04:33:38 GMT
* expire date: 2030-03-11 04:33:38 GMT
* issuer: CN=CA; DC=vsphere; DC=local; C=US; ST=California; O=pcda-vcsa.vsphere.local; OU=VMware Engineering
* SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
> GET /sdk/vimService.wsdl HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-suse-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8j zlib/1.2.7 libidn/1.10
> Host: 10.16.0.50
> Accept: */*
>
< HTTP/1.1 503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http16LocalServiceSpecE:0x00007f352c04c1a0] _serverNamespace = /sdk action = Allow _port = 8085)
< Date: Wed, 9 Dec 2020 06:05:18 GMT
< Connection: close
< Content-Type: text/html
< Content-Length: 198
<
* Closing connection #0
* TLSv1.0, TLS alert, Client hello (1):
<HTML><BODY><H1>503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http16LocalServiceSpecE:0x00007f352c04c1a0] _serverNamespace = /sdk action = Allow _port = 8085)</H1></BODY></HTML>vi-admin@VMA-NAGIOS:~>
I am not sure about the proxy part.
vi-admin@VMA-NAGIOS:~> curl 'https://10.16.0.50:443/sdk/vimService.wsdl' -k -v
* About to connect() to 10.16.0.50 port 443 (#0)
* Trying 10.16.0.50... connected
* Connected to 10.16.0.50 (10.16.0.50) port 443 (#0)
* successfully set certificate verify locations:
* CAfile: none
CApath: /etc/ssl/certs/
* TLSv1.0, TLS handshake, Client hello (1):
* TLSv1.0, TLS handshake, Server hello (2):
* TLSv1.0, TLS handshake, CERT (11):
* TLSv1.0, TLS handshake, Server key exchange (12):
* TLSv1.0, TLS handshake, Server finished (14):
* TLSv1.0, TLS handshake, Client key exchange (16):
* TLSv1.0, TLS change cipher, Client hello (1):
* TLSv1.0, TLS handshake, Finished (20):
* TLSv1.0, TLS change cipher, Client hello (1):
* TLSv1.0, TLS handshake, Finished (20):
* SSL connection using ECDHE-RSA-AES256-SHA
* Server certificate:
* subject: CN=pcda-vcsa.vsphere.local; C=US
* start date: 2020-03-16 04:33:38 GMT
* expire date: 2030-03-11 04:33:38 GMT
* issuer: CN=CA; DC=vsphere; DC=local; C=US; ST=California; O=pcda-vcsa.vsphere.local; OU=VMware Engineering
* SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
> GET /sdk/vimService.wsdl HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-suse-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8j zlib/1.2.7 libidn/1.10
> Host: 10.16.0.50
> Accept: */*
>
< HTTP/1.1 503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http16LocalServiceSpecE:0x00007f352c04c1a0] _serverNamespace = /sdk action = Allow _port = 8085)
< Date: Wed, 9 Dec 2020 06:05:18 GMT
< Connection: close
< Content-Type: text/html
< Content-Length: 198
<
* Closing connection #0
* TLSv1.0, TLS alert, Client hello (1):
<HTML><BODY><H1>503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http16LocalServiceSpecE:0x00007f352c04c1a0] _serverNamespace = /sdk action = Allow _port = 8085)</H1></BODY></HTML>vi-admin@VMA-NAGIOS:~>
Re: ESXi and Vcentre monitoring
Are you able to put https://10.16.0.50:443/sdk/vimService.wsdl in a browser and download an XML file? This is what the plugin is expecting and instead of getting the XML file it is receiving the 503 message. It looks like it is coming from the 10.16.0.50 server, in which case you'd need to check on the server side to see why it isn't being served, but there could be something like a proxy intercepting the traffic causing the issue.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
-
kalyanpabolu
- Posts: 246
- Joined: Fri Jul 03, 2020 4:18 am
Re: ESXi and Vcentre monitoring
Hello,
Thanks for your reply!!
We have asked our server team to check it, we will get back to you with the updates.
Thanks for your reply!!
We have asked our server team to check it, we will get back to you with the updates.
Re: ESXi and Vcentre monitoring
Thanks for the update. We'll wait for the next one.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
-
kalyanpabolu
- Posts: 246
- Joined: Fri Jul 03, 2020 4:18 am
Re: ESXi and Vcentre monitoring
Hello,
The website was down which was responsible for the error.
Its resolved now.
The website was down which was responsible for the error.
Its resolved now.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: ESXi and Vcentre monitoring
Great!kalyanpabolu wrote:Hello,
The website was down which was responsible for the error.
Its resolved now.
Locking thread