August 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

sles9: distribution-release not available
by Cosmo King 25 Aug '04

25 Aug '04

When configuring Autoyast for SLES9, and selecting "Software Selection" -> "Detailed Selection", I see the dependency conflict "aaa_base requires distribution-release" "distribution-release not available". I have not seen any packages named "distribution-release". Am I missing something? Thanks! Cosmo

1 0

More control...
by Anas Nashif 25 Aug '04

25 Aug '04

Hi, Some people in the past have been asking about how to have more control of the workflow and what is going on during manual and auto installations. Since 9.1, we have something new controling the whole installation phase. Some of you might have noticed a file named control.xml on the first CD. This file basically takes care of what dialogs should be shown and what the installation proposals should look like. It can either be customized for manual or automated installations. It also has some advanced features for manual installation which in most cases influence the initial installation proposal, i.e. partitioning and other global settings. Take a look at http://www.suse.de/~nashif/autoinstall/control.pdf. (Work in progress) The syntax is similar to this used for autoinstallation. Warning: Any change in this file will change the standard installation and might have unwanted results. So you should know exactly what you are doing. Anas

1 0

"No keyboard detected" when installing SuSE9.1 with textmode=1
by Voss Stefan 24 Aug '04

24 Aug '04

Hi folks, Whenever I (auto)install a Dell Optiplex GX60 using SuSE9.1 with the boot parameter 'textmode=1' the boot process stops shortly after Yast is started with the message: "starting yast... No keyboard detected. Trying to connect via serial interface /dev/ttyS0. On your terminal computer start the user interface with y2base "serial(115200):/dev/ttyS0" qt --fullscreen --noborder --auto-fonts ... " The behaviour is the same whether starting the installation process manually from cdrom or netbooting the machine using pxe. Of course, there is a keyboard connected to the machine and the boot messages show that it is detected correctly. It does not happen with SuSE 9.0. It does also not happen without textmode=1, i.e. during a normal manual installation which uses X11. It seems that yast cannot determine the keyboard and/or the console in this configuration. Does somebody know this error? I know this is a little OT, but textmode=1 is probably most often used in combination with autoinstall. Regards, Stefan Voss

1 0

Re: [suse-autoinstall] Could not format /dev/hda2
by Anthony Staples 23 Aug '04

23 Aug '04

Hello, I am encountering the following problem with autoinstall process. 1) I manually install NLD 1.6 on a reference machine, Dell GX60. 2) I create a reference profile on the DELL GX60 using YAST and autoinstall module. 3) I reboot the _reference_ machine from bootable CD for autoyast and autoinstall runs and installs NLD on the machine. 4) At this point all _seems_ well. 5) I boot a different GX60 with identical hardware and specs from the same CD for autoinstallation. 6) Yast fails during format of /dev/hda2 with the following error: "Could not format /dev/hda2. you can continue if you know what you are doing, but, to prevent damage to your filesystems, it is safer to cancel and reboot" However, if the error is ignored, since I want to re-install the target machine, files seem to copy and then the install fails later with lots of missing files. Seems as tho' my reference profile is only good for the original reference machine, which doesn't make much sense... Any insights or help appreciated!!! Regards, Tony The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.

2 1

YOU problem with SuSE 8.1
by Axel Wagner 23 Aug '04

23 Aug '04

