January 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

SLES9 network install
by Ness, Todd 07 Jan '05

07 Jan '05

Well, I found out a little more about my problem, I was actually trying to install JDS3 which is SLES9 based, they have broken the http install I did the exact same setup steps for http install with my SLES9 disks and it works fine. Thanks for all the suggestions. Todd

1 0

Problem using HTTP Installation Source with port different than 80
by Meyers, Holger 07 Jan '05

07 Jan '05

Hi, I am trying to install SLES 9 or SuSE Linux 9.2 from an installation source with a port different than 80. With both products the installation fails with no packages availible. Both installations work if I change the port back to 80. If I use port 2048 the root images is loaded but after yast starts it ignores port 2048 an reverts to port 80. Do I need an patch or is there any way to specify the installation source in the XML File? Holger Diese Nachricht ist vertraulich. Sie ist ausschliesslich fuer den im Adressfeld ausgewiesenen Adressaten bestimmt. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir um eine kurze Nachricht. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Da wir nicht die Echtheit oder Vollstaendigkeit der in dieser Nachricht enthaltenen Informationen garantieren koennen, schliessen wir die rechtliche Verbindlichkeit der vorstehenden Erklaerungen und Aeusserungen aus. Wir verweisen in diesem Zusammenhang auch auf die fuer die Bank geltenden Regelungen ueber die Verbindlichkeit von Willenserklaerungen mit verpflichtendem Inhalt, die in den bankueblichen Unterschriftenverzeichnissen bekannt gemacht werden. This message is confidential and may be privileged. It is intended solely for the named addressee. If you are not the intended recipient please inform us. Any unauthorised dissemination, distribution or copying hereof is prohibited. As we cannot guarantee the genuineness or completeness of the information contained in this message, the statements set forth above are not legally binding. In connection therewith, we also refer to the governing regulations of the bank concerning signatory authority published in the standard bank signature lists with regard to the legally binding effect of statements made with the intent to obligate the bank.

1 0

RE: [suse-autoinstall] SLES9 network install
by Ness, Todd 06 Jan '05

06 Jan '05

