English Spanish
After every successful installation, anaconda logs are copied into `/var/log` on the system you just installed. To avoid name clashes with other log files there, the anaconda logs are renamed:
| Name during installation | Name on the target system
| `/tmp/anaconda.log` | `/var/log/anaconda.log`
| `/tmp/syslog` | `/var/log/anaconda.syslog`
| `/tmp/X.log` | `/var/log/anaconda.xlog`
| `/tmp/program.log` | `/var/log/anaconda.program.log`
| `/tmp/storage.log` | `/var/log/anaconda.storage.log`
| `/tmp/yum.log` | `/var/log/anaconda.yum.log`
| `/tmp/ifcfg.log` (new in F14) | not copied
Starting with Fedora 15 (or post F14 Rawhide), the logs go to `/var/log/anaconda` directory on the target system, including ifcfg.log inroduced in F14.
Logging tips
If you are asked to provide logs for a bugzilla, your best option is switching from the anaconda GUI to tty2 and then use scp to copy the files to your computer, e.g.:
$ cd /tmp
$ scp anaconda.log aklap:/home/akozumpl/
It is also possible to make a complete dump of a state of running anaconda process (the same dump that is compiled automatically if an unhandled exception occurs). To do this send the main anaconda process SIGUSR2:
$ kill -USR2 `cat /var/run/anaconda.pid``
This builds a file `/tmp/anaconda-tb-?????` that also contains `anaconda.log`, `storage.log` and `syslog`.
If you are on a KVM virtual machine and there's no scp available (stage1), you can (after setting up the network if not up already) redirect to a special tcp file, on host:
$ nc -l 4444 > syslog.log
on guest:
$ ifconfig eth0 10.0.2.10/24 up
$ grep "" /tmp/syslog > /dev/tcp/10.0.2.2/4444