Re: [SSI-users] trying to build OpenSSI [with 2.6.14 kernel] from source

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

I'd do one more thing first... 

mkinitrd -o /boot/initrd.img-2.6.14-ssi-686-smp 2.6.14-ssi-686-smp

... and then the ssi-ksync (making sure that new boot materials are
placed into /tftpboot).

Cheers,
-scott

On  0, "Cumberland, Lonnie" <lon...@ni...> wrote:
> Thanks for getting back to me Scott,
> 
> Just tried your suggestion and am still getting the exact same messages to where Node 2 starts the kernel and then go to the point of halting like before.
> 
> Not sure what is happening here.
> 
> Do you think that I should have to start all over again with a fresh install of Debian "Lenny" on Node 1 and to a complete re-install?
> 
> Node 1 seems to be working from what I can tell and even the "cluster -v" shows it as "UP", but no luck with getting Node 2 all of the way up yet.
> 
> Thanks and have a great day,
> Lonnie Cumberland, Prof.
> Physicist
>  
> (301) 975-6869  (Office)
> (313) 333-2935  (Cell)
> (301) 926-7416  (Fax)
> 
> National Institute of Standards and Technology
> Ionizing Radiation Division (846)
> Radiation Physics Group (245), Room C106
> ADDRESS:
>                  100 Bureau Drive, Stop 8462
>                 Gaithersburg, MD 20899-8462
>  
> EMAIL: lon...@ni...
> http://physics.nist.gov/Divisions/Div846/div846.html
> 
> 
> 
> > -----Original Message-----
> > From: Scott Walters [mailto:sc...@sl...]
> > Sent: Thursday, August 05, 2010 1:14 PM
> > To: Cumberland, Lonnie
> > Cc: John Hughes; Openssi users
> > Subject: Re: [SSI-users] trying to build OpenSSI [with 2.6.14 kernel]
> > from source
> > 
> > Shouldn't have to explicitly add dhcp.
> > 
> > It sounds to me -- taking a guess here -- that your hand-rolled
> > mkinitrd has
> > survived and has never been replaced by OpenSSI's.  Node 2 gets the
> > right kernel
> > but the wrong initrd.
> > 
> > Remove /tftpboot/kernel and initrd first just to make sure that they're
> > being rebuilt and replaced with fresh copies.  ssi-ksync-network is a
> > shell
> > script and error reporting is never great in shell scripts.  I remember
> > having to tweak things a bit in my work of building and installing
> > a patched kernel.  The initnode happily booted the patched kernel
> > but then the other nodes came up on the old, original kernel until
> > I cleaned out that directory and muddled with things until I could get
> > ssi-ksync-network to go.  ssi-ksync calls ssi-ksync-network.  If stuff
> > in /tftpboot isn't rebuilt, step through the script one line at a time
> > (perhaps just run commands at the prompt) and make sure nothing errors
> > out or comes up with null data where it shouldn't.  Though honestly
> > my problems were probably related to not using the prescribed
> > bootloader =)
> > 
> > Cheers,
> > -scott
> > 
> > 
> > 
> > 
> > On  0, "Cumberland, Lonnie" <lon...@ni...> wrote:
> > > Hello All,
> > >
> > > I just found the "Node Hang at boot" over at:
> > >
> > > http://wiki.openssi.org/go/Debian
> > >
> > > which describes part of my problem but even though I tried it as well
> > as the solution in the "Node hang at boot, variant 2", I still get the
> > same message.
> > >
> > > What's strange is that the e1000 driver is included in the ramdisk
> > image as I mounted it to take a look.
> > >
> > > I also, added the /sbin/dhclient to the /etc/mkinitrd/exe before I
> > used "ssi-ksync" to rebuild the ramdisk image.
> > >
> > > No luck so far on getting Node 2 to complete the booting even though
> > it receives the kernel from the tftpd server on Node 1.
> > >
> > > Any ideas?
> > >
> > >
> > > Thanks and have a great day,
> > > Lonnie Cumberland, Prof.
> > > Physicist
> > >
> > > National Institute of Standards and Technology
> > > Ionizing Radiation Division (846)
> > > Radiation Physics Group (245), Room C106
> > > ADDRESS:
> > >                  100 Bureau Drive, Stop 8462
> > >                 Gaithersburg, MD 20899-8462
> > >
> > > EMAIL: lon...@ni...
> > > http://physics.nist.gov/Divisions/Div846/div846.html
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Cumberland, Lonnie [mailto:lon...@ni...]
> > > > Sent: Thursday, August 05, 2010 8:42 AM
> > > > To: John Hughes
> > > > Cc: Openssi users
> > > > Subject: Re: [SSI-users] trying to build OpenSSI [with 2.6.14
> > kernel]
> > > > from source
> > > >
> > > > Greetings All,
> > > >
> > > > I just tried to use "ssi-ksync" on the main node to sync up things
> > for
> > > > the ramimage that is being sent over via PXE boot to the nodes, but
> > it
> > > > seems that the dhcp client is missing from the ram image.
> > > >
> > > > The message that I am getting on node 2 is:
> > > >
> > > > "Gathering Cluster info
> > > >
> > > > DHCP client application not found
> > > >
> > > > Add dhcp client application to /etc/mkinitrd/exe and rebuild
> > ramdisk
> > > > image
> > > >
> > > > ERROR: Could not find a NIC with node configuration. Halting."
> > > >
> > > > I think that I need to edit the ramdisk so that it has the dhck
> > client
> > > > application, but am not sure how to do that.
> > > >
> > > > Any advice would be greatly appreciated.
> > > >
> > > > Thanks and have a great day,
> > > > Lonnie Cumberland, Prof.
> > > > Physicist
> > > >
> > > > National Institute of Standards and Technology
> > > > Ionizing Radiation Division (846)
> > > > Radiation Physics Group (245), Room C106
> > > > ADDRESS:
> > > >                  100 Bureau Drive, Stop 8462
> > > >                 Gaithersburg, MD 20899-8462
> > > >
> > > > EMAIL: lon...@ni...
> > > > http://physics.nist.gov/Divisions/Div846/div846.html
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: John Hughes [mailto:jo...@Ca...]
> > > > > Sent: Thursday, August 05, 2010 5:19 AM
> > > > > To: Cumberland, Lonnie
> > > > > Cc: Scott Walters; Openssi users
> > > > > Subject: Re: [SSI-users] trying to build OpenSSI [with 2.6.14
> > kernel]
> > > > > from source
> > > > >
> > > > > Cumberland, Lonnie wrote:
> > > > > > I have to ask what exact procedure you or others have used and
> > if
> > > > you
> > > > > have the log files from an install that works since I am at a
> > loss as
> > > > > to why this procedure is not working as it seems like it should.
> > > > > >
> > > > > The log files are the exact procedure I followed.
> > > > >
> > > > > I'm sorry that I haven't been able to find any time to work on
> > this
> > > > for
> > > > > the moment, I'll try again this weekend.
> > > > >
> > > > > (Current tasks, not necessarily in priority order:
> > > > >
> > > > > Port a huge application from SCO UnixWare to Debian Linux
> > > > > Finish remodeling daughters bedroom
> > > > > Replace broken fridge
> > > > > Clean up mess left after cutting down tree
> > > > > Work on OpenSSI
> > > > > Hobby project - Porting software to obsolete ICL mainframe
> > computer.
> > > > > (I
> > > > > don't have enough space for a model railway set)).
> > > >
> > > >
> > > > -------------------------------------------------------------------
> > ----
> > > > -------
> > > > The Palm PDK Hot Apps Program offers developers who use the
> > > > Plug-In Development Kit to bring their C/C++ apps to Palm for a
> > share
> > > > of $1 Million in cash or HP Products. Visit us here for more
> > details:
> > > > http://p.sf.net/sfu/dev2dev-palm
> > > > _______________________________________________
> > > > Ssic-linux-users mailing list
> > > > Ssi...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users
> > >
> > > ---------------------------------------------------------------------
> > ---------
> > > The Palm PDK Hot Apps Program offers developers who use the
> > > Plug-In Development Kit to bring their C/C++ apps to Palm for a share
> > > of $1 Million in cash or HP Products. Visit us here for more details:
> > > http://p.sf.net/sfu/dev2dev-palm
> > > _______________________________________________
> > > Ssic-linux-users mailing list
> > > Ssi...@li...
> > > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users