I have a device set up for a VMware vsphere client. There are sensor for each VM. All of the sensors for the VMs area down saying "session is connecting".
the probe is trying to establish a connection to the VMware servers SOAP API and that got stuck.
Please restart the probe service and check if that solves your issue.
I am also experiencing this problem. I am getting "Session is Connecting" errors every 1/2 hour or so. It seems to correct itself, but this is filling up my PRTG logs and well as generating many error messages on my ESX server. How can I determine what is causing this problem?
what is the scanning interval for your VMware sensors?
Try increasing the interval.
Hi, having the same issue here but it only started after my upgrade to PRTG8.
Scanning interval is 30 minutes and PRTG is installed also on one of these VM's and giving the same "error".
The thing is if I do a refresh after 3 minutes, the error is gone.
I had the same issue, and solved it by editing the device URL to be:
If you use http, ESXi returns an HTTP 301, which PRTG apparently doesn't always process correctly.
Hi rjst, thank you for your reply. I have implemented your suggested solution last Friday and haven't had any of these "warnings" anymoe.
This is thus a working solution for this problem.
@ Paessler: accepted solution for knowledgebase ?
Sorry, but the problem just popped up again since this morning
Servers are stressed now so probably that is why this didn't happen in weekend
Any solutions for "Session is connecting" for VMWare ESX sensor ?
Just a short note: We'll look into this issue!
Changing the communication to https seems to fix the "301 - Moved permanently" error, but doesn't fix the "Session is connecting error".
regards, Ricardo Trindade
Hi, Has a solution been found for this issue? We are having this problem with remote ESXis - restarting the probe service sometimes helps and sometimes doesn't.
Regards, Elke Pollischansky
Hi sorry but for us none of the proposed solutions is a permanent fix.
hello Paessler support ?
Hi guys. Any news / update / fix for this yet? HTTPS does not resolve issue and deleting and readding sensor does not fix it.
I resolved mine by deleting the device (whole ESX server) and then adding it again with autodiscovery. Not an ideal solution but it worked.