The autoyast requires the actual filename, not just the directory. e.g. autoyast=nfs://192.168.3.230/install/configProfiles/profile.xml It helped me a lot to monitor /var/log/messages of my dhcp server while booting the client. On Friday 03 February 2006 09:59, Richard Hobbs wrote:
Hello,
Thank you once again for your reply... I am once again, a step further :-)
However, I am still having the same problem, although now I think I know why.
Current Situation:
I have one NFS export, which is exported read-only. This contains two dirs - "suse10_64" and "configProfiles".
The relevant line in "/tftpboot/pxelinux.cfg/default" says:
append initrd=initrd splash=silent showopts insmod=e1000 netdevice=eth0 install=nfs://192.168.3.230/install/suse10_64/ autoyast=nfs://192.168.3.230/install/configProfiles/
But I am still getting the "Profile not found error". The MAC address of the machine is 00:14:22:b0:c6:66 and it's DHCP IP address and the IP address specified in the XML file are both 192.168.3.4. I have therefore tried calling the xml file "001422b0c666", "001422B0C666" and even "C0A80304" (the hex IP address), but I still get the "Profile not found" error.
I therefore decided to type "yast2 autoyast", then open the xml file, and then validate it using the option in the "Tools" menu. The following happened...
First of all, I click "File" | "Open" and opened the XML file I had generated. The following got printed to either stdout or stderr:
============================================================ Pseudo-hashes are deprecated at /usr/share/YaST2/modules/SambaServer.pm line 284 (#1) (D deprecated) Pseudo-hashes were deprecated in Perl 5.8.0 and they will be removed in Perl 5.10.0, see perl58delta for more details. You can continue to use the fields pragma. ============================================================
I then clicked "Tools" | "Check Validity of Profile" and after it had done it's checking, the following got reported back to me:
============================================================ ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1067: element write_list: validity error : No declaration for element write_list <write_list>@ntadmin root</write_list> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1068: element parameters: validity error : No declaration for element parameters </parameters> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1069: element listentry: validity error : No declaration for element listentry </listentry> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1074: element inherit_acls: validity error
: No declaration for element inherit_acls
<inherit_acls>Yes</inherit_acls> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1075: element path: validity error : No declaration for element path <path>/home/groups</path> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1076: element read_only: validity error : No declaration for element read_only <read_only>No</read_only> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1077: element parameters: validity error : No declaration for element parameters </parameters> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1078: element listentry: validity error : No declaration for element listentry </listentry> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1083: element inherit_acls: validity error
: No declaration for element inherit_acls
<inherit_acls>Yes</inherit_acls> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1084: element path: validity error : No declaration for element path <path>/home</path> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1085: element read_only: validity error : No declaration for element read_only <read_only>No</read_only> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1086: element veto_files: validity error : No declaration for element veto_files <veto_files>/aquota.user/groups/shares/</veto_files> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1087: element parameters: validity error : No declaration for element parameters </parameters> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1088: element listentry: validity error : No declaration for element listentry </listentry> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1092: element browseable: validity error : No declaration for element browseable <browseable>No</browseable> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1094: element inherit_acls: validity error
: No declaration for element inherit_acls
<inherit_acls>Yes</inherit_acls> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1095: element read_only: validity error : No declaration for element read_only <read_only>No</read_only> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1096: element valid_users: validity error
: No declaration for element valid_users
<valid_users>%S</valid_users> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1097: element parameters: validity error : No declaration for element parameters </parameters> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1098: element listentry: validity error : No declaration for element listentry </listentry> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1103: element create_mask: validity error
: No declaration for element create_mask
<create_mask>0600</create_mask> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1104: element directory_mask: validity error : No declaration for element directory_mask <directory_mask>0700</directory_mask> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1105: element path: validity error : No declaration for element path <path>%H</path> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1106: element read_only: validity error : No declaration for element read_only <read_only>No</read_only> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1107: element store_dos_attributes: validity error : No declaration for element store_dos_attributes <store_dos_attributes>Yes</store_dos_attributes> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1108: element parameters: validity error : No declaration for element parameters </parameters> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1109: element listentry: validity error : No declaration for element listentry </listentry> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1110: element config: validity error : Element config was declared #PCDATA but contains non text nodes </config> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1113: element samba-server: validity error
: Element samba-server content does not follow the DTD, expecting (client ,
global , role , service , shares , trusteddomains , version), got (config service version ) </samba-server> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1200: element groups: validity error : Element groups content does not follow the DTD, expecting (group)+, got (CDATA) <groups>video,dialout</groups> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1200: element groups: validity error : Element groups does not carry attribute config:type <groups>video,dialout</groups> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1205: element user_defaults: validity error : Element user_defaults content does not follow the DTD, expecting (expire? , group? , home? , inactive? , shell? , skel?), got (group groups home inactive shell skel ) </user_defaults> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1454: element profile: validity error : Element profile content does not follow the DTD, expecting (files | firewall
| groups | inetd | ldap | mail | networking | nfs | nfs_server | nis |
nisplus | nis_server | ntp-client | printer | proxy | runlevel | samba-client | samba-server | scripts | security | sound | sysconfig | tftp-server | user_defaults | users | x11 | online_update | bootloader | classes | general | lvm | partitioning | partitioning_advanced | raid | report | software)*, got (bootloader firewall general groups inetd kerberos ldap mail networking nfs_server nis nis_server ntp-client partitioning power-management printer report runlevel samba-client samba-server security software sound user_defaults users x11 ) </profile> ^ ============================================================
I have a feeling there was more to display, but it had scrolled beyond the top of the text area.
When generating the XML file, you have the option of selecting various "Additional Resources". I tried selecting all of them, even the ones that weren't installed or configured, but it prompted me to install dhcp-server and bind, so after unselecting "DHCP Server" and "DNS Server", I tried again and it generated an XML file without displaying any errors.
However, the machine does not have a lot of these things on it (or at least they have never been configured), like a NIS Server, Samba Server, NFS Server, LDAP client, Kerberos client, and Firewall.
Should I unselect these options if they are not installed or configured, or will manual intervention be required during each install onto the new machines?
I figured that even if they're not configured, by including them in the profile, it would tell autoyast that they were not configured, so don't prompt the user, but my assumptions may be wrong. I basically just want to clone the system! Lol
Thanks again, your help is appreciated :-)
Richard.
-- Richard Hobbs (Systems Administrator) Toshiba Research Europe Ltd. - Speech Technology Group Web: http://www.toshiba-europe.com/research/ Normal Email: richard.hobbs@crl.toshiba.co.uk Mobile Email: mobile@mongeese.co.uk Tel: +44 1223 376964 Mobile: +44 7811 803377
-----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: 02 February 2006 18:02 To: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] Help with installing multiple machines over network
On Thursday 02 February 2006 18:41, Richard Hobbs wrote:
I have also added an <initialize> tag within each <drive>
tag, just below
the <device> tag in order to remove the partition table on each disk before starting, so I hope I have done this correctly as well:
============================================================ <drive> <device>/dev/sda</device> <initialize config:"boolean">true</initialize>
this is correct.
Finally, just after it's probed the mouse and done a few
other things, I
get a dialog box appearing which says:
System Profile Location: /existing/location/of/file.xml
I then have the option ot typing in a different XML file,
but why is it
prompting me for a different file?
that can happen in two cases. Either the profile can't be found where you have pointed to with the autoyast=... option, or the profile has a XML syntax error. Since you created the profile with the autoyast UI, a syntax error is not very likely as long as you did not change anything with a texteditor. So make sure that the profile really is where autoyast=... points to and that the machine can read it. On SUSE Linux 10.1 the error message in that case is a lot better but of course that does not help you at the moment :)
I have a feeling there's a MAC address in the xml file somewhere, so do I just need to replace the MAC address of the
original machine with
the MAC address of the new machine I'm trying to build?
maybe it's a good idea to replace the MAC but I'm sure that's not the problem here.
Also, I have read somewhere that I can use a configuration server to store xml files for each machine I have, and given the quantity of machines, this would be the ideal approach for me because each one obviously needs a different IP address and hostname, so I
can't use the
same XML file for all the machines.
why don't you use DHCP in your network? If you do "autoyast=nfs://..../" without providing the profile name, then autoyast tries to fetch a profile with the name of the MAC address of the machine like "0007E9F2FCEB".
-- ciao, Uwe Gansert
Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
_____________________________________________________________________ This e-mail has been scanned for viruses by MCI's Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
_____________________________________________________________________ This e-mail has been scanned for viruses by MCI's Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com