Chatta subito con l'assistenza
Chat con il supporto

Foglight Agent Manager 5.9.5 - 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

Using setuid_launcher to configure secure launcher permissions

Using setuid_launcher to configure secure launcher permissions

This section contains instructions for using setuid_launcher to give agents elevated permissions.

To set up secure launcher permissions using the configuration interface and setuid_launcher:
1
Follow the instructions in To launch the Agent Manager Installation and Configuration interface: or To launch the Agent Manager configuration command-line interface: .
2
Navigate to the Configure Secure Launcher screen or the Secure Launcher step.
3
Set the path to point to the setuid_launcher executable. This executable is located in <fglam_home>/bin/setuid_launcher.
4
Exit from the configuration interface as described in To launch the Agent Manager Installation and Configuration interface: or To launch the Agent Manager configuration command-line interface: .
5
Use the command chmod u+s to set the sticky bit on <fglam_home>/bin/setuid_launcher.
6
Change the owner of <fglam_home>/bin/setuid_launcher to root. This permits the agents that need root privileges to be run as the root user without requiring a password.

If these permissions are no longer needed, issue the following command:

chmod u-s <fglam_home>/bin/setuid_launcher

To set up secure launcher permissions using fglam.config.xml and setuid_launcher:
1
Navigate to <fglam_home>/state/default/config.
2
Open the fglam.config.xml file for editing.
3
Edit the <config:path> element under <config:secure-launcher> to point to your local setuid_launcher executable. This executable is located in <fglam_home>/bin/setuid_launcher.
4
Issue the command chmod u+s to set the sticky bit on <fglam_home>/bin/setuid_launcher.
5
Change the owner of <fglam_home>/bin/setuid_launcher to root. This permits the agents that need root privileges to be run as the root user without requiring a password.
6
If these permissions are no longer needed, issue the command:
chmod u-s <fglam_home>/bin/setuid_launcher

Using the HP patch checking tool

If your database is installed on an HP-UX server, HP® provides a tool for ensuring that all the patches required to run JavaTM on HP-UX are installed.

The tool is available from http://www.hp.com/go/java.

To use the tool, issue the following command:

java -jar ./HPjconfig.jar -nogui -patches -listmis -javavers 6.0

About Agent Manager installations on AIX

About Agent Manager installations on AIX

On newly installed AIX® systems, the base operating system can be further customized by the install_assist program provided by IBM®. By default, this program is listed in the /etc/inittab file so that it starts automatically when the system is started.

When install_assist runs automatically, it can interfere with the Agent Manager startup scripts that are installed in /etc/rc.d/rc2.d, and with other startup scripts, such as those provided by OpenSSH.

To prevent install_assist from starting automatically:
1
Edit the /etc/inittab file.
 
* 
TIP: You can edit the file directly, or by running the following command as root:

# rmitab install_assist

2
Remove the following line from the /etc/inittab file:
install_assist:2:wait:/usr/sbin/install_assist </dev/console >/dev/console 2>&1

Preventing Agent Manager core dumps on Linux

Installing and running the Agent Manager on a Linux® machine with several interfaces can result in a core dump with the following console output:

*** glibc detected ***
...
malloc(): memory corruption:
...
Java_java_net_NetworkInterface_getAll+0x8c

This error is related to a known JavaTM 6 issue, JDK-7078386. This issue is resolved in Java 7. For more information about JDK-7078386, you can visit http://bugs.java.com/bugdatabase/view_bug.do?bug_id=7078386.

To prevent an Agent Manager core dump on a Linux machine:
1
Before installing the Agent Manager, install Java 7 update 45 on the machine where you plan to install the Agent Manager.
2
On this machine, install the Agent Manager, and navigate to the following directory: <fglam_home>/state/default/config.
3
In this directory, locate and open the vm.config file for editing.
4
In the vm.config file, search for the java.vm property, and edit its value to point to the new JDK 7 installation.
5
Save your changes to the vm.config file, and close it.
6
Start up the Agent Manager.

 

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione