No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

The wrong settings of the Putty causes the node’s CUP occupancy rate is flushing high when running health examination

Publication Date:  2012-11-09 Views:  51 Downloads:  0
Issue Description
Login in the MN node via the Chinese 0.62 version of Putty, execute the “healthcheck -n” node name, this node’s CUP occupancy rate will flush high, as the following picture displayed:

Adapting version:
The version of the Galax health examination tool: R2C00SPC206
The version of the Galax environment: R2C00SPC205
The version of the Putty tool: 0.62
Alarm Information
None
Handling Process
Before using the putty, check the configuration of the data column, confirm there isn’t configuration which may change the environment variable, if there has, please delete it, and then login in the MN to execute the health examination command.

(Note: This configuration can’t be deleted permanently; we must delete it each time we login in the PUTTY)
Root Cause
This problem is caused by the wrong settings of the Chinese version of Putty, there has entered values in the data configuration column which changing the environment variable LANG, as the picture displayed:

After login in the MN node, the tool has changed the node’s environment variable LANG, its normal value is POSIX, as the following picture displayed:


Login in the MN node via Putty, it has changed as zh_CN.UTF-8. As the following picture displayed:


After this environment variable has changed, the script “log_num.sh” falls into endless loop, can’t quit, and finally causes the CPU flushing high.
Suggestions
We recommend you don’t use the Chinese version of the PUTTY.

END