Elastic Compute Service:What do I do if an error message, such as "This account is currently not available", appears when I connect to a Linux ECS instance by using SSH?

Problem description

When you use an SSH command to log on to an ECS instance of the Linux system, the connection fails even if you use a normal account and password. Errors similar to the following are also displayed in the command-line or secure logs.

• This account is currently not available.

• Connection to 127.0.0.1 closed.

• Received disconnect from 127.0.0.1: 11: disconnected by user.

• Pam_unix (sshd: session): session closed for user test.

Causes

This problem is usually caused by the modification of the default Shell of the corresponding user.

Solution

1. Log on to an instance. For more information about how to log on to an instance, see Connect to a Linux instance by using a management Terminal.

2. Run the following command to view the default Shell of the corresponding user.

   Cat/etc/passwd | grep test

   The command output is as follows. The Shell of the logon user is changed to nologin.

   test:x:1000:1000::/home/test:/sbin/nologin

3. We recommend that you back up files before you modify the policy configuration.

4. Run the following command to edit /etc/passwd file, and change the default Shell of the corresponding user to bash, that is /sbin/nologin change /bin/bash save the settings and exit.

   vi /etc/passwd

5. Try to connect to the server again on the client and make sure that the connection is normal.

   Note

   Tips: If you have any questions, see Guidelines for troubleshooting failure to remotely log on to Linux instances through SSH.

Application scope

• ECS