Foglight 5.9.5 - Installing Foglight on a UNIX System with an Embedded PostgreSQL Database

Understanding the Password and Socket settings

The file server.config also contains parameters that set the password and socket that the embedded database uses.

The password that the server.database.embedded.password parameter specifies is the root password used for the embedded database. The default value is foglight.

If you selected the embedded database option while installing Foglight and now want to switch to using an embedded database, you do not need to change the root password.

If you did not select the embedded database option during installation, you need to specify the correct root password as the value of server.database.embedded.password. This password can be specified in either an encrypted or plain-text format. If necessary, you can encrypt the password using the <foglight_home>/bin/keyman.sh tool.

During installation, the Foglight installer overwrites the default value of server.database.embedded.password when you select the embedded database.

IMPORTANT: Do not use “<“ and “>” in your password, for example jo<anne>123. These characters corrupt the XML in the server.config file, causing Foglight to fail to start successfully.

The server.database.embedded.socket parameter specifies a UNIX® domain socket. This parameter is used on Linux® and Solaris platforms only. The installer generates a unique socket name for each installation.

IMPORTANT: Do not change this setting.

Configuring ports

You can set a number of different ports using the file <foglight_home>/config/server.config, including mandatory ports required for Foglight to run.

For a list of these ports, their default values, and the configuration parameters you can use to set them in server.config, see the Administration and Configuration Help.

NOTE: In certain configurations the Management Server may use ports in addition to the ones that you set using server.config. See the Administration and Configuration Guide for details.

Setting memory parameters for the server

If you are running the Management Server by running bin/fms, you can configure the Java® Virtual Machine’s (JVM) minimum and maximum memory parameters for the server in the <foglight_home>/config/server.config file.

If you are starting Foglight using the run.[bat|sh] command, the JVM heap memory parameters set in the <foglight_home>/config/server.config file do not take effect. Use -X options to pass the memory parameters straight to the VM.

If your installation supports a large number (hundreds) of agents, you can set the Java® heap memory minimum (-Xms) and maximum (-Xmx) options to the same size. For example, assigning
1GB of memory can be set in the server.config file as follows:

Ensure that you uncomment these lines in the file.

You can set up to 100 VM options in total.

NOTE: The -Xms and -Xmx options are different for 32-bit and 64-bit JVMs and available physical memory. The values of the -Xms and -Xmx options do not necessarily have to be the same size. However, the value of the -Xmx option should not exceed certain limits that the System Administrator specifies.

Process heap use

When a thread is created and run, a run-time stack is dynamically allocated from the native process heap (not the Java® heap). This native heap requires a large contiguous memory block. If the system you are running does not have enough RAM, or if the operating system cannot find a large enough contiguous memory block, new native threads cannot be created and a java.lang.OutOfMemoryError occurs.

If the VM generates errors relating to a failure to allocate native resources, or relating to exhaustion of process address space, you must increase the native process heap size. Errors appear as a Java VM internal error message or a detail message associated with an out-of-memory error. Messages with the relevant errors indicate that the problem is process heap exhaustion.

You cannot directly set the size of the process heap. The process heap uses memory within the 32-bit address space not used by the garbage-collected heap. To increase the size of the process heap, decrease the maximum Java heap size using the -Xmx option in the server.config file.

The default stack size can be adjusted with the ‑Xss option.