此内容没有您所选择的语言版本。
8.8.2. Enabling Syslog for Node Components
You can configure node hosts to send node platform and Apache logs to Syslog instead of writing to their default log file locations. After enabling Syslog logging, messages from the various node components are grouped and sent to the configured Syslog implementation. This method of aggregating log messages gives you the option to further configure your Syslog implementation to send logs directly to a remote logging server or monitoring solution without the messages being written locally to disk.
Note
Instructions for configuring a Syslog implementation to route to alternate destinations, such as a remote logging server, are outside of the scope of this guide. The implementation provided by Red Hat Enterprise Linux 6 is Rsyslog, which writes to the
/var/log/messages
file by default. See the Red Hat Enterprise Linux 6 Deployment Guide for information on viewing and managing log files if using Rsyslog.
Procedure 8.4. To Enable Syslog for Apache:
- Configure Apache to send log messages to Syslog by adding the following option in the
/etc/sysconfig/httpd
file:OPTIONS="-DOpenShiftFrontendSyslogEnabled"
OPTIONS="-DOpenShiftFrontendSyslogEnabled"
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Important
All options must be on the same line. For example, in Section 8.5.2, “Enabling Application and Gear Context in Node Component Logs” another option for Apache log files is explained. If both options are desired, the line must use the following syntax:OPTIONS="-Option1 -Option2"
OPTIONS="-Option1 -Option2"
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Restart the
httpd
service for the Apache changes to take effect:service httpd restart
# service httpd restart
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Procedure 8.5. To Enable Syslog for the Node Platform:
- Configure the node platform to send log messages to Syslog by editing the
/etc/openshift/node.conf
file. Add the following line and any or all of the described optional settings that follow:PLATFORM_LOG_CLASS=SyslogLogger
PLATFORM_LOG_CLASS=SyslogLogger
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Optional Threshold Setting:Add the following line to include messages with priorities up to and including the set threshold. Replace
priority
in the following line with one of the levels listed at http://ruby-doc.org/stdlib-1.9.3/libdoc/syslog/rdoc/Syslog.html#method-c-log:PLATFORM_SYSLOG_THRESHOLD=priority
PLATFORM_SYSLOG_THRESHOLD=priority
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Optional Trace Log Setting:Add the following line to include trace logs that were previously directed to the default
/var/log/openshift/node/platform-trace.log
file:PLATFORM_SYSLOG_TRACE_ENABLED=1
PLATFORM_SYSLOG_TRACE_ENABLED=1
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Restart the
ruby193-mcollective
service for the node platform changes to take effect:service ruby193-mcollective restart
# service ruby193-mcollective restart
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - When Syslog support is enabled for the node platform, the
local0
Syslog facility is used to log messages. By default, the/etc/rsyslog.conf
file does not log platform debug messages. If you are using Rsyslog as your Syslog implementation, add the following line to the/etc/rsyslog.conf
file to enable platform debug message logging. If necessary, replace/var/log/messages
with your chosen logging destination:local0.*;*.info;mail.none;authpriv.none;cron.none /var/log/messages
local0.*;*.info;mail.none;authpriv.none;cron.none /var/log/messages
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Then restart thersyslog
service:service rsyslog restart
# service rsyslog restart
Copy to Clipboard Copied! Toggle word wrap Toggle overflow With this change, all log messages using thelocal0
facility are sent to the configured logging destination.