Greetings. I'm a relatively new user of sisuite. I've a problem I don't understand, and I'm hoping the pool of experts can help. (And please forgive me if this is a common and/or trivial problem -- I searched and searched for a solution but found nothing.)
I am attempting to use SystemImager 4.0.0 to install images on the nodes of a small Linux (Ubuntu 7.04, amd64) cluster. I have successfully created an image on the golden client, and collected this image (we'll call it 'foo_image') on the image server with no (apparent) problems. The next step, actually installing the image, is where things are malfunctioning. When a node boots, DHCP does what it should and the process of installing the correct image from the image server appears to proceed normally for quite some time: The stages of pci-automod, mke2fs, etc all go smoothly. Here are some highlights, towards the end of the process: <transcript> mke2fs -q -j /dev/sda1 || shellout tune2fs -U 52562102-1f7f-4e7e-a0bc-47e151b3fc7f /dev/sda1 tune2fs 1.3.8 (30-June-2005) [then a series of 'mount' and 'mkdir' commands, all looks normal...] Quietly installing image... [next a bunch of 'rsync' commands, again looks normal...] Detecting systemconfigurator: --- systemconfigurator - 2.2.10 [...] --- ROOTDEV UUID=52562102-1f7f-4e7e-a0bc-47e151b3fc7f under [BOOT] does not exist, please check your systemconfigurator config. Killing off running processes. write_variables <<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> BusyBox v1.1.1 [etc etc] Your autoinstall has failed. [...] </transcript> So can anyone tell me what's going on here, or better yet, how to correct it? The image's systemconfig.conf file, located at: /var/lib/systemimager/images/foo_image/etc/systeconfig/systemconfig.conf looks like this: <file> [BOOT] ROOTDEV = /dev/sda1 BOOTDEV = /dev/sda1 DEFAULTBOOT = systemimager [KERNEL0] LABEL = systemimager PATH = /boot/vmlinuz-2.6.20-15-generic INITRD = /boot/initrd.img-2.6.20-15-generic APPEND = root=UUID=52560102-1f7f-4e7e-a0bc-47e151b3fc7f ro quiet splash </file> Needless to say, this file was created automatically and I've not touched it, so I don't think I've mis-configured something. Also, in /var/lib/systemimager/scripts there is a symlink called 'nodename.sh' (with the real node name) pointing to foo_image.master in the same directory. Any insights and suggestions will be greatly appreciated. Thanks! Kindest regards, Doug ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
