Deployment Environment Exception

When you deploy a server, the deployment may fail. One of the reasons is "Deployment environment exception." You can check and fix the problem on the Deployment Wizard page. The reason "Deployment environment exception" occurs in different situations. This document introduces the specific error messages and corresponding solutions. 

Note:

1. Tomcat is used as an example. For other containers, tools.jar also needs to be copied and pasted to the lib of the corresponding container.

2. The tools.jar in %JAVA_HOME%/jdk/lib is the file in the JAVA_HOME of the deployed server (not of the development computer).

Copy the tools.jar in %JAVA_HOME%/jdk/lib and paste the JAR file to the deployed server, namely in %TOMCAT_HOME%/lib and %TOMCAT_HOME%/webapps/Project name/WEB_INF/lib, as shown in the following figure.

For example, the error message is "Caused by: java.lang.UnsatisfiedLinkError: sun.tools.attach.LinuxVirtualMachine.isLinuxThreads()Z."

According to the prompt information, you can judge whether the tools.jar of the Linux environment is placed in the Windows environment or the tools.jar of the Windows environment is placed in the Linux environment.

Log error message: "Caused by: com.sun.tools.attach.AttachNotSupportedException: no providers installed"

When you install JDK in the Windows system, an independent JRE will be installed at the same time. No attach.dll file exists in the independently installed JRE, but the file is needed for FineBI startup.

Copy the attach.dll file in %JAVA_HOME%/jdk/jre/bin and paste the file to %JRE_HOME%/bin, as shown in the following figure.

Log error message: "Caused by: com.sun.tools.attach.AttachNotSupportedException: Unable to open socket file: target process not responding or HotSpot VM not loaded"

You cannot add files to the /tmp directory. The possible causes and solutions for this problem are as follows.

• 1. Ordinary users do not have the permission. The admin can assign the chmod -R 1777 /tmp permission to the /tmp directory. Command information: chmod -R 1777 /tmp. Command description: All people can read, write, and execute the /tmp folder and directory. Only the file owner and the super administrator can delete the files created in the /tmp directory.

• 2. The disk space where /tmp is located is full. Clean up the disk.

For different containers, the directed locations of java.io.tmp are different. The following are the possible reasons for this problem.

• 1. You do not have the permission. Ask the admin for the permission.

• 2. The disk space where java.io.tmp is located is full. Clean up the disk.

Solution: Upgrade the GNU Compiler Collection (GCC), and search online for the specific methods.

After the upgrade, enter ldd FineAssist_x86_64.so in the command line. If the content displayed is the same as the content in the following figure, it means the version of the GLIBC is normal.

Contact technical support with the startup log, see Service Platform > Online Support.

The font package does not exist in the OpenJDK in the server deployment package for copyright reasons. In this case, if the Linux system lacks a font package, an error will be reported: "fontconfig missing", or "Dec-Basic_Non_Existent."

Therefore, you need to check the fontconfig before deploying.

Detection method:

You can determine whether the fontconfig has been installed on the server by executing the fc-list command on the server or checking whether the fc-list file exists in the /usr/bin directory.

Installation method:

You can install the fontconfig according to your system conditions.

Usually in the Linux system, you can install the fontconfig by executing the command yum install fontconfig, and then restart FineBI.

Solution one: Set headless=true (recommended)

Headless mode is a working mode of the system. If the system property java.awt.headless is set to true, the headless toolkit will be used.

This section describes the procedures to enable the headless mode in Tomcat environment.

• In the Windows system, enter the directory %Tomcat_HOME%\bin. Find the setenv.bat file. If the file does not exist, create a setenv.bat file. Add the following lines to the file for configuration, and restart the project after configuration.

set JAVA_OPTS=%JAVA_OPTS% -Djava.awt.headless=true

• In the Linux system, enter the directory %Tomcat_HOME%\bin. Find the setenv.sh file. If the file does not exist, create a setenv.sh file. Add the following lines to the file for configuration, and restart the project after configuration.

JAVA_OPTS="$JAVA_OPTS -Djava.awt.headless=true"

Solution two: Installing the Missing Graphics Libraries

Extranet users:

Execute the command line to install the graphics libraries online (example for the Ubuntu system).

• apt-get install libxrender-dev

• apt-get install libxtst-dev

Intranet users

1. Select the installation package
 based on your system and the corresponding version at https://developer.aliyun.com/packageSearch?word=libxrender. 2. Install the package manually by using installation statements. The sample installation statements are as follows.

• The system of the DEB packages series (such as the Ubuntu system): dpkg -i **.deb

• The system of the RPM package series (such as the CentOS system): yum install **.rpm

Problem

In the Windows system, when you install or deploy version 5.1.15 and the later versions, an error is reported, indicating that the msvcr120.dll runtime library does not exist.

Solution

You are advised to install the msvcr120.dll file before deploying. For the missing file downloads, see Microsoft Visual C++ Redistributable Latest Supported Downloads.

Note:

Only by downloading the Visual Studio 2010 (VC++ 10.0) SP1 version can the problem be solved.