Hi Chris,
I had the same problem with setting up fc10 beta x86_64 after i
svnned the code from the branch-5.1 to my head node.
I managed to get the gui going after a lot of trouble and client
oscarimage and clients network etc but ran into the same problem you
are experiencing when imaging a node same DEFAULTBOOT error! I did not
investigate it as i did not have the time and i did post it on the user
not developer list but nobody replied.
I think it is the new systemimager or system configurator?
It fails the client install at the last moment and when i mount /a and
see /boot all the kernel files are there but trying to reboot the
machine just hangs.
I guess there are some changes made to systemimager which is responsible
for installing the client nodes after i had successfully twice installed
fc9 x86_64 when it was released some time ago.
SOMEBODY OUT THERE PLEASE HELP!
Cheers this should get their attention.
Allan Menezes
Chris Stevenson wrote:
I thought I'd ask people on the list if they've seen this, because
it's frustrating me.
Still trying to finish setting up OSCAR 5.1rc1 on a cluster of intel
quad-cores, master running Fedora 9. I was away for a bit; just getting
back to this.
I have the installation process getting painfully close to the end; "Step
6" in the GUI completes (apparently) successfully but the nodes do not
*quite* finish imaging correctly when I attempt to boot them after this,
before proceeding to testing. "Enable UYOK" and default systemimager-rsync
imaging/Install Mode, PXE-DHCP-TFTP booting, all successful, node disks
get partitioned and populated, and they encouraging show up in the
"Monitor Cluster Deployment" window (bottom of "step 6") for a full five
minutes... and then the installs fail at the 99% complete point.
Checking a console connected to a node, SystemImager is dying when trying
to set up a bootloader: it claims DEFAULTBOOT was not specied. I looked
around on the web and see reference several times to DEFAULTBOOT being set
to the kernel name in /etc/systemconfig/systemconfig.conf (which is
modified by the OSCAR installation GUI, step 6, when you click on "Setup
Network Boot" at the bottom in the "Setup Networking..." section). In
this case, it's being set to "systemimager"; perhaps this is as intended.
HOwever, I tried setting it to the kernel I'm using,
"2.6.25-14.fc9.x86_64", and reimaging - with absolutely no change.
This seems like a simple problem to solve, but after checking files and
testing a bit I can't. Perhaps someone else has run into this and got
past it. I appreciate that SystemImager's site and lists would be the
place to look into this, but also expect that OSCAR users will have seen
this if it was a problem. ANY guidance would be helpful.
I've included the last few dozen lines from the log. Of possible note are
a couple of broken pipes. The rsync daemon *is* running, despite the
report in the log (and the nodes do image, at least mostly).
Thanks in advance,
Chris
[...]
>> insmod /lib/modules/2.6.25-14.fc9.x86_64/kernel/fs/fuse/fuse.ko
>> insmod
/lib/modules/2.6.25-14.fc9.x86_64/kernel/net/bluetooth/bluetooth.ko
>> insmod /lib/modules/2.6.25-14.fc9.x86_64/kernel/net/bluetooth/l2cap.ko
>> insmod
/lib/modules/2.6.25-14.fc9.x86_64/kernel/net/bluetooth/rfcomm/rfcomm.ko
>> insmod
/lib/modules/2.6.25-14.fc9.x86_64/kernel/net/bluetooth/bnep/bnep.ko
>> insmod /lib/modules/2.6.25-14.fc9.x86_64/kernel/net/bridge/bridge.ko
>> insmod
/lib/modules/2.6.25-14.fc9.x86_64/kernel/fs/exportfs/exportfs.ko
>> insmod
/lib/modules/2.6.25-14.fc9.x86_64/kernel/net/sunrpc/auth_gss/auth_rpcgss.ko
>> insmod
/lib/modules/2.6.25-14.fc9.x86_64/kernel/fs/nfs_common/nfs_acl.ko
>> insmod /lib/modules/2.6.25-14.fc9.x86_64/kernel/fs/lockd/lockd.ko
>> insmod /lib/modules/2.6.25-14.fc9.x86_64/kernel/fs/nfsd/nfsd.ko
Choosing filesystem for new initrd: cpio
Creating new initrd from staging dir: /tmp/.systemimager.0
>> cd /tmp/.systemimager.0 && find . ! -name "*~" | cpio -H newc --create
| gzip -9 > /etc/systemimager/boot/initrd.img
142586 blocks
>> ls -l /etc/systemimager/boot/initrd.img
-rw-r--r-- 1 root root 20255928 Nov 7 16:01
/etc/systemimager/boot/initrd.img
Evaluating initrd size to be added in the kernel boot options
(e.g. /etc/systemimager/pxelinux.cfg/syslinux.cfg):
>> suggested value -> ramdisk_size=81533
cat: write error: Broken pipe
Using kernel from: /boot/vmlinuz-2.6.25-14.fc9.x86_64
>> ls -l /etc/systemimager/boot/kernel
-rw-r--r-- 1 root root 2069432 Nov 7 16:01 /etc/systemimager/boot/kernel
WARNING: The rsync daemon was not started. You must run si_prepareclient
again, without the -n option, before you can pull this
client's image to an imageserver.
Your client has been successfully prepared. Boot kernel (copied from
this Linux distribution) and an initrd.img (generated by the
initrd_template package) can be found in /etc/systemimager/boot.
Automatically create configuration file for systemconfigurator:
>> /etc/systemconfig/systemconfig.conf
cat: write error: Broken pipe
cat: write error: Broken pipe
--> Step 6: Successfully enabled UYOK
--> Step 6: Setup network boot: ./setup_pxe -v --uyok
2008-11-7 16:1:20 [main :: Line 290] Checking arguments.
2008-11-7 16:1:20 [main :: Line 116] Restarting xinetd
Stopping xinetd: ESC[60G[ESC[0;32m OK ESC[0;39m]
Starting xinetd: ESC[60G[ESC[0;32m OK ESC[0;39m]
2008-11-7 16:1:20 [main :: Line 118] Enabling tftp
2008-11-7 16:1:20 [main :: Line 132] Creating directories.
2008-11-7 16:1:20 [main :: Line 170] Getting pxelinux.0.
2008-11-7 16:1:20 [main :: Line 175] Copying default pxelinux.cfg file
2008-11-7 16:1:20 [main :: Line 182] Updating
/tftpboot/pxelinux.cfg/default file to skip local.cfg and support
si_monitor.
2008-11-7 16:1:20 [main :: Line 201] Disabling nonexec mappings on x86_64
2008-11-7 16:1:20 [main :: Line 207] Copying SystemImager's message.txt to
/tftpboot/pxelinux.cfg
2008-11-7 16:1:20 [main :: Line 259] Updating
/tftpboot/pxelinux.cfg/default file to support UYOK ramdisk size.
2008-11-7 16:1:20 [main :: Line 265] Copying SystemImager UYOK boot kernel
and initrd.img to /tftpboot
2008-11-7 16:1:20 [main :: Line 272] Symlinking SystemImager UYOK boot
kernel and initrd.img to /tftpboot/kernel and /tftpboot/initrd.img
respectively
--> Step 6: Successfully setup network boot
tcpdump: no process killed
--> Step 6: Stopped listening to network
--> Step 6: Completed successfully
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Oscar-users mailing list
Oscar-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oscar-users
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Oscar-users mailing list
Oscar-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oscar-users
