Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have installed mcelog in RHEL 6.1 x64bit. I have doubt in this. Currently there is no logs updated in /var/log/mcelog. Is there a way to test whether mcelog is working properly. /var/log/mcelog is not getting updated. Is there any configuration change to be made in /etc/mcelog/mce.conf file.
mcelog version is mcelog-1.0pre3_20101112-0.6.el6.x86_64
mcelog --client -------Does not produce any o/p
Now I do not know whether MCElog is working properly or not
Normally, you wouldn't expect any entries in the mcelog. It reports machine check exceptions, which are serious hardware errors. If you don't see any errors logged, that's a good sign! Of course, you may still have flakey hardware, but if it's not being stressed the problems might not show up. Are you running CPU or memory intensive programs on the machine? You could always run hardware diagnostic/stress test tools (e.g. memtest86+ for memory) on the hardware to see if they report errors.
My MCElog conf looks like this. Syslog is not used in my machine. Is this conf fine. Except /tmp/logfile. No logs are logged. I doubt whether mcelog is working fine or not. Can anyone send a link which explains mcelog options in mcelog.conf. I went through man page and mcelog --help. But still, I need info on options like "optionname, filter,
[root@server mcelog]# cat /etc/mcelog/mcelog.conf
# Example config file for mcelog
# mcelog is the user space backend that decodes and process machine check events
# (cpu hardware errors) reported by the CPU to the kernel
# general format
#optionname = value
# white space is not allowed in value currently, except at the end where it is dropped
# in general all command line options that are not commands work here
# see man mcelog or mcelog --help for a list
# e.g. to enable the --no-syslog option use
#no-syslog = yes (or no to disable)
# when the option has a argument
logfile = /tmp/logfile
# below are the options which are not command line options
# Set CPU type for which mcelog decodes events:
cpu = intel
# for valid values for type please see mcelog --help
# If this value is set incorrectly the decoded output will be likely incorrect.
# by default when this parameter is not set mcelog uses the CPU it is running on
# on very new kernels the mcelog events reported by the kernel also carry
# the CPU type which is used too when available and not overriden.
# Enable daemon mode:
daemon = yes
# By default mcelog just processes the currently pending events and exits.
# in daemon mode it will keep running as a daemon in the background and poll
# the kernel for events and then decode them.
# Filter out known broken events by default
filter = yes
# don't log memory errors individually
# they still get accounted if that is enabled
filter-memory-errors = no
# output in undecoded raw format to be easier machine readable
# (default is decoded)
raw = yes
# Set CPU Mhz to decode uptime from time stamp counter (output
# unreliable, not needed on new kernels which report the event time
# directly. A lot of systems don't have a linear time stamp clock
# and the output is wrong then.
# Normally mcelog tries to figure out if it the TSC is reliable
# and only uses the current frequency then.
# Setting a frequency forces timestamp decoding.
# This setting is obsolete with modern kernels which report the time
cpumhz = 2992.697
# log output options
# Log decoded machine checks in syslog (default stdout or syslog for daemon)
#syslog = yes
# Log decoded machine checks in syslog with error level
#syslog-error = yes
# Never log anything to syslog
no-syslog = yes
# Append log output to logfile instead of stdout. Only when no syslog logging is active
#logfile = filename
# Use SMBIOS information to decode DIMMs (needs root)
# This function is not recommended to use right now and generally not needed
# The exception is memdb prepopulation, which is configured separately below.
#dmi = no
# when in daemon mode run as this user after set up
# note that the triggers will run as this user too
# setting this to non root will mean that triggers cannot take some corrective
# action, like offlining objects
#run-credentials-user = root
# group to run as daemon with
# default to the group of the run-credentials-user
#run-credentials-group = nobody
# user allowed to access client socket.
# when set to * match any
# root is always allowed to access
# default: root only
client-user = root
# group allowed to access mcelog
# when no group is configured any group matches (but still user checking)
# when set to * match any
client-group = root
# path to the unix socket for client<->server communication
# when no socket-path is configured the server will not start
socket-path = /var/run/mcelog-client
# when mcelog starts it checks if a server is already running. timeout
# for this check.
initial-ping-timeout = 2
# Is the in memory DIMM error tracking enabled?
# Only works on systems with integrated memory controller and
# which are supported
# Only takes effect in daemon mode
dimm-tracking-enabled = yes
# Use DMI information from the BIOS to prepopulate DIMM database
# Note this might not work with all BIOS and requires mcelog to run as root.
# Alternative is to let mcelog create DIMM objects on demand.
dmi-prepopulate = yes
# execute these triggers when the rate of corrected or uncorrected
# errors per DIMM exceeds the threshold
# Note when the hardware does not report DIMMs this might also
# be per channel
# The default of 10/24h is reasonable for server quality
# DDR3 DIMMs as of 2009/10
#uc-error-trigger = dimm-error-trigger
uc-error-threshold = 1 / 24h
#ce-error-trigger = dimm-error-trigger
ce-error-threshold = 10 / 24h
# Memory error accounting per socket
socket-tracing-enabled = yes
# Threshold and trigger for uncorrected memory errors on a socket
# mem-uc-error-trigger = socket-memory-error-trigger
mem-uc-error-threshold = 100 / 24h
# Threshold and trigger for corrected memory errors on a socket
#mem-ce-error-trigger = socket-memory-error-trigger
#mem-ce-error-threshold = 100 / 24h
# Log socket error threshold explicitely?
#mem-ce-error-log = yes
# Processing of cache error thresholds reported by Intel CPUs
#cache-threshold-trigger = cache-error-trigger
# Should cache threshold events be logged explicitely?
#cache-threshold-log = yes
# Memory error accouting per 4K memory page
# Threshold for the correct memory errors trigger script
memory-ce-threshold = 10 / 24h
# Trigger script for corrected errors
# memory-ce-trigger = page-error-trigger
# Should page threshold events be logged explicitely?
memory-ce-log = yes
# specify the internal action in mcelog to exceeding a page error threshold
# this is done in addition to executing the trigger script if available
# off no action
# account only account errors
# soft try to soft-offline page without killing any processes
# This requires an uptodate kernel. Might not be successfull.
# hard try to hard-offline page by killing processes
# Requires an uptodate kernel. Might not be successfull.
# soft-then-hard First try to soft offline, then try hard offlining
#memory-ce-action = off|account|soft|hard|soft-then-hard
memory-ce-action = soft
# Maximum number of running triggers
children-max = 2
# execute triggers in this directory
directory = /etc/mcelog