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


vmware SOAP - timeout (Code: PE018)

Votes:

0

Your Vote:

Up

Down

Hi There,

Since yesterday, getting error on vmware SOAP collector timeout (Code: PE018).

if I do snmpwalk, able to see the data returned. Any idea?

pe018 soap vmware

Created on Nov 20, 2015 9:58:39 AM by  abhishekg (0) 1



10 Replies

Votes:

0

Your Vote:

Up

Down

Hello,
we appreciate your contact.

  • Which exact sensor(name) and version of PRTG are you using?
  • Are you monitoring an ESXi host or vCenter?

PE018 is a generic "Timeout" error, it can have several distinct source causes.

Kindly also note that the ...(SOAP) sensors rely on VMware's SOAP API (Simple Object Access Protocol) and not on the SNMP.

Best Regards,

Created on Nov 23, 2015 12:33:08 PM by  Luciano Lingnau [Paessler Support]

Last change on Nov 23, 2015 12:34:30 PM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

It is VMware Virtual Machine (SOAP) and monitoring individual ESXi hosts.

Surprisingly, error started for multiple hosts at a same time and no changes are made on either side.

Created on Nov 24, 2015 6:12:28 AM by  abhishekg (0) 1



Votes:

0

Your Vote:

Up

Down

Hello abhishekg,
thank you for your reply.

  • Which exact version of PRTG are you using? (You can check it on PRTG's footer bar (e.g. PRTG Network Monitor 15.4.19.4197)

Please perform the following:

  1. Within PRTG, head to the sensor's parent device (The ESXi host), and on it's settings tab, configure the Credentials for VMware/XenServer, set the Session Pool to Create a new session for each scan. You'll also have to re-enter the VMWare credentials when doing so.
  2. Within the settinfs from one of the affected [[https://www.paessler.com/manuals/prtg/VMware Virtual Machine (SOAP)|sensors]], configure the Debug Options, set the Sensor Result to Write sensor result to disk .
  3. After the next sensor's scan, head to the following folder on the Probe Server which monitors the sensor: "C:\ProgramData\Paessler\PRTG Network Monitor\Logs (Sensors)\" and kindly share with us the contents of the "Result of Sensor [ID].txt".

Best Regards,

Created on Nov 24, 2015 8:13:07 AM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Version is 15.4.20.4775+.

I will generate the debug logs and post it.

Thanks...

Created on Nov 24, 2015 10:29:31 AM by  abhishekg (0) 1



Votes:

0

Your Vote:

Up

Down

This what I can see in the log file but starting over again and again:

0:16:08:44.0344241:
starting
######
Starting WebServiceCall with parameters:

soapBody: <RetrieveServiceContent xmlns="urn:vim25"><_this type="ServiceInstance">ServiceInstance</_this></RetrieveServiceContent>

0:16:09:05.1125729:
ResponseFilter: soapenv:Body
######
0:16:09:05.1125729:
Initializing WebRequest
######

Created on Nov 24, 2015 10:40:36 AM by  abhishekg (0) 1

Last change on Nov 24, 2015 12:07:28 PM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Thank you for the provided details.

  • Which version of ESXi are you running? Kindly note that the latest releases of PRTG no longer support older versions of ESXi, only versions 5.0, 5.1, 5.5, or 6.0 are currently supported.
  • Since you've mentioned that you have several VMWare Sensors and those sensors have a high performance impact, kindly increase their scanning interval to at least 5 minutes, does the behavior change then? (You can change the interval of hundreds of sensors at once using Multi-edit.
  • Please review the Probe's log (Path: c$\ProgramData\Paessler\PRTG Network Monitor\Logs (System)\PRTG Probe Log *.log, are there any recent entries similar to the below?
08/10/2015 04:32:40 Limit of 100 parallel .exe - Sensors reached for 1 times. DROPPING SEVERAL REQUESTS for system stability.
  • A restart of the affected ESXi may also resolve the issue in some cases.

Best Regards,

Created on Nov 24, 2015 12:24:24 PM by  Luciano Lingnau [Paessler Support]

Last change on Nov 24, 2015 12:24:44 PM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

We are running with VMware ESXi 5.5.0 build-1331820

I checked the mentioned logs but did not find any similar errors in that.

Let me try restarting all management services on ESX host.

Created on Nov 25, 2015 5:19:34 AM by  abhishekg (0) 1



Votes:

0

Your Vote:

Up

Down

Hi,

even after restarting services on ESXi, it is not working.

Any idea?

Created on Nov 25, 2015 12:50:17 PM by  abhishekg (0) 1



Votes:

0

Your Vote:

Up

Down

Hello,

In this case kindly open a Support Ticket, we'll need to check your PRTG's logs and understand your setup a little further to be able to explain what is happening.

Best Regards,

Created on Nov 25, 2015 1:01:05 PM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

After restarting ESXi host where prtg is installed everything is working fine.

Created on Nov 27, 2015 10:12:55 PM by  abhishekg (0) 1



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.