Currently Being ModeratedNov 2, 2013 3:35 PM (in response to neoform)
The usual trigger for these sorts of Terminal.app environment oddities is something weird in the local login scripts.
Some add-on tools can modify these bash scripts and sometimes without the user realizing it. (Errors related to PATH are one of the more common symptoms here, but all sorts of weirdness is possible.)
Usual suggestion is to see if a different login works (different user), and also to rename (mv) the usual login files away from their standard names to disable them, and closing and restarting Terminal.app.
In general and FWIW, you should not be logging in as root. At all. That's something that Apple has been discouraging for a while now.
Server.app should not be modifying the login scripts.
Currently Being ModeratedNov 2, 2013 6:45 PM (in response to MrHoffman)
Very unusually, the issue turns out to have been the ~/.ssh/authorized_keys file I created.
The permissions on the file were 644 and not 600.... somehow that was the cause of the problem. Weird.