From: <er...@he...> - 2003-09-16 16:19:25
|
On Mon, Sep 15, 2003 at 07:35:37PM -0700, Jeremy Archuleta wrote: > > > On Monday, Sep 15, 2003, at 17:34 US/Pacific, Joshua Aune wrote: > > > On Tue, Sep 16, 2003 at 12:42:34AM +0100, jeremy archuleta wrote: > >> > >> The error from the slave: > >> RARP: BPROC 2223; File 4711; file:/var/beowulf/boot.img > >> recv: <someline about backoff was here> > >> recv: resend listing on port 1024 > >> recv: requesting /var/beowulf/boot.img from 192.168.36.110:4711 > >> recv: response from server: /var/beowulf/boot.img : File unavailable > >> Boot image download failure > > > > The one that usually bites me when I get this error is either the file > > (in this case /var/beowulf/boot.img) doesn't exist (or can't be read). > > > >> Here are the commands to create the phase 1 and phase 2 images: > >> sudo beoboot -1 -f -k /boot/vmlinuz-2.4.21 -o /dev/fd0 > >> sudo beoboot -2 -n -k /boot/vmlinuz-2.4.21 -o /var/beowulf/boot.img > > > > Try an ls -l /var/beowulf/boot.img to make sure it is there and > > readable > > by the beoserv process. > > I know that exists. I am curious to know if I also need to set up a > tftp server. In case I do, I have set one up with boot.img in both > /tftpboot/ and /tftpboot/var/beowulf/ but this didn't help either. > Tomorrow I will try again... try adding the line bootfile /var/beowulf/boot.img to /etc/beowulf/config and restart beoserv. - Erik |