nstat_lookup_entry failed:2

You are not alone. I do as well and others have reported it too...

I'll just chime in and say I'm getting the same log entries, but I don't see it actually producing any odd results unless it's tied to some other strange behavior I am seeing. But they don't seem related

+1 here

no idea what it is about

Bump...

Same here - about every three seconds. I can't isolate it. doesn't appear to be mail.

Same issue. Definitely affecting performance.

Same issue here. Hopefully nothing, but sure what this is.

I made it stop. What happened was that I built the server disk on a different machine from my server (since I already had tried an upgrade that had issues and had to restore my server from TM backup). At any rate, the Kerberos realm and ldap path were different from the hostname. I demoted my OD to standalone, promoted to master and that got everything all in sync. I had to reenter my OD entries but that didn't take long. Make sure you take an OD backup and, most importantly, keep the same UIDs for the users and groups if you recreate them. Now I just have to deal with my Lion client that won't log in to the server. TM is a life saver.

Very odd, mine match and I still get insane amounts of this in the log. I may still give it a try as it shouldn't hurt anything at the point that I am.

Interesting tidbit, Seth.

In my case, I have a standalone server with no OD services running. However, when I initially set this machine up, it was "at home" and indeed had a different name than the name it now has in the colocation facility.

I wonder if this is somehow at the root of the issue in my case as well; without OD running, I'm not sure if I have a remedy at hand as you did. I'm not too keen on starting OD just for this purpose.

Having said that, I'm also having VPN problems on this box, and wonder if it's somehow, in some twisty way, related.

I seem to have completely rid my logs of this for now, it appears. I wasn't expecting this to happen, but when I moved my server from SL to Lion, I made my new domain name the primary domain in mail. I had changed recently when a cybersqatter finally gave up on extorting money out of my company's rightful domain name, and didn't renew the domain....

Long story short, I called my ISP and had them correct my reverse DNS entry. Not long after I realized that my server stopped spamming my logs with this.

Seems Lion may be even more picky than SL was about correct PTR records.

Scratch that, the second I started to attempt to enroll my iPhone into profile manager, they spammed me again after 4 hours with 0 errors.

Great that you got a solution Tim -- alas, that's not the case with me. The forward and reverse DNS matches perfectly, but I do get the feeling that the core cause of this log entry is indeed somehow tied to system name, and that name changing. Hopefully it's harmless, but it certainly is annoying.

Well I thought I had solved it (per my above posting) but it turns out that I get the error once every 3 minutes in the kernel.log file. It did stop being so frequent. It'd be nice to track this down to why it's being called and what exactly is failing.

I've just noticed that the error also occurs while booting, and even when booting off the Recovery partition, ie. with completely standard settings and no apps running. As a result, I think it's safe to say it's a problem with Lion rather than anyone's configuration of Lion.