The only errors are: [Thu Jan 06 15:42:19 2005] [error] [client 192.168.1.118] File does not exist: /home/www/JDS/netbld/JDS3/part.info [Thu Jan 06 15:42:19 2005] [error] [client 192.168.1.118] File does not exist: /home/www/JDS/netbld/JDS3/driverupdate [Thu Jan 06 15:43:02 2005] [error] [client 192.168.1.118] File does not exist: /home/www/JDS/netbld/JDS3/suse/setup/descr/packages.en_US [Thu Jan 06 15:43:02 2005] [error] [client 192.168.1.118] File does not exist: /home/www/JDS/netbld/JDS3/sles9-i386/CD1/suse/setup/descr/Full-Installation. sel Don't really see why that would cause a problem and in the access log you can see the selection files being found: 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/suse/setup/descr/selections HTTP/1.1" 200 363 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/suse/setup/descr/Base-System.sel HTTP/1.1" 200 3181 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/suse/setup/descr/Basis-Devel.sel HTTP/1.1" 200 2184 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/suse/setup/descr/Basis-Sound.sel HTTP/1.1" 200 1284 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/suse/setup/descr/Developer.sel HTTP/1.1" 200 3073 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/suse/setup/descr/File-Server.sel HTTP/1.1" 200 1042 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/suse/setup/descr/Gnome.sel HTTP/1.1" 200 5957 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/suse/setup/descr/HA.sel HTTP/1.1" 200 888 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/suse/setup/descr/Kde-Desktop.sel HTTP/1.1" 200 3290 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/suse/setup/descr/LAMP.sel HTTP/1.1" 200 844 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/suse/setup/descr/LSB.sel HTTP/1.1" 200 1013 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/suse/setup/descr/Linux-Tools.sel HTTP/1.1" 200 2329 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/suse/setup/descr/Mail_News-Server.sel HTTP/1.1" 200 1186 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/suse/setup/descr/Print-Server.sel HTTP/1.1" 200 1075 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/suse/setup/descr/StarOffice.sel HTTP/1.1" 200 1491 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/suse/setup/descr/StarSuite.sel HTTP/1.1" 200 1468 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/suse/setup/descr/SuSE-Documentation.sel HTTP/1.1" 200 2399 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/suse/setup/descr/Various-Tools.sel HTTP/1.1" 200 1611 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/suse/setup/descr/WBEM.sel HTTP/1.1" 200 1114 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/suse/setup/descr/X11.sel HTTP/1.1" 200 2789 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/suse/setup/descr/YaST2.sel HTTP/1.1" 200 2889 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/suse/setup/descr/analyze.sel HTTP/1.1" 200 932 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/suse/setup/descr/auth.sel HTTP/1.1" 200 1536 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/suse/setup/descr/defaultStarOffice.sel HTTP/1.1" 200 1185 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/suse/setup/descr/defaultStarSuite.sel HTTP/1.1" 200 1163 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/suse/setup/descr/dhcp_DNS-Server.sel HTTP/1.1" 200 913 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/sles9-i386/CD1/suse/setup/descr/Base-System.sel HTTP/1.1" 200 3181 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/sles9-i386/CD1/suse/setup/descr/Basis-Devel.sel HTTP/1.1" 200 2184 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/sles9-i386/CD1/suse/setup/descr/Basis-Sound.sel HTTP/1.1" 200 1284 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/sles9-i386/CD1/suse/setup/descr/File-Server.sel HTTP/1.1" 200 1042 "-" "-" 192.168.1.118 - - [06/Jan/2005:15:43:02 -0700] "GET /JDS3/sles9-i386/CD1/suse/setup/descr/Full-Installation.sel HTTP/1.1" 404 1045 "-" "-" -----Original Message----- From: Brian Corriveau [mailto:bcorriveau@cray.com] Sent: Thursday, January 06, 2005 11:35 AM To: Ness, Todd Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] SLES9 network install On your http server check these files for clues /var/log/httpd/access_log /var/log/httpd/error_log On Wednesday 05 January 2005 7:24 pm, Anas Nashif wrote: > Can you browse and acccess all the directory structure under > http://server/JDS3 using some browser? > > Ness, Todd wrote: > > OK, just started playing with the network install of SLES9. > > I have NFS network install working fine. > > But, the HTTP install that is using the same directory structure > > fails with no package selections available... > > Any clues? > > Here is the HTTP configuration: > > Alias /JDS3 /home/www/JDS/netbld/JDS3 > > > > <Directory /home/www> > > Options +FollowSymLinks +Indexes > > AllowOverride None > > Order allow,deny > > Allow from all > > > > </Directory> > > For HTTP build I use http://server/JDS3 <http://server/JDS3> When I > > do the NFS build I use /home/www/JDS/netbld/JDS3 as the directory > > and it works. > > > > Directory structure: > > migration:/home/www/JDS/netbld/JDS3> ls -la total 0 drwxr-xr-x 5 > > root root 264 2005-01-05 18:57 . > > drwxr-xr-x 4 root root 128 2004-12-20 17:12 .. > > lrwxrwxrwx 1 root root 19 2005-01-05 10:40 boot -> > > sles9-i386/CD1/boot lrwxrwxrwx 1 root root 22 2005-01-05 10:36 > > content -> sles9-i386/CD1/content lrwxrwxrwx 1 root root 26 > > 2005-01-05 10:36 control.xml -> sles9-i386/CD1/control.xml > > drwxr-xr-x 6 root root 144 2005-01-05 10:36 core9-i386 lrwxrwxrwx > > 1 root root 22 2005-01-05 10:36 media.1 -> > > sles9-i386/CD1/media.1 > > drwxr-xr-x 3 root root 72 2005-01-05 10:35 sles9-i386 lrwxrwxrwx > > 1 root root 19 2005-01-05 18:57 suse -> sles9-i386/CD1/suse > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > ^^^^ You dont need this, but it should not be the problem here. > > Anas > > > drwxr-xr-x 4 root root 152 2005-01-05 10:39 yast > > > > > > Todd Ness > > EDS - Sun JDS Model Office

1 0

SLES9 network install
by Ness, Todd 06 Jan '05

06 Jan '05

OK, just started playing with the network install of SLES9. I have NFS network install working fine. But, the HTTP install that is using the same directory structure fails with no package selections available... Any clues? Here is the HTTP configuration: Alias /JDS3 /home/www/JDS/netbld/JDS3 <Directory /home/www> Options +FollowSymLinks +Indexes AllowOverride None Order allow,deny Allow from all </Directory> For HTTP build I use http://server/JDS3 <http://server/JDS3> When I do the NFS build I use /home/www/JDS/netbld/JDS3 as the directory and it works. Directory structure: migration:/home/www/JDS/netbld/JDS3> ls -la total 0 drwxr-xr-x 5 root root 264 2005-01-05 18:57 . drwxr-xr-x 4 root root 128 2004-12-20 17:12 .. lrwxrwxrwx 1 root root 19 2005-01-05 10:40 boot -> sles9-i386/CD1/boot lrwxrwxrwx 1 root root 22 2005-01-05 10:36 content -> sles9-i386/CD1/content lrwxrwxrwx 1 root root 26 2005-01-05 10:36 control.xml -> sles9-i386/CD1/control.xml drwxr-xr-x 6 root root 144 2005-01-05 10:36 core9-i386 lrwxrwxrwx 1 root root 22 2005-01-05 10:36 media.1 -> sles9-i386/CD1/media.1 drwxr-xr-x 3 root root 72 2005-01-05 10:35 sles9-i386 lrwxrwxrwx 1 root root 19 2005-01-05 18:57 suse -> sles9-i386/CD1/suse drwxr-xr-x 4 root root 152 2005-01-05 10:39 yast Todd Ness EDS - Sun JDS Model Office

4 3

RE: [suse-autoinstall] SLES9 network install
by Ness, Todd 06 Jan '05

06 Jan '05

Yes, that works as expected, that is why there is a suse directory in the JDS3 directory as well, I found file not found messages for /suse/setup/descr/packages still did not help. -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Wednesday, January 05, 2005 8:25 PM To: Ness, Todd Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] SLES9 network install Can you browse and acccess all the directory structure under http://server/JDS3 using some browser? Ness, Todd wrote: > OK, just started playing with the network install of SLES9. > I have NFS network install working fine. > But, the HTTP install that is using the same directory structure fails > with no package selections available... > Any clues? > Here is the HTTP configuration: > Alias /JDS3 /home/www/JDS/netbld/JDS3 > > <Directory /home/www> > Options +FollowSymLinks +Indexes > AllowOverride None > Order allow,deny > Allow from all > > </Directory> > For HTTP build I use http://server/JDS3 <http://server/JDS3> When I do > the NFS build I use /home/www/JDS/netbld/JDS3 as the directory and it > works. > > Directory structure: > migration:/home/www/JDS/netbld/JDS3> ls -la total 0 drwxr-xr-x 5 root > root 264 2005-01-05 18:57 . > drwxr-xr-x 4 root root 128 2004-12-20 17:12 .. > lrwxrwxrwx 1 root root 19 2005-01-05 10:40 boot -> > sles9-i386/CD1/boot lrwxrwxrwx 1 root root 22 2005-01-05 10:36 > content -> sles9-i386/CD1/content lrwxrwxrwx 1 root root 26 > 2005-01-05 10:36 control.xml -> sles9-i386/CD1/control.xml drwxr-xr-x > 6 root root 144 2005-01-05 10:36 core9-i386 lrwxrwxrwx 1 root root > 22 2005-01-05 10:36 media.1 -> > sles9-i386/CD1/media.1 > drwxr-xr-x 3 root root 72 2005-01-05 10:35 sles9-i386 lrwxrwxrwx 1 > root root 19 2005-01-05 18:57 suse -> sles9-i386/CD1/suse ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ You dont need this, but it should not be the problem here. Anas > drwxr-xr-x 4 root root 152 2005-01-05 10:39 yast > > > Todd Ness > EDS - Sun JDS Model Office > > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

