Start FineBI in Linux

On a Linux server, FineBI needs to be managed after the installation is successful, such as startup, setting of self-startup, shutdown and other operations.

1. Enter the directory

For example, if FineBI is installed in the opt directory, you need to enter the %FineBI%bin directory, as shown below:

cd /opt/FineBI/bin

2. Start the project

Execute the start command directly as follows:

nohup ./finebi &

The result of the operation is shown in the following figure:

• & : run in the background, this command allows the process to run in the background.

• nohup : Run the command without hanging up. This command can continue to run the corresponding process after logging out of the account / closing the terminal.

Combining nohup with & enables the ability to permanently execute a command in the background.

3. Successful start

After executing the command, as shown in the figure below, the startup is successful.

If you need to modify the memory, you need to modify it in the finebi.vmoptions file. For details, see: Modify JVM memory in Linux 

Note: The startup and memory setting files are in the first-level directory of the installation.

In Linux servers, commonly used applications are usually set to start automatically when the server is turned on, so that when the server is restarted, there is no need to perform the complicated operation of application startup, and at the same time, it can reduce the omission of application startup due to the restart of the server.

The principle of self-starting of Linux server: everything in the Linux server is a file, and the startup of the application also reads the file. Therefore, as long as the startup command of the application is written in the configuration file to be read when the server starts, the configuration file uses  rc.local  file.

1. Modify the configuration file

1) Find the rc.local file for editing, and fix its path at  /etc, you can directly execute editing commands, as shown below:

vi /etc/rc.local

2) In the editing interface, press the  i key to enter the insert state. Enter the startup command of FineBI in the last line of the file. Since it is not currently in the directory path of FineBI, the startup command should add the file absolute path, and the startup command is:

nohup /opt/FineBI/bin/finebi &

 Note: The path needs to be changed to the corresponding FineBI installation path.

As shown below:

3) After editing, press ESC to exit the insert interface, and enter  :wq, save the file and exit.

Note: If it cannot take effect after configuration, execute chmod +x /etc/rc.d/rc.local to make the configuration file take effect, because in Linux such as CentOS7 The rc.local file has been gradually deprecated permissions in the operating system.  

2. Restart the server

Execute the command reboot to restart the Linux system , after logging in again, use the following command to view the process:

ps -ef | grep finebi

If you see the FineBI process, it means that after the Linux system restarts, FineBI is automatically started successfully, as shown in the following figure:

3. Notes

If the configuration file according to section 2.2.1 fails to take effect and the automatic startup cannot be realized, execute chmod +x /etc/rc.d/rc.local  , add execute permission to the configuration file. Because in Linux operating systems such as CentOS7 /etc/rc.d/rc.local does not have execution permissions.

In the Linux system, FineBI does not have the corresponding background interface in the Windows system to close the program. Therefore, the service needs to be closed by killing the process.

1) Use the following command to view the PID corresponding to the FineBI process, as shown below:

ps -ef | grep finebi

2) Kill the PID process. For example, if the PID of the process corresponding to FineBI is 4626, execute the following command:

kill -9 4626

Note: The above two steps can be done with one command, ie  ps -ef | grep finebi | grep  -v 'grep' | awk '{print $2}' | xargs -I {} kill -9  {} .

When a non-root user starts, exceptions such as logs and spark's temporary tmp path may occur due to permission issues.