Chat now with support
Chat with Support

Foglight 5.9.5 - Installing Foglight on a UNIX System with an External MySQL Database

Before Installing Foglight Installing Foglight
Preparing to install Installing a new version of the Management Server Installed directories Foglight settings HP patch checking tool Uninstalling Foglight Upgrading the Management Server Installing Foglight FAQ
Running the Management Server Installing and Upgrading Cartridges Installing Agents

Monitoring the Management Server host

During the installation, or upgrade, a HostAgent is automatically created to monitor the host where the Management Server, the embedded Foglight Agent Manager, and embedded database run. The health of this host directly affects the health and performance of Foglight.

To view the HostAgent:
1
Start the Management Server.
For detailed information, see Starting the Management Server .
1
Log in to Foglight.
2
On the navigation panel, under Dashboards, click Administration > Agents > Agent Status.
3
On the Agent Status dashboard, find the UnixAgentPlus called EmbeddedHostMonitor.

Information about the status and data collection of the agent are available on this dashboard.

To view the data that the HostAgent collects for the Management Server host:
1
On the navigation panel, under Dashboards, click Infrastructure.
2
From the Select a Service list, select the service for the host.
3
On the Monitoring tab, select the host from the list.

For more information about monitoring activities and exploring the data collected for the host, see the Foglight for Infrastructure User and Reference Guide.

Next steps

To install cartridges, see Installing and Upgrading Cartridges.

Migrating data from an existing database

The contents of the MySQL® database can be copied to another MySQL instance via an export/import cycle.

The following procedure performs a full export of the database and can be run against a database currently in use by a server.

To export and import a MySQL database:
1
Run the following command from the MySQL command shell:
mysqldump -u <username> -p <password> -h <hostname> -P <port> --databases <database name> --routines --single-transaction > backup.sql
The -h parameter can be omitted if the database is on the same host.
2
Import the database using the following syntax:
mysql -u <username> -p <password> -P <port> < backup.sql
The import process recreates the tables in the database. Therefore, any data that was in the destination environment prior to the import is lost.
 
* 
NOTE: The Foglight servers must be stopped during the import process.

When moving a database between environments, care should be taken to ensure that the Foglight schema version is lower or equal to the Management Server version in the destination environment, as an upgrade to a new schema is possible. Start the Management Server with the option:

-Dfoglight.database.upgrade=true

or run foglight_db_upgrade.sh.

Running the Management Server FAQ

Why do I see an extra process named Quest Process Runner when I run Foglight?

On UNIX®, Foglight uses the Quest Common Process Runner to run processes such as the embedded database, the embedded Agent Manager, and command actions.

Why does the error message “cannot restore segment prot after reloc: Permission denied” appear when I start the Management Server?

Newer Linux® distributions have enabled new kernel security extensions from the SELinux project at the NSA (National Security Agency). SELinux is an NSA project to improve the security of Linux through Mandatory Access Control (MAC). These extensions allow finer-grained control over system security. However, SELinux also changes some default system behaviors, such as shared library loading, which can be problematic to third-party programs.

If you see the error message “cannot restore segment prot after reloc: Permission denied” when you start the Management Server, your SELinux configuration is preventing IDL (the Interface Definition Language) from launching.

To rectify this issue, you can perform one of the following workarounds:

•
Change the default security context for the Management Server by issuing the command:
chcon -t texrel_shlib_t <foglight_home>/jre/lib/i386/*.so
chcon -t texrel_shlib_t <foglight_home>/jre/lib/i386/server/*.so
•
Disable SELinux altogether by setting it to disabled in your /etc/sysconfig/selinux file:
SELINUX=disabled

For more information about SELinux, consult your Linux® distribution vendor.

I am running Foglight with a MySQL® database. When I try to start Foglight, it fails to start and an SQL exception appears in the logs. Why does this happen?

If you encounter this problem, the cause might be that the MySQL database file my.cnf has been made world-writable.

Do not make the MySQL database file my.cnf world-writable, for example by issuing the command chmod a+w <foglight_home>/mysql/my.cnf. Foglight and the database cannot start if there is world access to the configuration file my.cnf.

I am running Foglight in High Availability (HA) mode. When I start my Management Servers, “UDP mcast receiver” errors appear in the logs for the primary and secondary Management Servers. How can I resolve these errors?

If Management Servers that are not part of a particular HA partition are configured to multicast using the same port on the same subnet as the Management Servers within the HA partition, errors like the following appear in the logs for the Management Servers that are configured in this way:

ERROR [UDP mcast receiver] org.jgroups.protocols.UDP - message does not have a UDP header

or

ERROR [UDP mcast receiver] org.jgroups.protocols.UDP - discarded message from different group

If you see this type of message, change the cluster multi-cast port of the servers that are reporting the error. In addition, if you plan to have multiple High Availability (HA) partitions on the same sub-net, configure a different cluster multicast port for each HA partition. See Configuring the cluster multicast port used in High Availability mode for instructions.

 
* 
IMPORTANT: In both cases described here (resolving errors and planning to have multiple HA partitions on the same subnet), the primary server and secondary servers within each HA partition must be configured to use the same cluster multicast port.
If I stop the Management Server by closing the Command Prompt window, an error appears when I start up the server again. How do I restart the server?

It is recommended that you do not use this method to stop the Management Server. However, if you do use this method, follow the following workaround.

•
Remove the stale .pid file that is located in the state directory. The logs or the console output inform you which .pid file to remove when you restart the server.
Why does the “JavaScript Disabled” error message appear when I try to log in to Foglight?

The Foglight browser interface requires JavaScript. You may need to modify the security settings in your web browser to enable this functionality. Depending on your browser, this setting may be labeled either “Enable JavaScript” (for example, in Firefox®), or “Enable Active Scripting” (for example, in Internet Explorer®).

Why does clicking the login link on the server startup page not work?

The default link to the login page points to http://localhost:8080. In some instances, this link may not correspond to the URL of your Foglight server, resulting in the link not working. This issue can also occur when Foglight is not able to identify your local host. Add your host/IP information to the etc/hosts files to correct this issue.

Why does a link-local IPv6 address not work with the Foglight web user interface?

Configuring the Management Server with a link-local IPv6 address is not supported because many web browsers do not support link-local IPv6 addresses. To correct this issue, update your host/IP information in the etc/hosts file.

 

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating