yexinru/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
Files
fix_python
doc-exports/docs/ecs/umn/en-us_topic_0240708482.html
Hasko, Vladimir d8a2842a27 Re-implementing ecs umn 20240823 with HSS content 
Reviewed-by: otcbot <otcbot@t-systems.com>
Co-authored-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-committed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
2024-09-17 15:21:19 +00:00

7.9 KiB
Raw Permalink Blame History

Why Am I Seeing the Error Message "Module is unknown" When I Remotely Log In to a Linux ECS?

Symptom

When you attempt to remotely log in to a Linux ECS, the system displays the error message "Module is unknown".

Figure 1 Module is unknown
  • To resolve this issue, restart the ECS and enter the rescue mode.
  • Restarting the ECS may interrupt services. Exercise caution when performing this operation.

Root Cause

The file in the /etc/pam.d/ directory was modified by mistake.

Solution

  1. Enter the single-user mode.
    The following uses CentOS 7 as an example:
    1. Restart the ECS and click Remote Login.
    2. Click Ctrl+Alt+Del in the upper part of the remote login panel to restart the ECS.
    3. Press the up arrow key to prevent automatic system startup. When the kernels are displayed, press e to enter the editing mode.
      Figure 2 Entering the kernel editing mode

      The grub file is encrypted by Euler images by default. Before entering the edit mode, you need to contact customer service to obtain username and password.

    4. Locate the row containing linux16 and delete the parameters you do not require.
    5. Change ro to rw for mounting the root partition with read-write permissions.
    6. Add rd.break and press Ctrl+X.
      Figure 3 Before the modification
      Figure 4 After the modification
    7. Run the following command to go to the /sysroot directory:

      # chroot /sysroot

  2. Run the following command to view the system log for error files:
    grep Module /var/log/messages
    Figure 5 System log
  3. Comment out or modify the error line in the error files displayed in the system log.
    vi /etc/pam.d/login
    Figure 6 Modifying the error information
  4. Restart the ECS and try to log in to it again.
    • To view the modification records and check whether the modification is caused by unintended actions, run the following command:

      vi /root/.bash_history

      Search for the keyword vi or login.

    • Do not modify the files in the /etc/pam.d/ directory. Run the following command for details about pam:

      man pam.d

<script language="JavaScript"> </script>