nstat_lookup_entry failed:2

so how did you fix it?

my apache refuses to start as well

Sorry,

Two things for me:

Go through your vhosts file (

/etc/apache2/extras/http-vhost.conf

chmod 777 [folder]

Hi all,

I would like other readers to know that I have tried the following to no avail:

• Switching off Remote Login, File Sharing and Screen Sharing.

• Activating the standard Firewall

• Switching off other 3rd party utilites that mayhave been phoning home

• Renaming (in the Computer Name field)

Luckily it appears my performance hits- actually stalling and hanging- were caused by - no surprise here- Flash-enabled sites. I have 5 Flash-free tabs open now and the CPU isn't dying anymore.

Same kernel here ... slows system (10.7.2). Quitting Safari (5.1.2) ... proces stops. That's one reason why I switched to Chrome.

Since a few days, my MBP hangs at startup from time to time (Apple logo and progress wheel spinning forever). So I decided to boot in verbose mode and discovered that dreaded entry in the log. After a quick search in Google, here I am.

I have file and screen sharing activated. In the Console kernel.log, "nstat_lookup_entry failed: 2" stops showing as soon as I turn off screen sharing. If I turn it back on, the message eventually comes back.

I'll see if the boot issue persists after screen sharing has been deactivated.

I would just like to chime in here to say that I received a handful of these messages (nstat_lookup_entry failed) on a laptop that is NOT running any type of server software in the logs that appear during booting it in single user mode.

So explain that! 🙂

This is very easy to explain: As long as your kernel is running, it may output this error message — even, or rather, especially when there is no network connectivity.

The only way to reliably disable this annoying message from popping up in your log file is by following Simon Heimlicher's suggestion and disabling the "net.statistics" feature of the kernel.

I'm not running Lion Server either. But turning off screen sharing did solve the problem for me. My laptop is no more stuck with the spinning wheel at startup.

I noticed something odd about the way Apple has the Postfix master daemon set up--at least in the non-server version of Lion. It is run with the options "-e" "60", which causes the daemon to exit and restart every 60 seconds.

Every time the daemon starts, it causes a couple or three "nstat_lookup_entry failed: 2" entries.

I'm not sure why the daemon would need to exit every 60 seconds; my Red Hat Enterprise Linux (and CentOS and Scientific Linux and Ubuntu) servers which run Postfix have the master daemon running continuously--no exit option (-e) specified at all.

So, since I am using Postfix, I changed /System/Library/LaunchDaemons/org.postfix.master.plist by removing the lines saying "<string>-e</string>" and "<string>60</string>".

The master daemon restarting every minute would explain some odd behaviour from Postfix I've seen; unexpected "connection refused" errors that go away when you retry.

I had the postfix error every minute of

postfix/master[1869]: warning: valid_hostname: numeric hostname: xxx.xxx.xxx.xxx

I found that in /etc/postfix/main.cf there was a line that read myhostname = xxx.xxx.xxx.xxx (my IP address). I changed that to an artibrary hostame and the console errors stopped.

I'm also not running Lion Server but I came across these nstat_lookup_entry_failed:2 errors in my logs after suddenly experiencing desktop freezes.

I did two things to stop this, but I am not 100% sure which one actually fixed it.

> First I deleted the Airport Utility.app from my Lion install as I am on a desktop with no Wifi only Wired LAN.

> Second I turned off all sharing features.

--- the reason I deleted airport is because I was seeing repeated errors relating to airport and I have no use for wifi at all.

When I have more time I will turn on sharing features one at a time and see which one of those (perhaps) brings the error back.