After monitoring VMware with PRTG, the database of vmware vcenter is crashing because of login / logoff events written by PRTG.

The database crashes because of the 10g limit in the express version.

Every login is been protocolled. In 15 Days we had 30000000 login / logoff events.

Is this an issue?

Article Comments

Hi,

We are working on it, but unfortunately we can not yet tell when this will be available in the stable release.


Sep, 2014 - Permalink

Same problem for several customers. Is there a solution?


Nov, 2014 - Permalink

I'm sorry but there is still work in progress. I think as a modest estimate I can give you Q2/2015. Please bear with us.

Kind regards


Nov, 2014 - Permalink

I have two questions concerning this topic:
Is there a workaround how to handle this?
Which sensors are affected by this?

Kind regards
Birk Guttmann


Apr, 2015 - Permalink

We do have VMware Sensors currently in beta phase, which use session pooling to write significantly less log entries. If you'd like to participate in this beta test, please get in touch with us with an email to support@paessler.com


Apr, 2015 - Permalink

Any update on this? Monitors for 3 hosts and 25 VMs are growing the VCDB by 4MB an hour! I already had the vCenter server crash because the DB hit the max size in SQL Express.


Jun, 2015 - Permalink

Hi, I will contact you via email soon wrx7m.

Best regards


Jun, 2015 - Permalink

Update to this issue:

Update 15.3.19 (September 2015) did implement the new VMware (SOAP) sensor:

"The VMware Datastore (SOAP) sensor monitors the disk usage of a VMware data store. This sensor type supersedes the outdated SSH VMWare ESX(i) Disk sensor. The VMware (SOAP) sensors now also support session pooling. You can define session pooling in the device settings."

- see PRTG History.


Mar, 2016 - Permalink