Problem Description
When you use FineBI in the Linux system, the FineBI process shuts down abnormally, and there is no error message in the FineBI log.
Causes and Solutions
Possible Cause
The above problem may be caused by the FineBI process being killed by the system. You can check the Linux system log /var/log/messages to see what happened at that time when the process was terminated.
If the log shows that the FineBI process was killed at that time, it means that the system terminated the FineBI process. This may be caused by the Linux system's own OOM KILLER mechanism. Check the /etc/sysctl.conf file (kernel parameter configuration) of the Linux system. If vm.overcommit_memory equals 2, it means that the system does not allow overcommit operations.
The OOM KILLER mechanism will sequentially kill processes with high memory usage when Linux lacks memory. And it will record some information such as pid, process name, CPU mask and trace in /var/log/message. Similar problems can be detected through monitoring.
Solution
To address the problem, you can adjust the vm.overcommit_memory kernel parameter value of the system by setting it to 0/1.
0 – Heuristic overcommit handling. This is the default setting that allows overcommit request, but the overcommit request that is too blatant, for example, malloc demanding more memory than the system memory cap, will be rejected. The kernel uses a certain algorithm to determine whether your memory application is reasonable. If it finds it unreasonable, it will reject the overcommit request.
1 – Always overcommit. All overcommit requests are allowed.
You can adjust the kernel parameter value as needed, or increase the system memory. After adjusting the kernel parameter value, you need to enter the command sysctl -p to make the configuration file take effect.
sysctl -p
