When I open Terminal, I get an “I have no name!” prompt

Question

Suddenly, this morning, I open a Terminal window and I get this:

I have no name!@macbook:~$ whoami
502

** I am not a number! I am a human being! **

What gives? Anyone know what I need to do to get my name back?

I suppose there are two problems here, one is that my hostname is undefined, the other is that whoami reports my name as a number.

Answer 1

Something in memory got corrupted, and the mapping between your userID (502) and your username (ipd) was lost. I've seen it happen (usually when I've manually killed hung system processes), although I'm not sure exactly what causes it. launchd maybe?

Because that mapping is lost, whoami can't convert your ID into a username so returns the ID, and your prompt defaults to the "I have no name!" message because you effectively don't have a name.

Logging out and back in might fixit, but restarting is the best way (as you discovered).

Basically, it's a symptom of another problem, and not a problem in and of itself.

Answer 2

I see it's an old thread, but here is the solution to this problem (without restarting the whole computer).

The problem is in the opendirectoryd daemon and the earliest reports date from the beginning of 2011. Restarting the daemon (switching users with an admin one via Fast User Switching) fixes the problem.

While writing this answer, I've found a similar question in the Serverfault here, which also covers my answer.

Answer 3

This happens to me randomly when I resume from standby (ie opening my laptop). A log out or reboot is the only way for me to fix it. I dont know exactly what causes it. As I type it is happening right now. As the comment in the original post asked, I ran id -p and it crashed. (Crash report: http://pastebin.com/nmFFQELq)

Console commands: whoami - returns 501

id -p - crashes

cat /etc/passwd - my user is not in the document.

any ssh attempt fails with the error: You don't exist, go away!

I also checked out the console, from waking up, a bunch of random "Socket not connected" errors appear (which I think might be normal, being that wireless doesnt connect immediately) from programs like dropbox. An interesting error appears though:

4/12/12 8:37:09.045 PM coreservicesd: _scserver_ServerCheckin: client uid validation failure; getpwuid(501) == NULL

4/12/12 8:37:09.400 PM coreservicesd: _scserver_ServerCheckin: client uid validation failure; getpwuid(501) == NULL

Still not sure what is causing it, but thought I would share these diagnostics.

Im on a Mid 2009 MacBook Pro with 10.7.3 installed

Answer 4

I solved the problem by using iterm=>preferences=>URL_handler and connecting whoami to my username .. after restart on iterm, problem was no more

Answer 5

See if the permissions of the file /etc/passwd are set up like this:

-rwxr--r--

because it reads the user name from the passwd file.

Answer 6

Go to the home folder in Terminal and run . ~/.bashrc.

It works!!