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/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/syslog, messages from kernel and external programs (Network Manager)
/tmp/yum.log, yum's internal log
Certain log messages are also written to the terminals.
/dev/tty3, messages from
/dev/tty4, same as
/dev/tty5, stdout and stderr from external programs
tty4 reflect certain log files. Log files always contain messages from all the loglevels, including debug, but the minimal loglevel on the terminals can be controlled with the
loglevel command line option.
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.
In files the format of the log messages is as follows:
H:M:S,ms LOGLEVEL facility:message
H:M:Sis the message timestamp
msis the millisecond part of timestamp. Note that this will usually become zero on a remote syslog.
LOGLEVELis the message loglevel. In theory, because kernel messages are part of anaconda logs, all loglevels that are defined in rsyslog can appear in the logfiles. Anaconda itself will however log only at the following loglevels:
facilityis the program or component that created the message. Could be for instance
messageis the log message itself.
For the logs running in terminals, the format simply is:
Anaconda supports remote logging 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
syslogcommand line option. Do not forget to enable the port you are running your local syslog daemon on in firewall."
It's up to you how the remote logging daemon is configured, you can for instance log all incoming messages into one file or sort them into directories according to the IP address of the remote system.
The anaconda RPM provides the
analogscript, which generates a suitable rsyslogd configuration file based on a couple of install parameters. It is also able to generate a bash command to launch rsyslogd with the generated configuration. Thus you can do from a shell:
scripts/analog -p 6080 -s -o ./someconf /home/akozumpl/remote_inst
This starts an rsyslog daemon that will listen on port 6080. The logs from the remote machine with IP 10.34.33.221 will be stored under
The remote syslog configuration exploits several log message characteristics to be able to sort them into the correct files:
- the IP of the message sender to know which machine generated the message and thud what directory does the message belong to.
program.loghave the name embedded in them as
syslog/code> messages are coming in from kernel and daemon facilities, just like they do on the installed system
install.log.syslogmade during package installation is logged as a special
-ooption to see how exactly does a fitting configuration file look like. Also notice that it uses the same message format for remote logging as anaconda does, but you can of course modify this to specify any format you want.\
- Rsyslog documentation
- man tailf
The current list of logging requirements and tasks is maintained in bugzilla 524980.