Benches macOS

17

Terminal: "Process Completed"

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

Hi!

I found this:

http://discussions.apple.com/thread.jspa?threadID=1966373

But fixing permissions didn't help, and I don't see any files in var/log. This is just after a new installation of OS 10.6.4.

Any other ideas for fixing my Terminal?

Message was edited by: Almo2001

17 replies

Sign in or join Beachball Help to reply.

  1. 0

    BobHarris

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Download and install iTerm (free download)

    <http://iterm.sourceforge.net/&gt;

    See if the problem occurs with this terminal emulator. If it does, then it is something external to the terminal emulator. Think /etc/profile, the shell, some .bash* file in your home directory (which you will not be able to see from the Finder), some part of your home directory that has poorly set permissions, etc...

    If it works, then it might be something specific to Terminal. If iTerm does work, then you might try installing a new version of Terminal using Pacifist

    <http://www.versiontracker.com/dyn/moreinfo/mac/12743&gt;

    and your installation DVD.

  2. 0

    William Boyd, Jr.

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Almo2001 wrote:

    iTerm doesn't work either. Since I can't run a shell, how do I go in to look for these bad files of which you speak?

    You actually can see those files in the Finder. Use the Finder's menu option "Go -> Go to Folder, type "/etc" (without the quotes) into the field, then click "Go". Files I see that might be causing trouble are bashrc and profile, although there may be others. Privileges could cause trouble for moving and/or modifying those files from your normal account. If that's the case I'd suggest logging in as root (
    http://support.apple.com/kb/HT1528).

  3. 0

    Almo2001

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I've done a bunch more hunting, and tried:

    Trashing Terminal prefs. Setting a different shell (I'm using /bin/bash). I get slightly different messages, like "process exited - exit code 1". changing advanced options on my account to use a different shell.

    Still nothing.

  4. 0

    William Boyd, Jr.

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Almo2001 wrote:

    I found this:

    http://discussions.apple.com/thread.jspa?threadID=1966373

    But fixing permissions didn't help, and I don't see any files in var/log. This is just after a new installation of OS 10.6.4.

    Any other ideas for fixing my Terminal?

    I'd create another administrative user and see if the same problem exists for that user. If it doesn't, then the problem is probably due to "dot" file in your original user's home directory. You could use the "ls -a" command to identify the "dot" files in the original home directory, then use the "diff" command in Terminal to compare the versions in the old and new directories. If you spot a difference, then you can work on fixing it.

  5. 0

    Almo2001

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Ok, I made a new admistrative user, and I get the same problem when starting Terminal. 😟

    Message was edited by: Almo2001

  6. 0

    BobHarris

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Download and install iTerm (free download)

    <http://iterm.sourceforge.net/&gt;

    See if the problem occurs with this terminal emulator. If it does, then it is something external to the terminal emulator. Think /etc/profile, the shell, some .bash* file in your home directory (which you will not be able to see from the Finder), some part of your home directory that has poorly set permissions, etc...

    If it works, then it might be something specific to Terminal. If iTerm does work, then you might try installing a new version of Terminal using Pacifist

    <http://www.versiontracker.com/dyn/moreinfo/mac/12743&gt;

    and your installation DVD.

  7. 0

    Almo2001

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    iTerm doesn't work either. Since I can't run a shell, how do I go in to look for these bad files of which you speak?

    Lest that sound flippant, I'm very appreciative of your help. 🙂

  8. 0

    William Boyd, Jr.

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Almo2001 wrote:

    iTerm doesn't work either. Since I can't run a shell, how do I go in to look for these bad files of which you speak?

    You actually can see those files in the Finder. Use the Finder's menu option "Go -> Go to Folder, type "/etc" (without the quotes) into the field, then click "Go". Files I see that might be causing trouble are bashrc and profile, although there may be others. Privileges could cause trouble for moving and/or modifying those files from your normal account. If that's the case I'd suggest logging in as root (
    http://support.apple.com/kb/HT1528).

  9. 0

    Almo2001

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Ok, I'm on a computer that won't allow me root access, since I'm at a big corp (Ubisoft). I'll forward the information in this thread to tech support to help them solve this.

    Thanks again.

  10. 0

    William Boyd, Jr.

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Almo2001 wrote:

    Ok, I'm on a computer that won't allow me root access

    An alternative might be "single-user mode":

    http://docs.info.apple.com/article.html?path=Mac/10.6/en/8475.html

    This page mentioned a "mount" command that's needed if you plan to change anything on your disk:

    http://www.westwind.com/reference/os-x/commandline/single-user.html

  11. 0

    Almo2001

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Ok, I'm now using Single User and messing around. I've tried removing the .bash_* files from my home directory, and I've tried reverting to the original /etc/profile (we use a modified one here).

    I don't see anything out of place, but honestly I'm not an expert with these things.

    Oh yeah! I found this in the a system log just after Terminal fails:

    Jul 6 14:04:57 mtl-mac-af272-3 login[404]: in openpam
    loadmodule(): no pam_centrifydc.so found

    Jul 6 14:04:57 mtl-mac-af272-3 login[404]: pam_start(): system error

    Maybe this is relevant?

  12. 0

    William Boyd, Jr.

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Almo2001 wrote:

    I'm now using Single User and messing around. I've tried removing the .bash_* files from my home directory

    If I remember correctly that the fresh user you tried had the same problem, I wouldn't expect that to help, as the problem would appear to be in a system-level file. On the other hand, if your administrators have put shell initialization files in the user template (assuming that's possible), then any user you add could have the same problem. Did you remove .bashrc?

    I've tried reverting to the original /etc/profile (we use a modified one here).

    That's a good thing to try. Too bad it didn't help.

    I found this in the a system log just after Terminal fails:

    Jul 6 14:04:57 mtl-mac-af272-3 login[404]: in openpam
    loadmodule(): no pam_centrifydc.so found

    Jul 6 14:04:57 mtl-mac-af272-3 login[404]: pam_start(): system error

    I don't have such a file on my system. On the other hand, this Web page

    http://ushosi.110mb.com/files/centrifydcadminguide.pdf

    discusses how Centrify DirectControl has to do with Microsoft Active Directory, which is presumably something your corporate IT people installed. PAM itself is a system of "Pluggable Authentication Modules", providing "an additional layer of abstraction to Unix authentication". You might find a file related to Centrify in /etc/pam.d .

    I don't think that's what's causing your problem, but your IT people might be interested in knowing about it.

    Back to your problem, I'd try renaming /etc/bashrc and /etc/profile .

    In case it might suggest a fix, here's material from "man bash" (the section titled "Invocation"):


    The following paragraphs describe how bash executes its startup files.
    If any of the files exist but cannot be read, bash reports an error.
    Tildes are expanded in file names as described below under Tilde
    Expansion in the EXPANSION section.
    When bash is invoked as an interactive login shell, or as a non-inter-
    active shell with the --login option, it first reads and executes com-
    mands from the file /etc/profile, if that file exists. After reading
    that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.pro-
    file, in that order, and reads and executes commands from the first
    one that exists and is readable. The --noprofile option may be used
    when the shell is started to inhibit this behavior.
    When a login shell exits, bash reads and executes commands from the
    file ~/.bash_logout, if it exists.
    When an interactive shell that is not a login shell is started, bash
    reads and executes commands from ~/.bashrc, if that file exists. This
    may be inhibited by using the --norc option. The --rcfile file option
    will force bash to read and execute commands from file instead of
    ~/.bashrc.
    When bash is started non-interactively, to run a shell script, for
    example, it looks for the variable BASH_ENV in the environment,
    expands its value if it appears there, and uses the expanded value as
    the name of a file to read and execute. Bash behaves as if the fol-
    lowing command were executed:
    if [ -n "$BASH_ENV" ]; then . "$BASH_ENV"; fi
    but the value of the PATH variable is not used to search for the file
    name.
    If bash is invoked with the name sh, it tries to mimic the startup
    behavior of historical versions of sh as closely as possible, while
    conforming to the POSIX standard as well. When invoked as an interac-
    tive login shell, or a non-interactive shell with the --login option,
    it first attempts to read and execute commands from /etc/profile and
    ~/.profile, in that order. The --noprofile option may be used to
    inhibit this behavior. When invoked as an interactive shell with the
    name sh, bash looks for the variable ENV, expands its value if it is
    defined, and uses the expanded value as the name of a file to read and
    execute. Since a shell invoked as sh does not attempt to read and
    execute commands from any other startup files, the --rcfile option has
    no effect. A non-interactive shell invoked with the name sh does not
    attempt to read any other startup files. When invoked as sh, bash
    enters posix mode after the startup files are read.
    When bash is started in posix mode, as with the --posix command line
    option, it follows the POSIX standard for startup files. In this
    mode, interactive shells expand the ENV variable and commands are read
    and executed from the file whose name is the expanded value. No other
    startup files are read.
    Bash attempts to determine when it is being run by the remote shell
    daemon, usually rshd. If bash determines it is being run by rshd, it
    reads and executes commands from ~/.bashrc, if that file exists and is
    readable. It will not do this if invoked as sh. The --norc option
    may be used to inhibit this behavior, and the --rcfile option may be
    used to force another file to be read, but rshd does not generally
    invoke the shell with those options or allow them to be specified.
    If the shell is started with the effective user (group) id not equal
    to the real user (group) id, and the -p option is not supplied, no
    startup files are read, shell functions are not inherited from the
    environment, the SHELLOPTS variable, if it appears in the environment,
    is ignored, and the effective user id is set to the real user id. If
    the -p option is supplied at invocation, the startup behavior is the
    same, but the effective user id is not reset.

  13. 0

    Almo2001

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Ok, I tried renaming /etc/profile, and /etc/bashrc. No luck. Looks like they're going to do a complete reinstall to fix this. 😟 I've put them off while I'm still working on submitting my iPhone game, as I'd hate to have the reinstalled computer unable to build the executable.

    In the mean time, I'm hoping I find a solution to this.

    Is there some sort of tool on Mac OS like Filemon from Sysinternals.com? This program monitors the computer and lists all files that are accessed. Makes it easier to track down stuff like this.

    Message was edited by: Almo2001

  14. 0

    William Boyd, Jr.

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Almo2001 wrote:

    Ok, I tried renaming /etc/profile, and /etc/bashrc. No luck.

    The only other thing that occurs to me is to put a statement like this


    echo "I reached point X in file Y" >> ~/trace.txt

    right near the beginning and end of each of those scripts. That
    might give you an idea of how far the shell reached and what scripts it invokes. You might also throw in an "env" command to see what shell variables are set.

    Is there some sort of tool on Mac OS like Filemon from Sysinternals.com? This program monitors the computer and lists all files that are accessed. Makes it easier to track down stuff like this.

    I'm not aware of such a thing, although that doesn't mean it doesn't exist.

  15. 0

    pkkelly

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi Almo

    I had the same problem today and this is how I fixed it:

    My IT dept had installed Centrify on my Mac and it added som lines to /etc/pam.d/login.term

    All you need to do is delete / comment out any lines below "#Added by CentrifyDC

    thanks

    paul

  16. 0

    Almo2001

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Bingo!!!

    Thanks so much for that. I'll forward this info to our IT dept so they will know, too.

  17. 0

    William Boyd, Jr.

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Keep in mind that deleting those lines probably disables whatever function the Centrify software would have had. In a way, deleting those lines is a little like disconnecting a warning light on your car. It "solves" the problem of that bothersome light, but doesn't address the underlying problem. I would bring everything you know about the problem to your IT people and ask them to research it.