Show Table of Contents
8.5. Monitoring Node and Gear Activity
Problems with node hosts can affect a single gear, several gears, or all the gears on the host. A common indication of a node host problem is an inability to create or remove gears on that host.
8.5.1. Default Node Log File Locations
By default, node components write log messages locally to their configured log file destination. The following table provides the default locations of important log files for node components, summarizes the information they contain, and identifies the configuration setting that changes their default location:
Table 8.4. Node Log Files
| File | Description | Configuration Setting |
|---|---|---|
/var/log/openshift/node/platform.log | Primary log for node platform actions including MCollective actions performed on the node host. | PLATFORM_LOG_FILE setting in /etc/openshift/node.conf. |
/var/log/openshift/node/platform-trace.log | Logs node platform trace actions. | PLATFORM_TRACE_LOG_FILE setting in /etc/openshift/node.conf. |
/var/log/openshift/node/ruby193-mcollective.log | Logs MCollective messages communicated between broker and node hosts. Read to confirm proper gear creation. | logfile setting in /opt/rh/ruby193/root/etc/mcollective/server.cfg. |
/var/log/httpd/openshift_log | Logs gear access from the front-end Apache. | APACHE_ACCESS_LOG setting in /etc/openshift/node.conf. |
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.