Converse agora com nosso suporte
Chat com o suporte

Foglight 5.9.3 - High Availability Field Guide

Redirecting secondary Management Servers to the correct URL

When Foglight® Management Servers are configured as an HA cluster, the browser interface for each of the secondary Management Servers redirects to the primary Management Server. By default, the URL for the browser interface to which the secondary Management Servers are redirected is generated automatically by Foglight based on the primary Management Server machine’s host name.

You can override this URL and point Foglight to a different URL by starting the secondary Management Servers from the command-line with the following option:

where <host_name> is the desired host name or Fully Qualified Domain Name (FQDN).

Use this option in cases where a single machine hosts multiple applications (including Foglight) and is configured with multiple host names and IP addresses. In such cases:

You can base the URL on the alias using the -D option.

You have two machines, whose host names are server1 and server2. You have an HA cluster running on these machines. The primary Management Server runs on server1 and the secondary Management Server runs on server2.

Both machines have two IP addresses: one internal and one external. The external IP addresses are bound to the DNS (Domain Name System) names foglight1.example.com and foglight2.example.com. Foglight has been bound to the external IP addresses and is not listening on the internal IP addresses. In this case, the Foglight browser interface is available at
http://foglight1.example.com:8080.

However, the secondary server redirects to the default URL http://server1:8080. In this case, the Foglight browser interface is not available at this URL. To resolve this issue, override the URL with: -Dquest.host.name=foglight1.example.com.

Remote Monitor

The Remote Monitor is a JavaTM program that regularly communicates with a set of High Availability (HA) servers. If there is no reply after it attempts to contact the server, then it logs the event and (optionally) sends e-mail notifications to an administrator.

The Remote Monitor takes a list of host names or host name and port pairs as parameters. When invoked without parameters, Remote Monitor takes the list of host names or host name and port pairs from the file <foglight_home>/config/remote_monitor.config under the entry server.urls.

Each parameter in the entry server.urls points to a specific HA server. If a port is not specified as part of this entry, the default port 51231 is used. The default port can be configured in <foglight_home>/config/remote_monitor.config, under the entry health.monitor.port. This entry should match the health.monitor.port entry in the file <foglight_home>/config/restart_monitor.config on your servers.

Copy the <foglight_home>/tools/remote_monitor.zip file to your target machine and unzip the contents to a directory.

On UNIX®, enter the command:

On Windows®, do one of the following:

Enter the command: <foglight_home>\bin\remotemonitor.exe
Choose Start > Programs > Quest > Foglight > High Availability > Start Remote Monitor.

Do one of the following:

Enter Ctrl-C from the command shell or window where the Remote Monitor started.
On UNIX®, enter the command: <foglight_home>/bin/remotemonitor <hostname<:port>> -q
On Windows®, choose Start > Programs > Quest > Foglight > High Availability > Stop Remote Monitor
Enter the command: <foglight_home>\bin\remotemonitor.exe -q

Enabling email notification for High Availability

Servers running in High Availability (HA) mode can send out email notifications in various situations, such as when servers stop responding or on failure to restart a server. The files <foglight_home>/config/restart_monitor.config and <foglight_home>/config/remote_monitor.config control how email notification functions, such as email protocols, email server information, and the message and recipients for each situation. Email can be sent out from the HA server or from the Remote Monitor. See the comments in these configuration files for more information about email notification.

Starting and stopping the HA server from the command line

The fmsha command provides a command-line interface to the Management Server process running in High Availability (HA) mode. Running Foglight® in HA mode allows you to manage multiple instances of the Management Server in a JGroup partition that supports the HA feature.

This command offers a set of options that you can use to perform any of the following operations as required:

Configure JavaTM Virtual Machine (JVM) options and add entries to the Foglight classpath
fmsha [-s|--start] [-q|--stop] [-w|--wait] [-n|--name process_name]
[-i|--install-service] [-r|--remove-service] [-b|--start-service]
[-j|--jvm-argument JVM_options] [-p|--classpath class_path] [-v|--version]
[-h|--help] [-t|--thread-dump] [-m|--javavm path_to_JAVA_HOME]
[-D|-X JVM_option] [--set-global-debug-level debug_level]
[--add-debug-level package_1.=debug_level_1package_n.=debug_level_n]
[--remove-debug-level package_1.package_n.]
fmsha [-d|--daemon] [-s|--start] [-q|--stop] [-w|--wait]
[-n|--name process_name] [-j|--jvm-argument JVM_options]
[-p|--classpath class_path] [-v|--version] [-h|--help] [-t|--thread-dump]
[-m|--javavm path_to_JAVA_HOME] [-D|-X JVM_option]
[--set-global-debug-level debug_level]
[--add-debug-level package_1.=debug_level_1package_n.=debug_level_n]
[--remove-debug-level package_1.package_n.]
UNIX® and Windows®

add-debug-level

package.=debug_level

Specifies a debug level for one or more packages. Higher debug levels result in more detailed logging. For example, you can set the debug_level to one of the following values:

0: No debugging

1: Minimal debugging

2: Detailed debugging

The period '.' following the package name is mandatory, otherwise the package is treated as a class. The package.=debug_level argument can be specified multiple times.

D

X

JVM_option

Passes an option to the JVM.

h

help

None

Displays a list of arguments and their descriptions.

j

jvm-argument

JVM_options

Specifies one or more JVM options.

m

javavm

path_to_JAVA_HOME

Points to the JVM for the Management Server process.

n

name

process_name

Specifies a unique process name for the current instance of the Management Server. Foglight uses process names to distinguish between different instances of the same process launcher.

p

classpath

class_path

Adds entries to the JVM classpath.

q

stop

None

Stops the running Management Server process.

remove-debug-level

package.

Removes a debug level associated with one or more packages. The period '.' following the package name is mandatory, otherwise the package is treated as a class. The package. argument can be specified multiple times.

s

start

None

Starts the Management Server.

set-global-debug-level

debug_level

Sets the global debug level. The debug_level argument must be a non-negative integer. Higher debug levels result in more detailed logging.

For example, you can set the debug_level to one of the following values:

0: No debugging
1: Minimal debugging
2: Detailed debugging

t

thread-dump

None

Requests a thread output from the running application. This option writes the output to a separate log file in the application's installation directory.

v

version

None

Displays the version number, copyright, build number, and the installation directory.

w

wait

None

When sending a shutdown command to an existing Management Server process, this option instructs the command to wait indefinitely for the process to exit before shutting it down.

d

daemon

None

Starts the Management Server as a daemon process.

b

start-service

None

Starts the Management Server Windows service.

i

install-service

None

Installs the Management Server as a Windows service.

r

remove-service

None

Stops and removes the Management Server Windows service.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação