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.
1 |
On the navigation panel, under Dashboards, click Infrastructure. |
For more information about monitoring activities and exploring the data collected for the host, see the Foglight for Infrastructure User and Reference Guide.
To install cartridges, see Installing and Upgrading Cartridges.
-Dfoglight.database.upgrade=true
or run foglight_db_upgrade.sh.
To rectify this issue, you can perform one of the following workarounds:
• |
For more information about SELinux, consult your Linux® distribution vendor.
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.
ERROR [UDP mcast receiver] org.jgroups.protocols.UDP - message does not have a UDP header
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.
• |
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. |
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.
© ALL RIGHTS RESERVED. 利用規約 プライバシー Cookie Preference Center