Red Hat Hardware Error Log
Contents |
Red Hat Certificate System Red Hat Satellite Subscription Asset Manager Red Hat Update Infrastructure Red Hat Insights Ansible Tower by Red Hat Cloud Computing
Hardware Error Machine Check Events Logged Redhat
Back Red Hat CloudForms Red Hat OpenStack Platform Red Hat Cloud Infrastructure hardware error machine check events logged centos Red Hat Cloud Suite Red Hat OpenShift Container Platform Red Hat OpenShift Online Red Hat OpenShift Dedicated Storage
Hardware Error Machine Check Events Logged Ubuntu
Back Red Hat Gluster Storage Red Hat Ceph Storage JBoss Development and Management Back Red Hat JBoss Enterprise Application Platform Red Hat JBoss Data Grid Red Hat JBoss Web hardware event. this is not a software error Server Red Hat JBoss Portal Red Hat JBoss Operations Network Red Hat JBoss Developer Studio JBoss Integration and Automation Back Red Hat JBoss Data Virtualization Red Hat JBoss Fuse Red Hat JBoss A-MQ Red Hat JBoss BPM Suite Red Hat JBoss BRMS Mobile Back Red Hat Mobile Application Platform Services Back Consulting Technical Account Management Training & Certifications Red Hat mca: memory controller gen_channelunspecified_err Enterprise Linux Developer Program Support Get Support Production Support Development Support Product Life Cycle & Update Policies Knowledge Search Documentation Knowledgebase Videos Discussions Ecosystem Browse Certified Solutions Overview Partner Resources Tools Back Red Hat Insights Learn More Red Hat Access Labs Explore Labs Configuration Deployment Troubleshooting Security Additional Tools Red Hat Access plug-ins Red Hat Satellite Certificate Tool Security Back Product Security Center Security Updates Security Advisories Red Hat CVE Database Security Labs Resources Overview Security Blog Security Measurement Severity Ratings Backporting Policies Product Signing (GPG) Keys Community Back Discussions Red Hat Enterprise Linux Red Hat Virtualization Red Hat Satellite Customer Portal Private Groups All Discussions Start a Discussion Blogs Customer Portal Red Hat Product Security Red Hat Access Labs Red Hat Insights All Blogs Events Customer Events Red Hat Summit Stories Red Hat Subscription Benefits You Asked. We Acted. Open Source Communities Subscriptions Downloads Support Cases Account Back Log In Register Red Hat Account Number: Account Details Newsletter and Contact Preferences User Management Account Maintenance My Profile Notifications Help Log Out Language Back English
Linux discussion list
Transaction: Memory Scrubbing Error
Subject: Does redhat linux log all hardware events/issues/error in /var/log/mcelog? Date: Mon, https://access.redhat.com/solutions/298163 12 Mar 2012 18:28:23 -0400 Hi, We run redhat linux on intel hardware (mostly Dell, lately dell R710s). We want to be able to catch https://www.redhat.com/archives/redhat-list/2012-March/msg00001.html any hardware issues when they occur to act on them as quickly as possible. My understanding is that all hardware events/issues/errors are logged in /var/log/mcelog (Machine Check Events log). Is this correct? Can't stress this enough; does it log all hardware issues (cpu,memory,disk,ethernet,fibre/hba etc) ? Thanks, Follow-Ups: Re: Does redhat linux log all hardware events/issues/error in /var/log/mcelog? From: Paul Tader [Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]
of IP AddressesNext2.4. Viewing Logs Log files monitor activity for Admin Server and can help troubleshoot server problems. Admin Server logs use the Common Logfile Format, https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/8.2/html/Using_the_Admin_Server/Administration_Server_Basics-Logging_Options.html a broadly supported format that provides information about the server. Admin Server http://www.mcelog.org/ generates two kinds of logs: Access logs. Access logs show requests to and responses from the Admin Server. By default, the file is located at /var/log/dirsrv/admin-servaccess. Error logs. Error logs show messages for errors which the server has encountered since the log file was created. It also hardware error contains informational messages about the server, such as when the server was started and who tried unsuccessfully to log on to the server. By default, the file is located at /var/log/dirsrv/admin-serverror. The logs can be viewed through Admin Server Console or by opening the log file. 2.4.1. Viewing the Logs through the Console Open the Admin Server management window. Click the machine check events Configuration tab. Expand the Logs directory, and click the log file name, either Accesses or Error. 2.4.2. Viewing Logs in the Command Line The access log, by default, is at /var/log/dirsrv/admin-servaccess. To view the access log, open it in an editor such as vi. Access logs show connections to the Admin Server based on the IP address of the client, the username, and the method that the request was sent. Each line has the following format: ip_address - bind_DN [timestamp -0500] "GET|POST cgi" HTTP_response bytes Example logs are shown in Example 2.1, “Example Access Logs”. Example 2.1. Example Access Logs127.0.0.1 - cn=directory manager [23/Dec/2008:19:32:52 -0500] "GET /admin-serv/authenticate HTTP/1.0" 200 338 192.168.123.121 - cn=directory manager [23/Dec/2008:19:33:14 -0500] "POST /admin-serv/tasks/Configuration/ServerSetup HTTP/1.0" 200 244 192.168.123.121 - cn=directory manager [23/Dec/2008:19:33:16 -0500] "GET /admin-serv/tasks/Configuration/ReadLog?op=count&name=access HTTP/1.0" 200 10 The error log, by default, is at /var/log/dirsrv/admin-serverrors. To view the error log, open it in an editor such as vi. Error logs record any problem response from the Admin Server. Like the access log, error logs also records entries based the client's IP address, along with the type o
Flow References For Developers: Testing Logfile format Client protocol BIOS support Code README mcelog logs and accounts machine checks (in particular memory, IO, and CPU hardware errors) on modern x86 Linux systems. mcelog is required by both 32bit x86 Linux kernels (since 2.6.30) and 64bit Linux kernels (since early 2.6 kernel releases) to log machine checks and should run on all Linux systems that need error handling. The mcelog daemon accounts memory and some other errors errors in various ways. mcelog --client can be used to query a running daemon. The daemon can also execute triggers when configurable error thresholds are exceeded. This is used to implement a range of automatic predictive failure analysis algorithms: including bad page offlining and automatic cache error handling. User defined actions can be also configured. All errors are logged to /var/log/mcelog or syslog or the journal. For memory errors it supports modern x86 systems with integrated memory controllers; for CPU errors all modern x86 systems are supported. Traditionally mcelog was run as a cronjob, but this usage is deprecated now. The modern way to run it is to start it at boot up time and run it always as a daemon. In addition it can be used to decode fatal machine checks on the command line (but this is also usually not needed anymore on modern kernels which log those after reboot automatically) For installation information and how to set up a mcelog package (if you're a distributor) please see the README.