ThorstenT
Contributor
Contributor

Strange errors in vCenter log

Hi,

I have a local administrative account named vcroot, which logs in and out of vCenter almost every second. This causes the event tables in the database to grow by tens of thousands rows per day, which is rather unpleasant.

[2010-06-16 11:03:35.548 02412 info 'App'] [VpxLRO] -- BEGIN task-internal-4421921 --  -- vim.SessionManager.login -- 555CACFB-5348-4073-BEC1-9E96EB459FF0
[2010-06-16 11:03:35.548 02412 info 'App'] [Auth]: User vcroot
[2010-06-16 11:03:35.548 02412 info 'App'] [VpxLRO] -- FINISH task-internal-4421921 --  -- vim.SessionManager.login -- 555CACFB-5348-4073-BEC1-9E96EB459FF0
[2010-06-16 11:03:35.563 02176 info 'App'] [VpxLRO] -- BEGIN task-internal-4421922 --  -- vim.ServiceInstance.retrieveInternalContent -- 555CACFB-5348-4073-BEC1-9E96EB459FF0(6F35446A-A114-488E-8D9F-AD472AE30179)
[2010-06-16 11:03:35.563 02176 info 'App'] [VpxLRO] -- FINISH task-internal-4421922 --  -- vim.ServiceInstance.retrieveInternalContent -- 555CACFB-5348-4073-BEC1-9E96EB459FF0(6F35446A-A114-488E-8D9F-AD472AE30179)
[2010-06-16 11:03:35.563 02260 info 'App'] [VpxdHostSync] Retrieved host update to 5011
[2010-06-16 11:03:35.563 02172 info 'App'] [VpxLRO] -- ERROR task-internal-4421923 --  -- vim.DiagnosticManager.browse: vmodl.fault.InvalidArgument:
(vmodl.fault.InvalidArgument) {
   dynamicType = <unset>, 
   faultCause = (vmodl.MethodFault) null, 
   invalidProperty = "key", 
   msg = "", 
}
[2010-06-16 11:03:35.563 02464 info 'App'] [VpxLRO] -- BEGIN task-internal-4421924 --  -- vim.SessionManager.logout -- 555CACFB-5348-4073-BEC1-9E96EB459FF0(6F35446A-A114-488E-8D9F-AD472AE30179)
[2010-06-16 11:03:35.579 02464 info 'App'] [VpxLRO] -- FINISH task-internal-4421924 --  -- vim.SessionManager.logout -- 555CACFB-5348-4073-BEC1-9E96EB459FF0(6F35446A-A114-488E-8D9F-AD472AE30179)

Anybody got an idea?

Thanks,

Thorsten

PS: vCenter ist 4U2, the problem existed before the update as well.

Tags (2)
0 Kudos
1 Reply
ThorstenT
Contributor
Contributor

Obviously VIMA remote logging was the problem. Reconfiguring the remote log facility solved the problem.

The VIMA log mechanism regarding vCenter does not seem to be very robust... Retrying every second is not the best way to handle an error :).

Now I only got to remove 20 million rows from the database...

0 Kudos