Abnormal Shutdown BI process in Linux

When FineBI is used in Linux, the process of FineBI is abnormally shut down during the use of the system, and there is no abnormal information in the log of BI.

1. Possible reasons

In view of the above phenomenon, the cause of the problem may be that the process of FineBI is killed by the system, you can check the Linux system log /var/log/messages , view the log of the point in time when the process was shut down abnormally.

If there is a log corresponding to Killing the FineBI process at this point in time, it means that the FineBI process was killed by the system.

2. Solutions

The Linux system kills the process of FineBI, which may be caused by its own OOM KILLER mechanism. Check the /etc/sysctl.conf file (kernel parameter configuration) of your own Linux system. If vm.overcommit_memory=2, it means that the system does not allow overcommit operations.

The OOM KILLER mechanism will kill processes with high memory usage in turn when Linux memory is tight, and record them in /var/log/message, which will record some information such as pid, process name, cpu mask, trace, etc. Similar problems can be found through monitoring.

For such problems, we can adjust the value of the vm.overcommit_memory kernel parameter of the system and set it to 0/1, which means:

• 0 – Heuristic overcommit handling. This is the default value, which allows overcommit, but overcommit that are too blatant will be rejected. For example, the memory size requested by malloc at one time exceeds the total system memory. Heuristic means "heuristic", the kernel uses an algorithm (see the end of the article for a detailed explanation of the algorithm) to guess whether your memory application is reasonable, and it will reject overcommit if it thinks it is unreasonable.

• 1 – Always overcommit. Overcommit is allowed, and memory requests are not rejected.

Adjust the kernel parameter values as needed, or increase the system memory to solve. After adjusting the kernel parameter values, you need to enter the command sysctl -p to make the configuration file take effect.

sysctl -p

For detailed principles, please refer to Understanding MEMORY OVERCOMMIT of LINUX.