Chat now with support
Chat with Support

Foglight Agent Manager 5.8.5.7 - Foglight Agent Manager Guide

Configuring the embedded Agent Manager Installing external Agent Managers
Understanding how the Agent Manager communicates with the Management Server Deploying the Agent Manager cartridge Downloading the Agent Manager installer Installing the Agent Manager Starting or stopping the Agent Manager process Frequently asked questions
Configuring the Agent Manager Advanced system configuration and troubleshooting
Configuring Windows Management Instrumentation (WMI) Configuring Windows Remote Management (WinRM) UNIX- and Linux-specific configuration
Monitoring the Agent Manager performance Deploying the Agent Manager to large-scale environments

Configuring the Agent Manager to run as a daemon

Previous Next


As described in Installing the Agent Manager using the installer interface on page 14 and Installing the Agent Manager from the command line on page 21, you can install an init.d-style script called dell-fglam in the init.d directory on your system. This script is called when the host on which the Agent Manager is installed starts or shuts down, allowing it to run as a daemon.
Even if you choose not to install the init.d script during the installation, or if you do not perform the installation as the root user, the installer generates scripts that can perform the necessary setup.
These scripts are fglam-init-script-installer.sh and fglam-init-script.sh, and they are located in the <fglam_home>/state/default/ directory.
The script fglam-init-script-installer.sh installs the script fglam-init-script.sh into your system’s init.d directory as dell-fglam. Your system’s init.d process then uses dell-fglam to run the Agent Manager as a daemon.
2
Optional. If you want to make any edits to fglam-init-script.sh to customize it for your system, do so prior to running fglam-init-script-installer.sh.
IMPORTANT: Any customizations that you make to the script fglam-init-script.sh are not supported by Dell Inc..
4
From the command shell, run the script fglam-init-script-installer.sh with the install option:
The setup script fglam-init-script-installer.sh installs the init.d script dell-fglam. See Locating the init.d script for the location in which it is installed.

Locating the init.d script

Previous Next


Depending on the operating system you are running, the init.d-style script dell-fglam is installed to a different location either by the Agent Manager installer or after you run the script fglam-init-script-installer.sh.
The locations of the installed init.d script (listed by operating system) are as follows:
AIX®: /etc/rc.d/init.d
All Linux® operating systems: /etc/init.d
HP-UX: /sbin/init.d
Oracle Solaris®: /etc/init.d
NOTE: The location of the init.d script depends only on the type of operating system, not on the specific architecture. For example, the location is the same for HP-UX running on either PA‑RISC or Itanium, or for Oracle Solaris® running on either SPARC or x86.

Obtaining the Agent Manager daemon status

Previous Next


In addition to starting or stopping the Agent Manager process, the init.d script allows you to obtain the status of the daemon process when you run the script with the status option. When the status option is specified with the init.d script, the script returns one of the following status codes:
0: The Agent Manager daemon process is running.
1: The Agent Manager daemon process is dead and a pid file is generated.
3: The Agent Manager daemon process is not running.
4: The Agent Manager daemon process status is unknown.

Configuring Agent Manager agent privileges

Previous Next


On UNIX® systems, certain Foglight agents require elevated privileges in order to gather the required system metrics. This is achieved by having the Agent Manager launch these agents with root privileges.
To give these agents the required access, the Agent Manager is configured to launch these agents using an external application like sudo, setuid_launcher, or any other tool that allows privilege escalation (without a password) and supports the same command‑line semantics as sudo.
NOTE: The tool setuid_launcher is included with the Agent Manager, in the <fglam_home>/bin/setuid_launcher directory.
Instructions for using sudo and setuid_launcher to give these agents the necessary privileges are provided below.
Related Documents