|xref:dnf.adoc[DNF] package installation messages|
|works in libvirt>=0.8.2|
|What is logged remotely|
|`tty3` and `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` link:https://anaconda-installer.readthedocs.io/en/latest/boot-options.html#inst-loglevel[command line option].|
|This builds a file `/tmp/anaconda-tb-?????` that also contains `anaconda.log`, `storage.log` and `syslog`.|
|The remote syslog configuration exploits several log message characteristics to be able to sort them into the correct files:|
|The remote logging only works when the installer initializes network. Once network is up, it takes a couple of minutes for rsyslogd to realize this. Rsyslog has a queue for messages that couldn't be forwarded because of inaccessible network and it eventually forwards all of them, in the correct order.|
|There are two other log files created on the target filesystem, in the `/root` directory, also accessible at `/mnt/sysimage/root` during the installation:|
|the IP of the message sender to know which machine generated the message and thud what directory does the message belong to.|
|the general installation information, particularly the step changes.|
The anaconda RPM provides the `analog` script, 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:
`$ eval 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 `/home/akozumpl/remote_inst/10.34.33.221/`, e.g. `/home/akozumpl/remote_inst/10.34.33.221/anaconda.log`.