Aix Error Log
Contents |
High Availability LPAR Networks Performance Security Systems Management Tivoli Virtualization Workload Management Cloud Computing IBM Announcements IBM Research Linux Open Source What's New Automotive Healthcare Manufacturing Miscellaneous Non-Profit Retail Application Development Migration Miscellaneous Systems Management Disk Flash Servers Software unix error log Tape AIX > Administrator > Systems Management Reviewing AIX Error and Boot Logs July solaris error log 2013 | by David Tansley Print AIX provides comprehensive logging of events—some are errors requiring attention and others are just notifications. For linux error log system administrators, tasked to make sure the system is running without major issues, logging provides alerts or apprises them of events as they happen. AIX offers different logs depending on the action and when it occurred. db2 error log These logs hold information on the boot-up process, console, hardware and system software events. It’s up to the system admin to take action on these events, because once AIX has published the log, its job is done. Logs, Logs, Logs AIX not only offers the errpt but also other error reporting logs. Using the alog command one can list and pick a log to view: # alog -L boot bosinst nim console cfg
Error Log Command
mdmplog lvmt lvmcfg dumpsymp When issues arise during the boot-up process, for example, and you’re not at the console, you can review the start-up process messages, particularly the boot and console messages. To list the available logs: alog -o -t For example, to view the console log: alog -o -t console Logging Your Own Entries The standard errpt list hardware or software events in AIX that have occurred. However, you might want a message generated and inserted into errpt after some user interaction, for instance, if a system admin has made a change. This allows the change notification to be visible via errpt. Like the logger command that writes to the system log (messages file), errlogger will write an operator notification entry to the error log. For example, having completed an AIX upgrade, you could post that to the error log, so other users could view it, like so: errlogger "AIX upgrade completed - no errors- test" Working With errpt The first thing AIX admins should do is get event notifications via email. Those errors/warnings will be emailed as well as posted to the errpt log. First, create an email alias containing all system admins’ addresses in the /etc/mail/aliases file. Insert the email alias into the notification list, using the following smit selections: smit diag, current shell
errreporter script. Download the sample errreporter.conf configuration file. The AIX Error Logging Facility Sandor W. Sklar The primary goal of every UNIX systems http://web.stanford.edu/~ssklar/errreporter/article.html administrator is to ensure that the systems that they are responsible for are functioning smoothly and with the best performance possible, 100% of the time. File systems running out http://www.softpanorama.org/Commercial_unixes/AIX/managing_aix_logs.shtml of space, applications dumping core, and Ethernet adapter failures are just a sample of the types of things that can trip up a system, impacting that goal. Therefore, error log it is critical that the people responsible for a system are aware of anything that might have an impact on attaining that 100% system availability. One of the things that makes AIX my favorite flavor of UNIX is that, besides all the standard tools, daemons, and configuration files that are present in all flavors of UNIX, IBM has aix error log provided a number of enhancements that make the monitoring, reliability, and administration of RS/6000 systems second to none. This article will focus on one of those tools: the error logging facility. I'll show you how the AIX error logging facility works, then I'll present a program I wrote that checks the log for error messages, filters out any error messages you wish to ignore, and sends an email to the systems administrator. The Error Logging Subsystem On most UNIX systems, information and errors from system events and processes are managed by the syslog daemon (syslogd); depending on settings in the configuration file /etc/syslog.conf, messages are passed from the operating system, daemons, and applications to the console, to log files, or to nowhere at all. AIX includes the syslog daemon, and it is used in the same way that other UNIX-based operating systems use it. In addition to syslog, though, AIX also contains another facility for the management of hardware, operating system, and application messages and errors. This facility, while simple in it
Recommended Papers Reference Logs Analysis Syslog Syslog MultiTail Syslog Configuration Examples Log analyzers Logger Logrotate AIX security AIX Hardening TEC logfile Adapter Compiling Apache on AIX Compiling PHP on AIX Humor Etc AIX use both the BSD syslogd daemon and AIX proprietary error logging facilities, with a number of function-specific log files to record error events on each node. Most AIX components report errors using the errdemon daemon, an idiosyncratic AIX solution which is totally different from the BSD syslog facility. For example AIX kernel does not use syslog for error logging. In AIX the syslogd daemon is not activated by default. You need to perform several steps in order to be able to use it the way it is used on Solaris and Linux: Increase the size of AIX Error Log facility logs (as native AIX logging system it contains additional diagnostic information in error messages, which is useful for troubleshooting). Create syslog.conf manually and specify log rotation parameters (unique, but very useful feature of AIX syslogd daemon implementation) The syslogd daemon does not create files unless they already exist. Touch required to create log files. After then you need to restart the daemon or ask it to reread config file with kill -HUP Ensure forwarding of the messages from the AIX Error Log facility. Optionally integrate log processing into Tivoli (via TEC logfile Adapter) or some other ESM system. You can also use Apache+PHP based open source log processing systems on AIX (see Compiling Apache on AIX and Compiling PHP on AIX ) The AIX Error Log facility is configured by default to write files just one megabyte in size. When the log fills up, it wraps around and overwrites existing entries. Therefore, you should set the size to at least 40MB. You can do this once for all nodes with the dsh command after the nodes are installed. dsh -a /usr/lib/errdemon -s 40960000 AIX syslogd implementation of SYSLOG has built-in log rotation capabilities that are specified with optional fields after the log destination: facility-level destination rotate size s files n time t compress archive path For example: *.emerg;*.alert;*.crit;*.warning /var/adm/messagesrotate files 4 time 7d compress This is probably the most clean