VMware Cloud Community
ITRC_Architect
Contributor
Contributor

vCenter log filling up with these info messages - please help diagnose

This set of messages is occurring over and over again in the logs, nonstop about every 300ms.

Any ideas on fixing it or even how to isolate the problem to stop the logs from filling up with this information?  This can't be good...

Thank you in advance.

[2011-03-01 09:39:52.196 05212 info 'Libs' opID=2e204a4c] [ADS] Account _myuser found, but not local

[2011-03-01 09:39:52.197 05212 info 'App' opID=2e204a4c] Error 1326 authenticating user .\_myuser.

[2011-03-01 09:39:52.292 05212 info 'App' opID=2e204a4c] [Auth]: User HSEN\_myuser

[2011-03-01 09:39:52.292 05212 info 'Libs' opID=2e204a4c] [ADS] GetTokenInformation failed: 1312

[2011-03-01 09:39:52.292 05212 info 'Libs' opID=2e204a4c] [ADS] GetTokenInformation failed: 1312

[2011-03-01 09:39:52.292 05212 info 'App' opID=2e204a4c] [VpxLRO] -- FINISH task-internal-5641 --  -- vim.SessionManager.login -- 061A68D2-3083-4C8D-B064-AD4FDFA38688(016DB9C3-7F94-4A59-A2D4-8D7CF9582029)

[2011-03-01 09:39:52.294 05212 info 'App' opID=759e76dc] [VpxLRO] -- BEGIN task-internal-5642 --  -- vim.PerformanceManager.queryProviderSummary -- C5519B5D-EC6E-445A-B9B9-80C182B0CA44(0E70CCCC-3ACD-486D-B963-5D9BCE8B24D4)

[2011-03-01 09:39:52.295 05212 info 'App' opID=759e76dc] [VpxLRO] -- FINISH task-internal-5642 --  -- vim.PerformanceManager.queryProviderSummary -- C5519B5D-EC6E-445A-B9B9-80C182B0CA44(0E70CCCC-3ACD-486D-B963-5D9BCE8B24D4)

[2011-03-01 09:39:52.297 06300 error 'App' opID=2898c886] vmodl.fault.InvalidArgument

[2011-03-01 09:39:52.298 06300 info 'App' opID=2898c886] [VpxLRO] -- ERROR task-internal-5643 --  -- vim.DiagnosticManager.browse: vmodl.fault.InvalidArgument:

Result:

(vmodl.fault.InvalidArgument) {

   dynamicType = <unset>,

   faultCause = (vmodl.MethodFault) null,

   invalidProperty = "key",

   msg = "",

}

Args:

Arg host:

Arg key:

"vpxd:vpxd-60214.log"

Arg start:

7999

Arg lines:

100

[2011-03-01 09:39:52.301 04720 info 'App' opID=810325cd] [VpxLRO] -- BEGIN task-internal-5644 --  -- vim.SessionManager.GetCurrentSession -- 061A68D2-3083-4C8D-B064-AD4FDFA38688(016DB9C3-7F94-4A59-A2D4-8D7CF9582029)

[2011-03-01 09:39:52.301 04720 info 'App' opID=810325cd] [VpxLRO] -- FINISH task-internal-5644 --  -- vim.SessionManager.GetCurrentSession -- 061A68D2-3083-4C8D-B064-AD4FDFA38688(016DB9C3-7F94-4A59-A2D4-8D7CF9582029)

[2011-03-01 09:39:52.304 05784 info 'App' opID=4edea7c0] [VpxLRO] -- BEGIN task-internal-5645 --  -- vim.SessionManager.logout -- 061A68D2-3083-4C8D-B064-AD4FDFA38688(016DB9C3-7F94-4A59-A2D4-8D7CF9582029)

[2011-03-01 09:39:52.304 05784 info 'App' opID=4edea7c0] [VpxLRO] -- FINISH task-internal-5645 --  -- vim.SessionManager.logout -- 061A68D2-3083-4C8D-B064-AD4FDFA38688

[2011-03-01 09:39:52.307 06300 info 'App' opID=8b0d61f1] [VpxLRO] -- BEGIN task-internal-5646 --  -- vim.SessionManager.GetCurrentSession -- 0B3867BD-0310-4663-B4F1-0206CB81CF2D

[2011-03-01 09:39:52.307 06300 info 'App' opID=8b0d61f1] [VpxLRO] -- FINISH task-internal-5646 --  -- vim.SessionManager.GetCurrentSession -- 0B3867BD-0310-4663-B4F1-0206CB81CF2D

[2011-03-01 09:39:52.324 05784 info 'App' opID=bace3050] [VpxLRO] -- BEGIN task-internal-5647 --  -- vim.ServiceInstance.GetContent -- 189FE308-092B-412A-9B48-8E99AD7251C0

[2011-03-01 09:39:52.325 05784 info 'App' opID=bace3050] [VpxLRO] -- FINISH task-internal-5647 --  -- vim.ServiceInstance.GetContent -- 189FE308-092B-412A-9B48-8E99AD7251C0

[2011-03-01 09:39:52.336 06300 info 'App' opID=181abb67] [VpxLRO] -- BEGIN task-internal-5648 --  -- vim.SessionManager.GetCurrentSession -- 189FE308-092B-412A-9B48-8E99AD7251C0

[2011-03-01 09:39:52.336 06300 info 'App' opID=181abb67] [VpxLRO] -- FINISH task-internal-5648 --  -- vim.SessionManager.GetCurrentSession -- 189FE308-092B-412A-9B48-8E99AD7251C0

[2011-03-01 09:39:52.339 05212 info 'App' opID=35e72191] [VpxLRO] -- BEGIN task-internal-5649 --  -- vim.SessionManager.login -- 189FE308-092B-412A-9B48-8E99AD7251C0

0 Kudos
1 Reply
ITRC_Architect
Contributor
Contributor

We found the culprit.

vMA was trying to connect to vCenter Server to collect logs.  When it failed, it just kept on trying...

0 Kudos