VMware 5.1 vCenter Appliance – Call “EventHistoryCollector.SetLatestPageSize” for object “SessionID” on vCenter Server failed.

So I noticed an issue when using the vSphere Client to connect to the VMware vCenter Server Appliance was appearing every now and again.

Call “EventHistoryCollector.SetLatestPageSize” for object “SessionID” on vCenter Server “ServerName” failed. (unfortunately didnt take a screenshot, so here’s one I found and modified).

2014-10-20_09-18-39

This issue is pretty common, and is to do with the amount of events in the database not being purged, and is covered by VMware in this KB article for windows environments.

However not so commonly covered for the vCenter Appliance which uses a progress database.

After a bit of digging around, I found the following crude solution on the VMware communities board.

So open up a console to your VCSA, login in. Run the following commands

/opt/vmware/vpostgres/1.0/bin/psql -d VCDB vc 
TRUNCATE TABLE vpx_event CASCADE;

then to exit “\q”

2014-10-20_08-59-04

If your interested in some commands for the postgres, see here, but use at your peril!
Dean
View Dean Lewis's profile on LinkedIn

10 thoughts on “VMware 5.1 vCenter Appliance – Call “EventHistoryCollector.SetLatestPageSize” for object “SessionID” on vCenter Server failed.

  1. good day
    i’m have a vm vcenter OS OpenSuse 11 and when i’m enter this command, return this error:
    /opt/vmware/vpostgres/1.0/bin/psql -d VCDB vc TRUNCATE TABLE vpx_event CASCADE;
    psql: warning: extra command-line argument “TRUNCATE” ignored
    psql: warning: extra command-line argument “TABLE” ignored
    psql: warning: extra command-line argument “vpx_event” ignored
    psql: warning: extra command-line argument “CASCADE” ignored
    psql (9.0.4)
    Type “help” for help.

    help please/

    1. Hi,

      you need to do seperate the lines

      So first

      /opt/vmware/vpostgres/1.0/bin/psql -d VCDB vc

      Then

      TRUNCATE TABLE vpx_event CASCADE;

      Please see the picture in the post as well,

    1. Cheers for that, I’ve only come across this issue once so far, but I believe when upgrading the VCSA from 5.1 to 5.5 it fills the internal hard drive, with log files.

      Slightly different to this issue, but highlights why the self contained appliance, sometimes isn’t a great thing, especially for those with little or no linux experience

Leave a Reply