Unable to start the Foglight Agent Manager (FGLAM) or Foglight Management Server (FMS) after Linux operating system upgrade (4252644)

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:

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)”

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:

1. Connect to the FglAM server
2. Go to "$FGLAM_HOME/state/default/config/"
3. Make a backup copy of the file "baseline.jvmargs.config"
4. 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, ....
5. 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:

1. Connect to the FMS server
2. Go to "FGL_HOME/config"
3. Make a backup copy of the file "server.config"
4. Find next available  server.vm.option and put line like this server.vm.optionx = "-Xss2m ";
   X is next available number
5. 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