Hi, we first experienced experienced this problem a few weeks ago. All of a sudden, on 3 different macs (Mac Pro 10.5.4 OS X Server, Mac Pro 10.5.4, and 2004 xserve, 10.4.* OS X Server), within the space of a few days, the 3 machines' were incapable of launching a shell.
In all cases, I would not get a login prompt.
I tried from different users accounts that have different default shells (bash vs. tcsh). I tried changing the login shell from default to tcsh to zsh.
This I find to be very bizarre. I don't know what the commonality is for those applications. I don't think there is a common .login script that is used.
The computers otherwise seem to be working fine. I have web services, mysql, applications all seeming to work normally.
I can't see anything suspicious in my Console log files.
Last time I solved the problem on the 3 compouters by rebooting. But it has happened again (2-3 weeks later). This time I am tempted to let it be for a while until I come up with a possible solution that I can try (but not having remote access to the machine is not something that I can sustain.)
Anyone have a clue?
- When I try to log in to the machine through ssh remotely, after receiving my password, the terminal hangs.
- Terminal hangs on launch
- iTerm hangs on launch
- xterm hangs on launch
- Double clicking on tcsh, csh or ksh from Finder in /bin launches a Terminal window that hangs.
In all cases, I would not get a login prompt.
I tried from different users accounts that have different default shells (bash vs. tcsh). I tried changing the login shell from default to tcsh to zsh.
This I find to be very bizarre. I don't know what the commonality is for those applications. I don't think there is a common .login script that is used.
The computers otherwise seem to be working fine. I have web services, mysql, applications all seeming to work normally.
I can't see anything suspicious in my Console log files.
Last time I solved the problem on the 3 compouters by rebooting. But it has happened again (2-3 weeks later). This time I am tempted to let it be for a while until I come up with a possible solution that I can try (but not having remote access to the machine is not something that I can sustain.)
Anyone have a clue?
Last edited: