Management problem with GAIA OS

[Matlu]

Hello, everyone.

We have a HA SMS environment, which is in version R81.10, both on Open Server.

Currently the HA SMS passive equipment, has very big problems SLOWNESS.
Every time we try to access by CLI to the equipment
(We enter by Putty, or some other terminal, the "prompt" to enter the username and password, takes an eternity to appear).

The active member of HA SMS has no problem.

When accessing after a long time to the passive equipment, the equipment fails to accept the commands you try to type, and/or if it accepts the command, and you try to have an output of the same, such as commands like (cpview, top, free -m), the equipment takes forever to display the output of the command.

We have noticed that the CPU seems to be "stressing out" and we believe this is the reason for the problem.

In this scenario, is it advisable to FRESH INSTALL the device, and reinstall the GAIA OS?

I have the impression that the OS has been damaged for some reason.

Do you have any opinion and/or experience similar to the above?

Thanks for your comments.

[Matlu]

It is an extreme decision.

A case has been opened with CT, but they are unable to "find" a probable cause-root.

That is why, given the customer's need for the solution to work well, we are almost determined to reinstall the GAIA OS, believing that this will "correct" the problem.

[the_rock]

Are you able to send us output of command @Timothy_Hall asked, as well as below:

top

ps -auxw

free -g

screencap of cpview output of memory/cpu

[the_rock]

Also, send us output of cpstat os -f all

[Timothy_Hall]

If the hypervisor environment is the source of the problem, reloading Gaia in the same VM won't help.  Creating a brand new VM and reloading it might help if the hypervisor was denying/restricting resources to the old VM for some reason.

[Hugo_vd_Kooij]

Ackwardly no one mentioned another cause. Your OpenServer might just be faulty. Say you have a disk issue than the system will be in a heap of trouble as it can't write the data in a timely fashion.

In case of an installaton on ESXi make sure you applied the tuning from https://support.checkpoint.com/results/sk/sk104848 as I have seen some weird thing happen if you don't do it. In one case the system was fine for years without it untill we added a syslog export. Then everything went haywire as soon as you performed an additioncal task.

And make sure You are on the latest Jumbo Hotfix. Memory leaks and so on get fixed in them.