-
Titolo
Unable to start the Foglight Agent Manager (FGLAM) or Foglight Management Server (FMS) after Linux operating system upgrade -
Descrizione
After installing an operating system patch on a Linux machine, the Foglight Agent Manager (FglAM) or Foglight Management Server (FMS) does not start up anymore. It failed with a Java Virtual Machine memory allocation error.
During startup the following error can be found:
---
# A fatal error has been detected by the Java Runtime Environment:## SIGBUS (0x7) at pc=0x00007f8cde2bd66b, pid=32440, tid=140243098556160## JRE version: 6.0_45-b06# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.45-b01 interpreted mode linux-amd64 compressed oops)# Problematic frame:# j java.lang.Object.()V+0## An error report file with more information is saved as:# /opt/Quest_Software/Foglight_Agent_Manager/client/5.7.0-201405021222-334052-588/hs_err_pid32440.log-------------0 (0x00000000f40a89d8) [00|00| 2][ 0x0000000000000000][ 0x0000000000000000][ 0x0000000000000000]-------------1 (0x00000000f40a89f8) [00|00| 3][ 0x0000000000000000][ 0x0000000000000000][ 0x0000000000000000]-------------...---This error appears 6 times and then the startup process stops. -
Causa
In June 19, 2017, Red Hat released a new fix which addressing the CVE-2017-1000364 kernel: heap/stack gap jumping via unbounded stack allocations.
This fix caused a new issue for several Red Hat versions and all Linux systems which applied the CSV fixing “JVM crashes after updating to kernel with patch for Stack Guard flaw (CVE-2017-1000364)”
The resolution from Red Hat is to upgrade to its newer kernel version. Problematic kernel version is: 2.6.32-696.3.2.el6.x86_64.
If an kernel upgrade is not possible please follow the workaround below to get Foglight up and running again.
-
Risoluzione
Preferred Solution:
Follow Red Hat KB3091371 upgrade to new Linux kernel.
Workaround:
To fix the issue in Foglight Agent Manager (FglAM) please set the following parameter:
- Connect to the FglAM server
- Go to "$FGLAM_HOME/state/default/config/"
- Make a backup copy of the file "baseline.jvmargs.config"
- Open the file and add the parameter: vmparameter.0 = "-Xss2m";
Note: If parameter vmparameter.0 is already in use, please select the next free parameter number, for example vmparameter.1 or vmparameter.2, .... - Once the change is done, please start the FglAM
If the Foglight Agent Manager installer file failed to start, please use the following command:
$FGLAM_HOME/fglam-XXX.bin -D-Xss2m
To fix the issue in Foglight Management Server (FMS) please set the following parameter:
- Connect to the FMS server
- Go to "FGL_HOME/config"
- Make a backup copy of the file "server.config"
- Find next available server.vm.option and put line like this server.vm.optionx = "-Xss2m ";X is next available number
- Once the change is done, please start the FMS
If the Foglight Management Server (FMS) installer file failed to start, please use the following command:
$FMSHOME/bin/fms-XXX.bin -D-Xss2m
*********** How to verify if the OS has being upgraded recently********
Please run with root access level:
rpm -qa --last | less
and see the date
-
Informazioni aggiuntive
In case embedded FglAM is used the above mentioned changes has to be made to FglAM config as well in the baseline.jvmargs.config file to ensure proper start up of embedded FglAM.