Hi, I have the message "Timeout caused by wait for mutex. Consider distributing your VMware sensors across several probes! PE121"

I read the topic "30643-how-can-i-increase-the-connection-limit-on-vmware-systems-pe121" but i don't have a Vcenter. I just have a ESXi 5.1 with 175 VM and PRTG 13. I'm not find the value "Perf.Stats.MaxCollectionThreads" in Vsphere client.

Can you help me ?

Thanks Anthony

Article Comments

Hi Anthony,

you are right, these setting is not available on the hosts itself.
Which version of PRTG are you using? In 13.4.7.3531 we introduced new, higher performing VMWare SOAP-Sensors. If you are using an older version of PRTG please update to the latest stable version.

Did you check the .Net-Update mentioned in the topic?
Which scaninterval are you using?

Kind regards

Dieter


Jan, 2014 - Permalink

hi!

I have this problem since last night on a customer's PRTG server. Version 16.4.27.6720+ on a Windows 2012 R2 Server with .NET 4.5 installed - so I think the .Net-update won't be applicable ... I set the Perf.Stats.MaxCollectionThreads to 16 although I think that this won't help, as we monitor the ESX-Host directly.

Since several hours 2 out of 14 sensors get the same error "Timeout caused by wait for mutex. Consider distributing your VMware sensors across several probes! See https://helpdesk.paessler.com/en/support/solutions/articles/76000063102 for more information. (code: PE121)": the "VMware Datastore (SOAP)" sensor -> prim. channel: "Free Space (%)" and the "VMware Host Performance (SOAP)" -> prim. channel: "CPU usage (%)". First we forgot to change the "default" scanning interval of 60 seconds, but with a new interval of 5 minutes nothing changes ... Any other ideas or suggestions or should I open up a support case?

Thanks, Clemens


Nov, 2016 - Permalink

The sensors were paused the whole weekend and today I resumed both - after several minutes just "no data" ...

So I cloned the first sensor and ... cool ... it was green immediatly ... with the second one the same ... interesting! ;)


Nov, 2016 - Permalink

Hello Clemens,

unfortunately, we currently do not have a distinct answer/explanation for this.

If the issue re-occurs, please open a support ticket including the probe state files. Please perform the following procedure on your Core Server which will generate additional logs:

  • Within PRTG head to Setup > Administrative Tools and select "Write Probe Status Files".
  • Please repeat step 1) 3 times with a 30 seconds interval
  • To upload the Probe State files and the PRTG system logs to our FTP server, use the button "Send Logs to Paessler..." on the Tab "Logs and Infos" in the "PRTG Administration Tool". Please enter the Ticket-ID (PAE782247) into the related text-field.

Kind regards, Sven


Nov, 2016 - Permalink

Hello Sven,

thank you for your answer.

I'll do so, if the problem occurs again!

Kind regards, Clemens


Nov, 2016 - Permalink