169.254.0.0/16 in SLES9
by Jon Thorson 06 Jan '05

06 Jan '05

Where is this 169.254.0.0/16 network coming from when I build a system via autoinstall? I don't have it defined in my config file, but it magically appears whenever I use autoinstall to build a SLES9 machine. I don't have this problem using autoinstall and SLES8. Also, would this phantom network have something to do with my gateway not working when the machine comes up? I have the gateway defined in the config file, but it never seems to make it over to the system at the end of the install. Here's a netstat from a freshly built machine: teeth:~ # netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 10.150.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo Here's the network portion of the config file: <networking> <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <dhcp_resolv config:type="boolean">false</dhcp_resolv> <domain>srttel.com</domain> <hostname>teeth</hostname> <nameservers config:type="list"> <nameserver>10.150.1.3</nameserver> </nameservers> <searchlist config:type="list"> <search>srttel.com</search> <search>srtnet.com</search> <search>ndak.net</search> <search>minot.com</search> </searchlist> </dns> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <broadcast>10.150.1.255</broadcast> <device>eth0</device> <ipaddr>10.150.1.111</ipaddr> <netmask>255.255.255.0</netmask> <network>10.150.1.0</network> <startmode>onboot</startmode> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>eth0</device> </module_entry> </modules> <routing config:type="list"> <route> <destination>default</destination> <device>eth0</device> <gateway>10.150.1.1</gateway> <netmask>255.255.255.0</netmask> </route> <ip_forward config:type="boolean">false</ip_forward> </routing> </networking> Is there a way to keep this network from appearing? Is this network the reason why my gateway doesn't show up? I could put something in the post-install to clean this mess up, but that seems like a hack. Surely there is an elegant way to fix this. Thanks. -j

4 4

SCR problem
by Brian Corriveau 05 Jan '05

05 Jan '05

How do I run this from the bash shell? (from clients/inst_finish.ycp) SCR::Write (.target.string, "/var/lib/YaST2/runme_at_boot", "") I want to try running this manually so I can understand why it is failing during autoinstallation. This is failing for my target, as are a couple other SCR commands. I can run the command from a chroot post-script to get the help output with: chroot /mnt /usr/lib/YaST2/servers/scr -h So the command seems to run somewhat, but for the runme_at_boot creation I get the Y2log error: 2004-12-18 02:34:13 <0> linux(3172) [liby2] Y2ProgramComponent.cc(launchExternall Program):292 Going to execute /usr/lib/YaST2/servers/scr with chroot /mnt 2004-12-18 02:34:13 <0> linux(519) [libycp] Scanner.cc(Scanner):107 Scanner settting builtinTable to 0x507d10 2004-12-18 02:34:13 <0> linux(519) [libycp] Scanner.cc(initTables):146 m_globalTT able 0x1776bb0 2004-12-18 02:34:13 <0> linux(519) [libycp] Scanner.cc(initTables):158 m_localTaable 0x52fd60 2004-12-18 02:34:13 <0> linux(519) [libycp] parser.yy(yyparse):284 ------------------------------------------- accept ------------------------------ -------------- 2004-12-18 02:34:13 <0> linux(519) [liby2] Y2ProgramComponent.cc(sendToExternal)) :377 Error writing to external program /usr/lib/YaST2/servers/scr: Couldn't sendd (`Write (.target.string, "/var/lib/YaST2/runme_at_boot", "")) (Broken pipe) 2004-12-18 02:34:13 <3> linux(519) [liby2] Y2ProgramComponent.cc(receiveFromExtee rnal):343 External program /usr/lib/YaST2/servers/scr died unexpectedly 2004-12-18 02:34:13 <3> linux(519) [Interpreter] scr:240 SCR::Write() did not reeturn a boolean So I'd like to understand what is wrong with my target's environment that this would fail. thanks, Brian

