Linux – PuTTY closes after login

bashlinuxputtysshunix

I'm logging in through my schools host and everything works fine, I exited earlier and now anytime I try to log back in, PuTTY automatically closes. I also used the Google Shell to see if it was an issue with PuTTY but I still get logged out. Here is the output I get:

Last login: Tue Feb 14 21:51:02 2017 from rsrch-bd09s72.ucads.uc.edu
/home/ep69674/.profile[3]: Class: not found [No such file or directory]
/home/ep69674/.profile[7]: 1.: not found [No such file or directory]
/home/ep69674/.profile[14]: 2.: not found [No such file or directory]
/home/ep69674/.profile[15]: what: not found [No such file or directory]
/home/ep69674/.profile[22]: 3.: not found [No such file or directory]
/home/ep69674/.profile[29]: 4.: not found [No such file or directory]
/home/ep69674/.profile[32]: ________________: not found [No such file or directory]
/home/ep69674/.profile[36]: 5.: not found [No such file or directory]
/home/ep69674/.profile: line 36: syntax error: `(' unexpected
Connection to rwclinux.rwc.uc.edu closed.
NaCl plugin exited with status code 3.

Side note: I'm also using SSH

Best Answer

It seems as though your .profile file has become corrupted, and is preventing your account from logging in.

This will likely require you to contact your system administrator to fix the file.

I've looked through a few "How to bypass .profile on login" articles, and though I don't have access to PuTTY to see if these flags can be set somehow, specifying bash --noprofile as the remote command might allow you to login.

Someone also reported that they were able to regain control by sending Control-C during the login process.

Should you be able to get access to your account this way, you may wish to run

mv .profile .profile-copy

so you can get back into your account without trickery in the future.

Related Solutions

Using colour schemes with vim and putty

By default, PuTTY presents itself as xterm. The terminfo database, used by various programs to determine the terminal capabilities, says xterm supports eight colors only:

$ infocmp -1L xterm | grep max_colors

This means that even if your version of Xterm does support 256-color mode, programs won't know about it.

The easiest fix is to set your $TERM environment variable to xterm-256color.

(In your ~/.profile, you could use:
if [ "$TERM" = xterm ]; then TERM=xterm-256color; fi)
You can tell PuTTY to always identify itself as xterm-256color, via Configuration → Connection → Data → Terminal-type string.

Note: If you use #1 or #2, and you connect to a server which doesn't have the apropriate terminfo entry, all TUI programs will break.
You can also set the 't_Co' option in vim to 256 to override the terminfo value.
```
if &term == "xterm"
    set t_Co=256
endif
```

Or you could edit the terminfo database.

$ infocmp -L -1 xterm | sed -r 's/(max_colors)#[0-9]+/\1#256/' > /tmp/xterm
$ tic /tmp/xterm

The updated entry will be kept in ~/.terminfo.

Putty title changes after login

It's most likely updated by your shell prompt ($PS1 in ~/.bashrc or the system-wide /etc/bash.bashrc). Look for \e]2; or \033]2; or a similar escape sequence.

Your given example looks like the usual "<user>@<host>:<path>" template, in which domU-12-31-20-0a-81-AB is the server's hostname as currently configured in the kernel. Most likely, it was assigned by an automated Xen domU creation tool based on your virtual server's Ethernet address.

You can change the current hostname by using hostname newname. To make it persist across reboots, look around in /etc – on every reboot, the hostname is read from the file /etc/hostname (other distributions may use /etc/sysconfig/hostname or similar).

Best Answer

Related Solutions

Using colour schemes with vim and putty

Putty title changes after login

Related Question