Hello, The YaST2 online update stopped working on one of my systems. Here is what happened: I tried to update an older SuSE 8.1 system, which was offline most of the time. I started the YaST2 online update. The update first loaded some updates on YOU itself. I had to restart the online update 2 times. Then it started to download a large number of packages. Unfortunately, there was not much space left on the system, and during the download the system ran out of disk space. The update aborted. I removed some files and have enough space now (about 900MB). But the online update does not work any more. After starting it, it says "Initialisierung für FTP/HTTP-Update... Einen Moment bitte..." and after some seconds "Keine Verbindung zu www.suse.de möglich. Bitte überprüfen Sie die Verbindung." (Note: I'm using the text version of YasT2 on a german system) I checked on our firewall, but I could not find any package going out to www.suse.de. However, ping and ftp to that server work well, so I don't think it's a problem with the connection. I found a note on SuSE's web site that behind firewall, it could help to set wget to passive ftp downloads. I did that by changing /etc/wgetrc, as recommended. Did not help. And, BTW, the first update (before the disk was full) worked through the firewall without that change. Then I looked a little bit into the YaST modules, and found a setting in /usr/share/YaST2/modules/OnlineUpdate.ycp. There is an entry global string you_url = ""; in it. I inserted the text "ftp:://ftp.suse.com/pub/suse" and tried again. That helped a little, as the first initialization step was working now. Actually, YasT2 seems to download some URL if none is given in that variable. But now, when I start the update, I got other similar error messages. However, now I found the line "[mediaaccess] MediaWget.cc(getFile):125 wget error: connection failed" in the y2log file. Seems like wget has some problem. Again, the firewall did not show any packet going out. I also checked DNS and network setups. No clue. And, as I said, I can download packages manually using ftp. This is where I'm stuck. I suspect that during the failed update process, the system has been left in an incomplete state, and there's no way getting out with YaST2. Does anyone have an idea how I can get out of this? I'm currently thinking of removing the YaST packages via rpm, and restore the original ones from the CDs. But before doing that, and maybe causing other trouble, I thought I should ask for help here. I didn't use YOU before. A collegue told me (later) that he had bad experience with it. Is YOU known to have such problems? Should I better do the updates manually? BTW, the rest of the system seems to run fine. Thanks in advance, Axel ************************************************************** Axel Wagner raytest Isotopenmessgeraete GmbH Benzstr. 4 D-75334 Straubenhardt Tel: (07082) 9255 16 Fax: (07082) 20813 Email: wagner(a)raytest.de

1 0

YAST2 Online Update (When is a subscription required?)
by JazzPup 23 Aug '04

23 Aug '04

Hi I recently received and installed the Linux Technical Resource Kit from Novell. I installed SLES 8 (/w United Linux 1.0) My question is, am I able to take advantage of SuSe's YAST2 Online Update services to install patches, software, or system upgrades? I have read what I could find and I believe that I am not able to update SLES 8 components because I am using an evaluation version of the software, but what about United Linux 1.0 or the SuSe client software that is not part of SLES. Can these be updated online or do I have to purchase some kind of support license? I want to install Oracle 10g and want to make sure my system is up-to-date. Thanks and take care, JazzPup

2 1

SLES 9: Errors in the XML DTD
by Hans Kamm 23 Aug '04

23 Aug '04

Hello, I' ve just tested SLES 9 and autoyast, I' ve created a XML file with the yast tool from scratch. Bugs 1. Tools -> Create Reference Profile seems not to work, e.g. no software collection will be created. 2. Tools -> Check Validity of Profile: I don't know the error in the DTD: /tmp/YaST2-02661-GARgtP/valid.xml:70: element security: validity error : No declaration for element security </security> The following errors occur as the bootloader.dtd is incorrect, the mentioned elements 'activate' and 'repl_mbr' are missing: /tmp/YaST2-02661-GARgtP/valid.xml:91: element activate: validity error : No declaration for attribute type of element activate <activate config:type="boolean">false</activate> ^ /tmp/YaST2-02661-GARgtP/valid.xml:91: element activate: validity error : No declaration for element activate <activate config:type="boolean">false</activate> ^ /tmp/YaST2-02661-GARgtP/valid.xml:95: element repl_mbr: validity error : No declaration for attribute type of element repl_mbr <repl_mbr config:type="boolean">false</repl_mbr> ^ /tmp/YaST2-02661-GARgtP/valid.xml:95: element repl_mbr: validity error : No declaration for element repl_mbr <repl_mbr config:type="boolean">false</repl_mbr> ^ /tmp/YaST2-02661-GARgtP/valid.xml:96: element bootloader: validity error : Element bootloader content does not follow the DTD, expecting (global? , initrd_modules? , loader_device? , loader_type , location , sections?), got (activate loader_device loader_type location repl_mbr ) </bootloader> ^ Have anybody tested this piece of software before releasing it? I'm afraid of installing a system with autoyast, is it possible? _________________________________________________________________ Schluß mit Spam! http://www.msn.de/antispam/prevention/junkmailfilter Wir helfen Ihnen, unerwünschte E-Mails zu reduzieren.

2 1

A profile for this machine could not be found
by Joseph V Moss 21 Aug '04

21 Aug '04

I'm experiencing a problem similar to what Luca Lafranchi reported in his message to the list on 22-Apr-2004 where autoyast claims it can't retrieve the needed control file. In my case, I am using SLES9 to retrieve the file via ftp. The log shows: 2004-08-20 16:04:01 <1> linux(875) [YCP] AutoinstConfig.ycp:214 urltok = $["frag ment":"", "host":"10.7.51.226", "pass":"", "path":"/control-files/test.xml", "po rt":"", "query":"", "scheme":"ftp", "user":""] 2004-08-20 16:04:01 <1> linux(875) [YCP] ProfileLocation.ycp:46 Path to remote c ontrol file: /control-files/test.xml 2004-08-20 16:04:01 <1> linux(875) [YCP] ProfileLocation.ycp:57 File=test.xml 2004-08-20 16:04:01 <1> linux(875) [agent-curl] CurlAgent.cc(Execute):209 Data: 2004-08-20 16:04:01 <1> linux(875) [agent-curl] CurlAgent.cc(Execute):210 Output : /tmp/YaST2-00875-tHiu4i/autoinst.xml 2004-08-20 16:04:01 <3> linux(875) [YCP] autoinstall/io.ycp:83 Can't find URL: f tp://10.7.51.226/control-files/test.xml so it claims that it can't find the file, but the log on the ftp server shows that the file was downloaded and in fact the output file .../autoinst.xml has the correct contents. So why is it claiming that it can't find it?

1 0

Manual autoinstall...?
by Miro 20 Aug '04

20 Aug '04

Hi. I am trying to figure out a way to prompt for everything (manual package sel , rootpass, users..etc.). during a vnc autoinstall, except for the network configuration.! aka. install everything manually, but skip the network config (preconfigure= d). Does anybody know a solution to this..? Thanks in advance. Miro.

1 0

post install script oddity
by Dax Kelson 19 Aug '04

19 Aug '04

On SLES9 I have a AutoYaST post install script that runs: useradd -m -p '$1$J1n.X/QK$hj1vaqARqf.O/RWisMGRn1' visitor (this is a test account, on isolated, non-production test systems that are reinstalled daily with a variety of operating systems) The home directory /home/vistor is created and populated, BUT the very odd thing is there is no entry in the /etc/passwd file. All the files in the home directory have their ownership set to UID 1000. No error messages show up in the /var/adm/autoinstall/* log files. Things work fine on SUSE Linux 9.1 and SLES8. Suggestions welcome. Dax Kelson

1 0