On Thu, Aug 5, 2010 at 12:38, Ivan De Masi <it-support@asta.tu-darmstadt.de> wrote:

I'm trying to create new autoyast config files and when an installations fails the output is poor. Where can I get the y2log of autoyast to see in deep what's happening? Do I have to access the disk of the machine I tried to install or is it somewhere in "memory"?

If your installation grinds to a halt, you can switch to another virtual console (for example, ctrl-alt-f2 or "sendkey ctrl-alt-f2" in case of qemu-based VMs) and look at the files below the chroot in /tmp (iirc). AFAIK, you need access to the disk. For both the during-install method as described above as well as for the after-the-fact analysis, the important files are in the following directories below the (ch)root dir. (this is from my own documentation, sorry for possibly bad translation.) * /var/adm/autoinstall/ o cache/installedSystem.xml: the complete AutoYAST profile which this system received. o files/: if the profile contains files, here are copies of them. o scripts/: copies of scripts (eg. "myscript") and, if enabled, debug output with the suffix "-run" (eg. "myscript-run"). o logs/: everything that your scripts produced as output. * /var/log/YaST2/ (general install logs): o _dev_*: copies of the boot sectors o badlist: list of problems with packages o disk_*: information about your hard disk(s) o y2log-1: log of stage 1, usually about 50.000 lines o y2log: log of stage 2, usualy more than 10.000 lines o and more… If you suspect anything in particular, it is really helpful to search for related stuff in the logs. Like, for example, errors with gpg signature problems of your own repositories could be found when searching for "GpgSomething" (yes, the spelling differs from the names within your autoyast profile). To find out *what* to search for is the real hard part. Greetings, 686f6c6d -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org