December 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

[opensuse-autoinstall] Init-scripts and nfs location
by Andrew Laden 14 Dec '06

14 Dec '06

Using autoyast on Sles 9 SP3. pxebooting using dhcp. Installing over NFS, Autoyast file served up via NFS, so I know that all works fine. Autoinstall all works fine. I get a fully installed ready to go system. So now I am trying to use/configure some init scripts. I have two of them. One I have placed the source in the xml, and the other via NFS. <scripts> <init-scripts config:type="list"> <script> <filename>init-zeus_bootstrap</filename> <interpreter>shell</interpreter> <location>nfs://192.168.1.1/vol/prod_LinuxInstall_grn_x/zeus/zeus_bootst rap</location> </script> <script> <filename>init-online-update.sh</filename> <interpreter>shell</interpreter> <source><![CDATA[ /usr/bin/online_update -s -u http://lx4-adm.grn.tudor.com/YOU -V > /var/tmp/online-update.out 2> /var/tmp/online-update.err ]]></source> </script> </init-scripts> </scripts> The one with source works fine. The other doesn't seem to work. So 1: Is the location paramter supported on Sles 9.3 for init scripts. 2: Is this section parsed and the files created at a time when the network is up, so that NFS is available? 3: Are there some log files that will help me. Since the script never runs, there is nothing in /var/adm/autoinstall. It looks like the script never gets copied from NFS and placed in there. Thanks -Andrew -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 3

RE: [opensuse-autoinstall] Network and file systems availability during user script levels
by Andrew Laden 13 Dec '06

13 Dec '06

To people who have gotten <location> references to work, can you email me 1: The relevent (scripts) portion of your autoyast.xml 2: A pxeboot config file. I am curious if tweaking the dhcp settings may help. I tried a boot with DHCP=0 and useDHCP=0, passing in HostIP, IPAddr, netmask, gateway and nameserver. Not only did the <location> script still not get installed, but the installation bombed out after reboot, as for some reason, post install it tries to install libcap from the nfs source. Since this works with DHCP, it seems that there must be some network up at some point after the reboot before autoyast is finished. Which goes back to my original question. At what script point are both the network and the filesystem available. (and where) > -----Original Message----- > From: Andrew Laden [mailto:Andrew.Laden@tudor.com] > Sent: Wednesday, December 13, 2006 12:46 PM > To: Jorge Alvarado; Rich; opensuse-autoinstall(a)opensuse.org > Subject: RE: [SPAM] - RE: [opensuse-autoinstall] Network and > file systems availability during user script levels - Email > found in subject > > Makes 2 of us. > > 2006-12-12 17:15:06 <3> linux(3497) [agent-curl] > CurlAgent.cc(Get):70 curl told us 7 > > Were you using static IP's or DHCP? > > > -----Original Message----- > > From: Jorge Alvarado [mailto:jalvarado@pervasive.com] > > Sent: Wednesday, December 13, 2006 12:09 PM > > To: Andrew Laden; Rich; opensuse-autoinstall(a)opensuse.org > > Subject: RE: [SPAM] - RE: [opensuse-autoinstall] Network and file > > systems availability during user script levels - Email found in > > subject > > > > yep, I couldn't get <location> to work for a post-install script. > > y2log had a curl rc 7 failure when retrieving the script. I > tried ftp > > and http, no luck. > > > > so, I would also be interested in any debug info...I may > revisit this > > later. > > > > -----Original Message----- > > From: Andrew Laden [mailto:Andrew.Laden@tudor.com] > > Sent: Wednesday, December 13, 2006 11:02 AM > > To: Rich; opensuse-autoinstall(a)opensuse.org > > Subject: [SPAM] - RE: [opensuse-autoinstall] Network and > file systems > > availability during user script levels - Email found in subject > > > > > > > Andrew Laden wrote: > > > > Heya all > > > > > > > > Since I cant seem to get the <location> option to work, > > and since in > > > > > > i can get <location> working just fine, using http://<ip>/path it > > > kinda "just worked" for me :) > > > > At least one other person responded that they didn't work. > > Maybe it is isolated to a particular network card or config? > > I don't know. These two errors lead me to think it's a > > network issue. (I did also try http, with the same lack of success.) > > > > 2006-12-12 14:54:10 <3> linux(3497) [bash] > > ShellCommand.cc(shellcommand):73 mount server reported tcp > > not available, falling back to udp > > 2006-12-12 14:54:10 <3> linux(3497) [bash] > > ShellCommand.cc(shellcommand):73 mount: RPC: Remote system > > error - Network is unreachable > > > > If there is any other debugging I can do, please let me know. > > > > > > > > > sles10, init scripts changed to run before the network is > > up. (which > > > > > > hmm. not according to > > > http://www.suse.com/~ug/autoyast_doc/createprofile.scripts.htm > > > l (and my > > > setup) : > > > > > > "Starting from SLES9, network is not available during > > > post-installation script execution. To access the > network, network > > > device has to be configured in the script. > > > > > > It is possible to execute the post scripts in an earlier > > phase while > > > the installation network is still up and before AutoYaST > configures > > > the system. To run network enabled post scripts, the > > boolean property > > > network_needed has to be set to true." > > > > > > this is about postinstall, not init scripts - which, in turn : > > > > > > "These scripts are executed during the initial boot process > > and after > > > YaST2 has finished. The final scripts are executed using > a special > > > init.d script which is executed only once. The final scripts are > > > executed toward the end of the boot process and after > > network has been > > > intialized." > > > > > > i have an init script which nicely downloads required > files, and it > > > works fine. > > > > Check the release notes for Changes between sles10 and sp1 > > http://www.suse.com/~ug/autoyast_changes_SLES10SP1.html > > [bug] init-script does not require network now > > > > -- > > To unsubscribe, e-mail: > opensuse-autoinstall+unsubscribe(a)opensuse.org > > For additional commands, e-mail: > > opensuse-autoinstall+help(a)opensuse.org > > > > > -- > To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org > For additional commands, e-mail: > opensuse-autoinstall+help(a)opensuse.org > > -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] Network and file systems availability during user script levels
by Andrew Laden 13 Dec '06

13 Dec '06

Heya all Since I cant seem to get the <location> option to work, and since in sles10, init scripts changed to run before the network is up. (which defeats the purpose I needed them for anyway) My current plan is to write a small script that I can place in the xml that will, at the appropriate time, mount the nfs share, copy the files into place, and then unmount. My question is what is the right phase to run in? The 6 possible phase are: Pre-install Chroot (pre chroot) Chroot (post chroot) Post install (network available) Post install (no network) Init Pre-install work work as the File system isnt there. Post install (no network) work work as I have no network. Init wont work, in sles 10 I wont have network. (there is another issue in that I want the script I am downloading to run in an rc level, so placing it duing init time would be too late anyway.) Is the network available during the chroot phases? My best option would be during the chroot (post chroot) phase, as I can drop the file in and then do a chkconfig -a to get them added in to the boot sequence. If that doesn't work, then where is the file system located in the post-install (network available) phase, so I can drop the files in myself. Thanks -Andrew -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

RE: [SPAM] - RE: [opensuse-autoinstall] Network and file systems availability during user script levels - Email found in subject
by Andrew Laden 13 Dec '06

13 Dec '06

Makes 2 of us. 2006-12-12 17:15:06 <3> linux(3497) [agent-curl] CurlAgent.cc(Get):70 curl told us 7 Were you using static IP's or DHCP? > -----Original Message----- > From: Jorge Alvarado [mailto:jalvarado@pervasive.com] > Sent: Wednesday, December 13, 2006 12:09 PM > To: Andrew Laden; Rich; opensuse-autoinstall(a)opensuse.org > Subject: RE: [SPAM] - RE: [opensuse-autoinstall] Network and > file systems availability during user script levels - Email > found in subject > > yep, I couldn't get <location> to work for a post-install > script. y2log had a curl rc 7 failure when retrieving the > script. I tried ftp and http, no luck. > > so, I would also be interested in any debug info...I may > revisit this later. > > -----Original Message----- > From: Andrew Laden [mailto:Andrew.Laden@tudor.com] > Sent: Wednesday, December 13, 2006 11:02 AM > To: Rich; opensuse-autoinstall(a)opensuse.org > Subject: [SPAM] - RE: [opensuse-autoinstall] Network and file > systems availability during user script levels - Email found > in subject > > > > Andrew Laden wrote: > > > Heya all > > > > > > Since I cant seem to get the <location> option to work, > and since in > > > > i can get <location> working just fine, using http://<ip>/path it > > kinda "just worked" for me :) > > At least one other person responded that they didn't work. > Maybe it is isolated to a particular network card or config? > I don't know. These two errors lead me to think it's a > network issue. (I did also try http, with the same lack of success.) > > 2006-12-12 14:54:10 <3> linux(3497) [bash] > ShellCommand.cc(shellcommand):73 mount server reported tcp > not available, falling back to udp > 2006-12-12 14:54:10 <3> linux(3497) [bash] > ShellCommand.cc(shellcommand):73 mount: RPC: Remote system > error - Network is unreachable > > If there is any other debugging I can do, please let me know. > > > > > > sles10, init scripts changed to run before the network is > up. (which > > > > hmm. not according to > > http://www.suse.com/~ug/autoyast_doc/createprofile.scripts.htm > > l (and my > > setup) : > > > > "Starting from SLES9, network is not available during > > post-installation script execution. To access the network, network > > device has to be configured in the script. > > > > It is possible to execute the post scripts in an earlier > phase while > > the installation network is still up and before AutoYaST configures > > the system. To run network enabled post scripts, the > boolean property > > network_needed has to be set to true." > > > > this is about postinstall, not init scripts - which, in turn : > > > > "These scripts are executed during the initial boot process > and after > > YaST2 has finished. The final scripts are executed using a special > > init.d script which is executed only once. The final scripts are > > executed toward the end of the boot process and after > network has been > > intialized." > > > > i have an init script which nicely downloads required files, and it > > works fine. > > Check the release notes for Changes between sles10 and sp1 > http://www.suse.com/~ug/autoyast_changes_SLES10SP1.html > [bug] init-script does not require network now > > -- > To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org > For additional commands, e-mail: > opensuse-autoinstall+help(a)opensuse.org > > -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

