From Fedora Project Wiki
(Created page with '== To do == The current list of logging requirements is maintained in bugzilla [https://bugzilla.redhat.com/show_bug.cgi?id=524980 524980].')
 
No edit summary
Line 1: Line 1:
== Introduction ==
Anaconda tracks all of its activities in logs. This includes:
* changing installation steps (that roughly correspond to different screens in the graphical installer)
* storage devices detection and manipulation
* installation media detection
* network initialization
* kernel messages
* calls to critical methods within anaconda
* calls to external programs
== Logging on the installed system ==
During the installation the logs are stored in the <code>/tmp</code> directory:
* <code>/tmp/anaconda.log</code>, the general installation information, particularly the step changes.
* <code>/tmp/storage.log</code>, storage devices scan and manipulation (hard drives, partitions, LVM, RAID), partitioning
* <code>/tmp/program.log</code>, calls to external programs, their output
* <code>/tmp/messages.log</code>, messages from kernel and external programs (Network Manager)
There are two other log files created on the target filesystem, in the <code>/root</code> directory, also accessible at <code>/mnt/sysimage/root</code> during the installation:
* <code>/mnt/sysimage/root/install.log</code>, log of the package installation process.
* <code>/mnt/sysimage/root/install.log.syslog</code>, messages from installation chroot logged through the system's syslog. Mostly information about users and groups created during yum's package installation.
== Remote logging ==
In the anaconda from Fedora 13 onwards, remote logging is handled through the rsyslog daemon running on the installed system. It can be configured to forward its logs through TCP to an arbitrary machine in network that is also running a syslog daemon. This is controlled with the <code>syslog=</code> [[Anaconda/Options|command line option]]
== To do ==
== To do ==
The current list of logging requirements is maintained in bugzilla [https://bugzilla.redhat.com/show_bug.cgi?id=524980 524980].
The current list of logging requirements and tasks is maintained in bugzilla [https://bugzilla.redhat.com/show_bug.cgi?id=524980 524980].
 
This page:
* remote logging details
* tty logging

Revision as of 16:50, 21 January 2010

Introduction

Anaconda tracks all of its activities in logs. This includes:

  • changing installation steps (that roughly correspond to different screens in the graphical installer)
  • storage devices detection and manipulation
  • installation media detection
  • network initialization
  • kernel messages
  • calls to critical methods within anaconda
  • calls to external programs

Logging on the installed system

During the installation the logs are stored in the /tmp directory:

  • /tmp/anaconda.log, the general installation information, particularly the step changes.
  • /tmp/storage.log, storage devices scan and manipulation (hard drives, partitions, LVM, RAID), partitioning
  • /tmp/program.log, calls to external programs, their output
  • /tmp/messages.log, messages from kernel and external programs (Network Manager)

There are two other log files created on the target filesystem, in the /root directory, also accessible at /mnt/sysimage/root during the installation:

  • /mnt/sysimage/root/install.log, log of the package installation process.
  • /mnt/sysimage/root/install.log.syslog, messages from installation chroot logged through the system's syslog. Mostly information about users and groups created during yum's package installation.

Remote logging

In the anaconda from Fedora 13 onwards, remote logging is handled through the rsyslog daemon running on the installed system. It can be configured to forward its logs through TCP to an arbitrary machine in network that is also running a syslog daemon. This is controlled with the syslog= command line option

To do

The current list of logging requirements and tasks is maintained in bugzilla 524980.

This page:

  • remote logging details
  • tty logging