New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

300.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


What is happening when a sensor says "session is connecting"

Votes:

0

Your Vote:

Up

Down

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".

alarm prtg vmware

Created on Mar 24, 2010 2:43:14 PM by  Bob Walters (0) 1



13 Replies

Accepted Answer

Votes:

0

Your Vote:

Up

Down

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.

Created on Mar 25, 2010 8:08:48 AM by  Aurelio Lombardi [Paessler Support]



Votes:

0

Your Vote:

Up

Down

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?

Created on Sep 15, 2010 3:22:39 AM by  John Foley (0)



Votes:

0

Your Vote:

Up

Down

what is the scanning interval for your VMware sensors?

Try increasing the interval.

Created on Sep 30, 2010 7:05:33 AM by  Aurelio Lombardi [Paessler Support]



Votes:

0

Your Vote:

Up

Down

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.

Thx

Created on Oct 18, 2010 12:01:53 PM by  Robby Ulens (0)



Votes:

0

Your Vote:

Up

Down

I had the same issue, and solved it by editing the device URL to be:

https://x.x.x.x

instead of

http://x.x.x.x

If you use http, ESXi returns an HTTP 301, which PRTG apparently doesn't always process correctly.

Created on Oct 21, 2010 9:03:45 AM by  rjst (0)



Votes:

0

Your Vote:

Up

Down

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.

Thanks again

@ Paessler: accepted solution for knowledgebase ?

Created on Oct 25, 2010 7:11:24 AM by  Robby Ulens (0)



Votes:

0

Your Vote:

Up

Down

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 ?

Created on Oct 26, 2010 10:28:59 AM by  Robby Ulens (0)



Votes:

0

Your Vote:

Up

Down

Just a short note: We'll look into this issue!

Created on Nov 1, 2010 9:39:06 AM by  Dirk Paessler [Founder Paessler AG] (10,922) 3 4



Votes:

0

Your Vote:

Up

Down

Hi,

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

Created on Nov 2, 2010 2:57:49 PM by  rjst (0)



Votes:

0

Your Vote:

Up

Down

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

Created on Dec 30, 2010 3:45:56 PM by  Elke Pollischansky (0) 1



Votes:

0

Your Vote:

Up

Down

Hi sorry but for us none of the proposed solutions is a permanent fix.

hello Paessler support ?

Created on Jan 6, 2011 8:40:16 AM by  Robby Ulens (0)



Votes:

0

Your Vote:

Up

Down

Hi guys. Any news / update / fix for this yet? HTTPS does not resolve issue and deleting and readding sensor does not fix it.

Created on Feb 25, 2011 6:51:42 AM by  Andre Swigon (0) 2



Votes:

0

Your Vote:

Up

Down

I resolved mine by deleting the device (whole ESX server) and then adding it again with autodiscovery. Not an ideal solution but it worked.

Created on Feb 25, 2011 7:23:47 AM by  Andre Swigon (0) 2



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.