RE: [opensuse-autoinstall] Network and file systems availability during user script levels
by Andrew Laden 13 Dec '06

13 Dec '06

> Andrew Laden wrote: > > Heya all > > > > Since I cant seem to get the <location> option to work, and since in > > i can get <location> working just fine, using > http://<ip>/path it kinda "just worked" for me :) At least one other person responded that they didn't work. Maybe it is isolated to a particular network card or config? I don't know. These two errors lead me to think it's a network issue. (I did also try http, with the same lack of success.) 2006-12-12 14:54:10 <3> linux(3497) [bash] ShellCommand.cc(shellcommand):73 mount server reported tcp not available, falling back to udp 2006-12-12 14:54:10 <3> linux(3497) [bash] ShellCommand.cc(shellcommand):73 mount: RPC: Remote system error - Network is unreachable If there is any other debugging I can do, please let me know. > > > sles10, init scripts changed to run before the network is up. (which > > hmm. not according to > http://www.suse.com/~ug/autoyast_doc/createprofile.scripts.htm > l (and my > setup) : > > "Starting from SLES9, network is not available during > post-installation script execution. To access the network, > network device has to be configured in the script. > > It is possible to execute the post scripts in an earlier > phase while the installation network is still up and before > AutoYaST configures the system. To run network enabled post > scripts, the boolean property network_needed has to be set to true." > > this is about postinstall, not init scripts - which, in turn : > > "These scripts are executed during the initial boot process and after > YaST2 has finished. The final scripts are executed using a > special init.d script which is executed only once. The final > scripts are executed toward the end of the boot process and > after network has been intialized." > > i have an init script which nicely downloads required files, > and it works fine. Check the release notes for Changes between sles10 and sp1 http://www.suse.com/~ug/autoyast_changes_SLES10SP1.html [bug] init-script does not require network now -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

