The pts/27 is now locked by liu.yang. password: authentication failure – What it Means and How to Fix It

In today’s digital world, security is paramount. However, sometimes security measures can lead to inconveniences. If you’ve encountered the message: “the pts/27 is now locked by liu.yang. password: authentication failure,” you’re not alone. This situation occurs in environments like Linux or Unix systems, where multiple failed login attempts lead to an account lockout or access restrictions.

The message “the pts/27 is now locked by liu.yang. password: authentication failure” indicates multiple failed login attempts due to incorrect password entries, resulting in a temporary lockout.

In this article, we will explore the message in depth. We will explain why it happens, how you can troubleshoot it, and what preventive measures you can take in the future. The goal is to give you insights and solutions beyond just the error message.

What Does the Message “the pts/27 is now locked by liu.yang. password: authentication failure” Mean?

This message is commonly seen in Linux/Unix-based systems and indicates that a specific terminal, pts/27 in this case, has been locked by a user named liu.yang due to repeated authentication failures (incorrect password attempts).

Let’s break this down further:

• pts/27: This is a pseudo-terminal session identifier. In multi-user systems, pseudo-terminals (pts) are used to manage multiple sessions. The number (27) represents the particular session where this issue occurred.
• Liu.yang: This is the username of the individual who has locked the session.
• Password authentication failure: This simply means that multiple failed attempts were made to log into the system, using the wrong password.

This error typically points to either an incorrect password being entered multiple times, or in some cases, an attempted security breach. As a result, the system temporarily locks the session for liu.yang as a protective measure.

Why Does This Error Occur?

1. Incorrect Password Entries: The most common reason is that the user entered the wrong password multiple times, triggering the lockout.
2. Security Settings: Many systems have a built-in feature to automatically lock a terminal or account after a certain number of failed login attempts. This is designed to prevent brute-force attacks or unauthorized access attempts.
3. Multiple Login Attempts from Different Locations: In some cases, a user might try to log in from multiple devices simultaneously, causing conflicts, especially if the wrong credentials are entered on one of the devices.
4. Keyboard Layout Issues: Sometimes, the keyboard layout might change unexpectedly, leading to unintentional wrong password entries.

How to Fix “the pts/27 is now locked by liu.yang. password: authentication failure”

While the error might seem frustrating, there are several ways to resolve it. Let’s look at the steps:

1. Wait for Automatic Unlock

Many systems have an automatic unlock feature. After a certain period (which can vary depending on system settings), the account or session might unlock itself.

2. Contact the Administrator

If you’re working in a corporate or institutional environment, contact your system administrator. They can manually unlock the terminal and assist you in resetting the password if necessary.

3. Manually Reset the Account (Administrator)

If you’re the administrator, you can unlock the terminal with the following steps:

1. Log in as root or a user with sudo privileges.
2. To check the locked session, run:

   who -T

This will show you all active sessions, including locked ones.

3. You can use the kill command to terminate the locked session:

   sudo kill -9 {process_id}

Replace {process_id} with the ID of the locked session.

4. Optionally, reset the password for liu.yang if the problem persists:

   sudo passwd liu.yang

4. Check for Failed Login Attempts

You can view recent login attempts using the lastb command. This command shows all failed login attempts, giving you a sense of what’s happening:

lastb

If you see numerous failed attempts, it might indicate a security issue, and you should investigate further.

5. Check System Logs

Review the system logs to understand the nature of the error. The auth.log or secure.log files will provide insights into why the authentication failure occurred:

cat /var/log/auth.log | grep "liu.yang"

Preventing Future Lockouts

While occasional lockouts due to incorrect password entries are understandable, repeated lockouts can be frustrating. To prevent this from happening in the future, consider these tips:

1. Use Strong but Memorable Passwords

Strong passwords reduce the chances of authentication failure. However, they should also be memorable to avoid typing mistakes.

2. Enable Multi-Factor Authentication (MFA)

Multi-Factor Authentication adds an extra layer of security. Even if the wrong password is entered, the system will require a secondary method of verification, reducing the risk of lockouts.

3. Check Keyboard Layouts

Before entering your password, make sure the keyboard layout is set correctly. On some systems, accidental switching between layouts (e.g., from QWERTY to AZERTY) can cause incorrect password entries.

4. Limit the Number of Concurrent Sessions

Some systems allow users to open multiple concurrent sessions. However, these sessions can sometimes interfere with each other. Limiting the number of sessions can help reduce lockouts.

5. Update Security Policies

System administrators can update security policies to adjust the number of failed attempts allowed before a session is locked. Reducing the threshold might prevent accidental lockouts.

Understanding Pseudo-Terminals (PTS) and Their Role in Lockouts

In Linux and Unix environments, pseudo-terminals (PTS) are virtual devices used to manage user sessions. Each PTS represents a unique session for a user. The error message refers to pts/27, which indicates the specific session that was locked.

When a user logs into the system, a new PTS is created, represented by a number (e.g., pts/27). This allows multiple users to log in and interact with the system simultaneously. However, when too many incorrect login attempts occur in one session, the system locks that session to prevent further attempts.

Related Terms and Concepts

Authentication

Authentication is the process of verifying the identity of a user or device. Password authentication, as seen in this error, is one of the most common methods. Failed authentication attempts typically result in error messages like this one.

Lockout

A lockout occurs when a user is temporarily or permanently prevented from accessing a system after a series of failed login attempts. This security measure protects systems from unauthorized access attempts.

Brute Force Attack

A brute-force attack is a method where an attacker tries multiple password combinations in an attempt to guess the correct one. Many systems prevent brute-force attacks by locking accounts after several failed attempts.

Frequently Asked Questions

1. What is “the pts/27 is now locked by liu.yang. password: authentication failure” error?

This error indicates that a user session (pts/27) has been locked due to multiple failed password attempts, resulting in a temporary lockout.

2. How long does the lockout last?

The duration of the lockout varies depending on the system’s security settings. It could last anywhere from a few minutes to several hours.

3. Can I unlock the session myself?

If you are the system administrator, you can manually unlock the session using administrative commands. Regular users need to wait or contact an administrator.

4. How can I prevent future lockouts?

To prevent future lockouts, use strong passwords, enable multi-factor authentication, ensure correct keyboard layouts, and reduce the number of concurrent sessions.