1 1

RE: [suse-autoinstall] Automatic X11 configuration
by Suffin, Charles 05 Jan '05

05 Jan '05

I use a default 800x600 configuration and instruct folks to tailor it later. I figure they're going to want to do that anyway. Besides, if you have a farm of machines, they're all likely to have different monitors anyway, don't you think guys? Nice tip on running sax2 in the postinstall script, Eric. -- Charlie -----Original Message----- From: Andreas Haupt [mailto:andreas.haupt@hmi.de] Sent: Wednesday, January 05, 2005 5:12 AM To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Automatic X11 configuration Eric Heydrick wrote: > I don't see any way in autoyast to automatically configure X11 based on > detected hardware. It would be useful if autoyast could automatically > generate an XF86Config in the way that "SaX2 -i" does. Then you > wouldn't have to provide hardware-dependent values in the profile. Yes, I'd like to have this feature as well. By now I call sax within the post installation script. HTH Andreas -- | Andreas Haupt | E-Mail: andreas.haupt(a)hmi.de | Hahn-Meitner-Institut (DN) | WWW: | Glienicker Straße 100 | Phone: +49/30/8062-2597 | 14109 Berlin | Fax: +49/30/8062-2096 -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Automatic X11 configuration
by Eric Heydrick 05 Jan '05

05 Jan '05

I don't see any way in autoyast to automatically configure X11 based on detected hardware. It would be useful if autoyast could automatically generate an XF86Config in the way that "SaX2 -i" does. Then you wouldn't have to provide hardware-dependent values in the profile. -Eric

2 1

AW: [suse-autoinstall] ERROR: no proposal
by Heinz Bleck 04 Jan '05

04 Jan '05

It works now !!! It seems that Yast2 find the autinst.xml on Floppy, but doesn´t tell it to autoyast. I solved this Problem by type in the Command line option: autoyast=/dev/fd0/autoinst.xml cu Heinz Bleck -----Ursprüngliche Nachricht----- Von: Heinz Bleck [mailto:Heinz.Bleck@morse.com] Gesendet: Montag, 3. Januar 2005 11:16 An: suse-autoinstall(a)suse.com Betreff: [suse-autoinstall] ERROR: no proposal Hi @ll, the manual installation works fine on all tested machines, but the automated installation with autoyast doesn't work. If the Computer where booted from cd the autoinst process will not started typically. After booting I have to select the language like I am doing a manual installation. The next screen shows the installation settings. All section shows correct automatically detected settings, but not the Partitioning and Software section. Partitioning * ERROR: no proposal Software * ? It seems to be a Problem with the HD, but all necessary modules are loaded (seen at the Kernel messages). Testenvironment: SUN fire 20z (double Opteron; SCSI HD; SuSE prof. 9.1, 9.2) IBM x360 (double XEON; SCSI HD; SuSE prof. 9.1, 9.2) Compaq Evo D300v (single P5; IDE HD; SuSE prof 9.1,9.2) No Name (single P5; IDE HD; SuSE prof 9.1,9.2) autoinst.xml file: created with autoyast or manually created or used older files witch where used with older SuSE Versions. I have tested 7 different files. The result is always the same: ERROR: no proposal If I am using SuSE 8.1 it works fine in all environments. Any ideas ? Thanks ;o) Heinz Bleck Service Consultant Morse GmbH Oskar Messter Straße 13 85737 Ismaning Tel. +49 - (0) 89/ 944940-264 Fax +49 - (0) 89 / 944940-275 <file:///C:\Dokumente%20und%20Einstellungen\hb\Anwendungsdaten\Microsoft\Sig natures\www.morse-techsol.de> www.morse-techsol.de **************************************************************************** *** This email and any attachments are confidential and are intended only for the addressee. If you are not the intended recipient of this email and have received it in error, please notify the sender immediately by reply email and then delete it from your system.

1 0