Got it

The Controller Memory Is Insufficient and the Minisystem Is Entered During Login

113 0 1 0 0

[Problem Information]

Table 1 Basic information about the problem

Information Name: The Controller Memory Is Insufficient and the Minisystem Is Entered During Login

Storage Type V3

Product Version ALL

Fault Category Login

Keyword: insufficient memory, minisystem, login failure


[Symptom]

Controller A fails to log in to the CLI, and a message is displayed indicating insufficient memory. Controller A enters the minisystem mode.


[Troubleshooting Roadmap]

1. Run the free -m command in the minisystem of controller A to check the available memory. If the available memory is close to or less than 100 MB, run the following command:

p1

2. Run the ps aux command in the minisystem view to query the memory usage of the iBase process (377144 KB). If the memory usage exceeds 81920 KB (80 MB), the memory usage of the iBase process is too high. (Find the process name ibase in the COMMAND column and the memory usage in the RES column.)

p2


3. The version is earlier than V300R003C20.


[Cause]

When FusionSphere, eSight, or upper-layer NMS software interconnects with storage V3 products, frequent login and logout will cause memory leakage of the storage iBase process, occupying a large amount of memory. The available memory of the controller is insufficient.


[Solution]

Method I. Interim measures

1. Log in to controller A with insufficient memory and run the kill -9 xxx command in the minisystem window. In the preceding command, xxx indicates the iBase process ID obtained from the ps aux command. In this example, the IDs are 21765 and 21763. Stop the iBase process.

2. You can log in to controller A again. (The memory is released after the iBase process with high memory usage is killed.) Run the reboot ism command in the developer view to restart the iBase process.


3. Go to the minisystem of controller A and run the ps aux command to check that the memory usage of the iBase process is normal. You can log in to DeviceManager of controller A.

p4

Method 2: Solution

After the temporary measures are taken, upgrade the version to the latest recommended version.


[Post-Recovery Check]

You can log in to controller A.


[Suggestion and Summary]

None


[Applicability]

Versions earlier than V300R003C20

Comment

You need to log in to comment to the post Login | Register

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."

My Followers

Login and enjoy all the member benefits

Login

Block
Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Reminder
Please bind your phone number to obtain invitation bonus.