[Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 505
  • Last Modified:

Vmware hatast-ha-host-vim.hos....

I have this error in my logs, all servers...

[2014-08-21 14:33:29.027 13D00B90 verbose 'App'] Looking up object with name = "haTask-ha-host-vim.HostSystem.acquireCimServicesTicket-615951" failed

the only thing that changes is the ticket numbers.
0
wlacroix
Asked:
wlacroix
  • 5
  • 4
1 Solution
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
and is everything working correctly, as it should.....
0
 
wlacroixAuthor Commented:
Seems to be, there are other similar entries with success, but far more failures than successes.

Its not just a few either, its several.
Despite my googles I cant find much on that error at all.
0
 
compdigit44Commented:
Is it happening on all host or just one? What build of ESXi4.1 are you running?
0
Threat Trends for MSPs to Watch

See the findings.
Despite its humble beginnings, phishing has come a long way since those first crudely constructed emails. Today, phishing sites can appear and disappear in the length of a coffee break, and it takes more than a little know-how to keep your clients secure.

 
wlacroixAuthor Commented:
Yes all hosts have this message but not all of them are in a failed state.

VMware 4.1

988178
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
I think if you dig deep enough in VMware Logs, you'll find all sorts of errors and issues....

but if everything has been tested and working......?
0
 
wlacroixAuthor Commented:
Andrew yes your absolutely right, but which ones do you investigate?

I have other techs that bring errors to me all the time, 90% of them are moot.

Just understanding what some of them are so I can rule them out is half the battle.

So if its not reported in vcenter we should not worry about it as much?
Takes a lot of time to google some of them. Without resolution
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
We currently have 283 outstanding faults with VMware vSphere! (that can be reproduced!)

We do not go through the kernel logs, escalating ALL errors, *UNLESS* there is a fault, that can be seen and reproduced in vCenter Server/ESXi. (we have too much on, to do this!!).

and then logs are processed and reviewed.

There is a lot of internal chatter between hosts/vCenter Server, which is noise!

So, unless you have a reproducible fault, I would go looking in the logs, trying to find a fault...
0
 
wlacroixAuthor Commented:
That makes sense for sure, I do have an error that I am working on with a loss in volumes.
I am now trying to reproduce it like you said, if we can reproduce it we can fix it :)

The one in this thread I think is moot, and I am going to award you the points on it because I feel your 100% right.
If we cant reproduce it, or its something that is rearing its ugly head regularly, then I dont have time to look into all 282 faults! hehe.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
We managed many many hosts at the DC, all logs come into a central Splunk database from all Hosts, and you would be surprised of the amount of chatter, and errors that appear, that appear to be moot!
0
 
wlacroixAuthor Commented:
This error is nothing to worry about
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now