FortiSIEM
FortiSIEM provides Security Information and Event Management (SIEM) and User and Entity Behavior Analytics (UEBA)
RuiChang
Staff
Staff
Article Id 316157
Description

 

This article provides a method to resolve symlink in FortiSIEM for Java & opensdk.

 

Scope

 

FortiSIEM.

 

Solution

 

FortiSIEM Java & opensdk symlink sometimes may break after an upgrade or changes in the backend. It can be verified via this command:

 

[root@supervisor]# ls -la /opt

total 13068

lrwxrwxrwx   1 root       root             12 Feb 29 22:26 Java -> /opt/openjdk

drwxr-xr-x   5 admin      admin           225 Dec  9 08:57 jsreport

drwxr-xr-x   7 admin      admin           206 Feb  6 12:54 node-rest-service

lrwxrwxrwx   1 root       root             40 Feb  6 12:44 openjdk -> /etc/alternatives/java_sdk_1.8.0_openjdk

 

If both lines above are highlighted in red, it means that the symlink is broken. In the log, it will affect multiple processes and functions. In the log, it is possible to find the error below:

 

Phxctl.log:

 

Fixing symlink for /etc/alternatives/java_sdk_1.8.0_openjdk

 

/opt/phoenix/logs/phoenix.log:

 

2024-04-12T11:22:57.260588+08:00 PCSGFSMC phDiscover[707017]: [PH_DISCOV_RUN_VM_TEST_CONN_ERROR]:[eventSeverity]=PHL_WARNING,[procName]=phDiscover,[fileName]=discover.cpp,[lineNumber]=2379,[hostIpAddr]=172.20.1.30,[exitValue]=32512,[phLogDetail]=Failed to execute runVmTestConn.sh

 

It can be further verified under this path:

 

# ls -la /etc/alternatives/java_sdk*

 

[root@supervisor alternatives]# ls -la java_sdk*

lrwxrwxrwx 1 root root 60 Dec  9 08:44 java_sdk -> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.392.b08-4.el8_8.x86_64

lrwxrwxrwx 1 root root 54 Dec  9 08:44 java_sdk_17 -> /usr/lib/jvm/java-17-openjdk-17.0.9.0.9-2.el8_8.x86_64

lrwxrwxrwx 1 root root 54 Dec  9 08:44 java_sdk_17_openjdk -> /usr/lib/jvm/java-17-openjdk-17.0.9.0.9-2.el8_8.x86_64

lrwxrwxrwx 1 root root 60 Dec  9 08:44 java_sdk_openjdk -> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.392.b08-4.el8_8.x86_64

 

From the output above, java_sdk_1.8.0_openjdk is missing from the list. Hence, users need to rebuild the symlink with the command below:

 

#ln -s /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.<version>.el8.x86_64 /etc/alternatives/java_sdk_1.8.0_openjdk

 

Example:

 

#ln -s /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.382.b05-2.el8.x86_64 /etc/alternatives/java_sdk_1.8.0_openjdk

 

Notes:

The Java version can be verified from other FortiSIEM instances with the same firmware version.

 

After that, the symlink is fixed, and the verified output below is presented with the color below:

 

[root@supervisor alternatives]# ls -la java_sdk*

lrwxrwxrwx 1 root root 60 Dec  9 08:44 java_sdk -> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.392.b08-4.el8_8.x86_64

lrwxrwxrwx 1 root root 54 Dec  9 08:44 java_sdk_17 -> /usr/lib/jvm/java-17-openjdk-17.0.9.0.9-2.el8_8.x86_64

lrwxrwxrwx 1 root root 54 Dec  9 08:44 java_sdk_17_openjdk -> /usr/lib/jvm/java-17-openjdk-17.0.9.0.9-2.el8_8.x86_64

lrwxrwxrwx 1 root root 60 Dec  9 08:44 java_sdk_1.8.0 -> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.392.b08-4.el8_8.x86_64

lrwxrwxrwx 1 root root 60 Dec  9 08:44 java_sdk_1.8.0_openjdk -> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.392.b08-4.el8_8.x86_64

lrwxrwxrwx 1 root root 60 Dec  9 08:44 java_sdk_openjdk -> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.392.b08-4.el8_8.x86_64

 

[root@supervisor]# ls -la /opt

total 13068

lrwxrwxrwx   1 root       root             12 Feb 29 22:26 Java -> /opt/openjdk

drwxr-xr-x   5 admin      admin           225 Dec  9 08:57 jsreport

drwxr-xr-x   7 admin      admin           206 Feb  6 12:54 node-rest-service

lrwxrwxrwx   1 root       root             40 Feb  6 12:44 openjdk -> /etc/alternatives/java_sdk_1.8.0_openjdk