RE: [SPAM] - RE: [opensuse-autoinstall] Network and file systems availability during user script levels - Email found in subject
by Jorge Alvarado 13 Dec '06

13 Dec '06

yep, I couldn't get <location> to work for a post-install script. y2log had a curl rc 7 failure when retrieving the script. I tried ftp and http, no luck. so, I would also be interested in any debug info...I may revisit this later. -----Original Message----- From: Andrew Laden [mailto:Andrew.Laden@tudor.com] Sent: Wednesday, December 13, 2006 11:02 AM To: Rich; opensuse-autoinstall(a)opensuse.org Subject: [SPAM] - RE: [opensuse-autoinstall] Network and file systems availability during user script levels - Email found in subject > Andrew Laden wrote: > > Heya all > > > > Since I cant seem to get the <location> option to work, and since in > > i can get <location> working just fine, using > http://<ip>/path it kinda "just worked" for me :) At least one other person responded that they didn't work. Maybe it is isolated to a particular network card or config? I don't know. These two errors lead me to think it's a network issue. (I did also try http, with the same lack of success.) 2006-12-12 14:54:10 <3> linux(3497) [bash] ShellCommand.cc(shellcommand):73 mount server reported tcp not available, falling back to udp 2006-12-12 14:54:10 <3> linux(3497) [bash] ShellCommand.cc(shellcommand):73 mount: RPC: Remote system error - Network is unreachable If there is any other debugging I can do, please let me know. > > > sles10, init scripts changed to run before the network is up. (which > > hmm. not according to > http://www.suse.com/~ug/autoyast_doc/createprofile.scripts.htm > l (and my > setup) : > > "Starting from SLES9, network is not available during > post-installation script execution. To access the network, > network device has to be configured in the script. > > It is possible to execute the post scripts in an earlier > phase while the installation network is still up and before > AutoYaST configures the system. To run network enabled post > scripts, the boolean property network_needed has to be set to true." > > this is about postinstall, not init scripts - which, in turn : > > "These scripts are executed during the initial boot process and after > YaST2 has finished. The final scripts are executed using a > special init.d script which is executed only once. The final > scripts are executed toward the end of the boot process and > after network has been intialized." > > i have an init script which nicely downloads required files, > and it works fine. Check the release notes for Changes between sles10 and sp1 http://www.suse.com/~ug/autoyast_changes_SLES10SP1.html [bug] init-script does not require network now -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] autoyast with /dev/disk/by-path not working
by Hartmut Gottwald 13 Dec '06

13 Dec '06

Hello list, using /dev/disk/by-path syntax in autoyast control file does not work but the equivalent /dev/sd? devices do. Is this a known issue and a fix available? Need by-path syntax to avoid trashing other devices during autoinstall in case one of the system disks failed and is missing. <drive>  <device>/dev/sdb</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> Thanks, Hartmut -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 3

RE: [opensuse-autoinstall] Init-scripts and nfs location
by Andrew Laden 13 Dec '06

13 Dec '06

> On Tuesday 12 December 2006 21:25, Andrew Laden wrote: > > > The one with source works fine. The other doesn't seem to work. So > > 1: Is the location paramter supported on Sles 9.3 for init scripts. > > yes > > > 2: Is this section parsed and the files created at a time when the > > network is up, so that NFS is available? > > yes, that works fine (I just tried it again to be sure) > Because you are doing a network installation, it should work > for you too. > At the moment I can not say why it does not work for you. > It works fine here. > Any ideas as to what else I can do to debug? Is there a way to pause the autoyast setup at the point when it should be fetching the files so I can see why it cant detect a network? I sent out the log in a previous email. Thanks -Andrew -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] [SLES 10] error using autoyast=device://cciss/c0d0p1/autoinst.xml (nested devices)
by Sylvain Le Courtois (alplog) 13 Dec '06

13 Dec '06

Hello All, I send this message to give information about a bug I encountered using autoyast SLES 10 and Profilant HP servers. The HP Smart array raid controllers creates "nested" devices in /dev : cciss/c0d0p1 is the first partition of the first logical drive of the first controller The use of : autoyast=device://cciss/c0d0p1/autoinst.xml failed (profile file not found error in Yast) After some time consuming investigations, I found these lines in the y2log file : 006-07-17 17:18:06 <1> 192.168.0.43(3346) [YCP] autoinstall/io.ycp:227 nested device found 2006-07-17 17:18:06 <1> 192.168.0.43(3346) [YCP] autoinstall/io.ycp:232 Host=cciss/ Path=c0d0p1/autoinst/autoinst.xml 2006-07-17 17:18:06 <1> 192.168.0.43(3346) [YCP] autoinstall/io.ycp:227 nested device found 2006-07-17 17:18:06 <1> 192.168.0.43(3346) [YCP] autoinstall/io.ycp:232 Host=cciss//c0d0p1 Path=autoinst/autoinst.xml 2006-07-17 17:18:06 <1> 192.168.0.43(3346) [agent-system] SystemAgent.cc(Read):544 Can't access directory '/dev/cciss//c0d0p1': Not a directory' 2006-07-17 17:18:06 <3> 192.168.0.43(3346) [bash] ShellCommand.cc(shellcommand):78 /bin/cp: cannot stat `/tmp/YaST2-03346-Op2jd3/tmp_mountautoinst/ autoinst.xml': No such file or directory 2006-07-17 17:18:06 <3> 192.168.0.43(3346) [YCP] autoinstall/io.ycp:243 file /tmp/YaST2-03346-Op2jd3/tmp_mountautoinst/autoinst.xml can't be found The guilty lines are located in the Get function of the io.ycp module. It seems that there is some lines of code to take care of "nested devices" but it does not work. /* sometimes we have devices like /dev/cciss/c1d0p5 those "nested" devices will be catched here as long as we find a directory where we expect a device, we cut down the Path and enhance the Host (device name) */ while( SCR::Read( .target.dir, "/dev/"+Host ) != nil ) { y2milestone("nested device found"); list<string> l = splitstring( Path, "/" ); Host = Host + "/" + l[0]:""; l = remove(l,0); Path = mergestring(l,"/"); y2milestone("Host=%1 Path=%2",Host,Path); } // catching nested devices done autoyast=device://cciss/c0d0p1///autoinst.xml works as a workaround. Hoping that this information can be useful to other happy SuSE administrators. Regards, -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

RE: [SPAM] - [opensuse-autoinstall] Init-scripts and nfs location - Email found in subject
by Andrew Laden 12 Dec '06

12 Dec '06

Not a whole lotta help... 2006-12-12 14:54:10 <1> linux(3497) [YCP] AutoinstScripts.ycp:406 Writing init script into /var/adm/autoinstall/init.d/init-zeus_bootstrap 2006-12-12 14:54:10 <3> linux(3497) [bash] ShellCommand.cc(shellcommand):73 mount server reported tcp not available, falling back to udp 2006-12-12 14:54:10 <3> linux(3497) [bash] ShellCommand.cc(shellcommand):73 mount: RPC: Remote system error - Network is unreachable 2006-12-12 14:54:10 <2> linux(3497) [YCP] autoinstall/io.ycp:146 Mount failed 2006-12-12 14:54:10 <3> linux(3497) [YCP] AutoinstScripts.ycp:412 script nfs://10.2.42.65/vol/prod_LinuxInstall_grn_x/zeus/zeus_bootstrap could not be retrieved Except it seems that the network is not available. Which make me wonder why the option is there..... > -----Original Message----- > From: Jorge Alvarado [mailto:jalvarado@pervasive.com] > Sent: Tuesday, December 12, 2006 3:35 PM > To: Andrew Laden; opensuse-autoinstall(a)opensuse.org > Subject: RE: [SPAM] - [opensuse-autoinstall] Init-scripts and > nfs location - Email found in subject > > look at /var/log/YaST2/y2log. > I also could not get <location> to work. first I thought is > was my ftp setup, but curl continued to return a 7 (failed to > connect to host). The y2log should give some clue. I was > using an http location reference, tried ftp - no go. Take > the same reference after the reboot and curl works. Not > clear why if fails during auto install. > > I went with the <source> reference...had to move on. > > -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0