Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
Finaly i done with installation openssi 1.9.1 on fresh FC3..after that...i
try to adding node..and success...but the problem begin when....my new node
boot up....found dhcp...and start init....there's kernel panic and cant
the detail is in this movie....i compress it with winrar....and i upload it
or the screen shot showing that it's kernel panic in...
My sistem is =3D
P4 1.6 mem 1Gbyte....HD 80 GByte as primary...and HD 40 Gbyte as
but i install the linux in VMware....
Any one can help me what's happen ??...cause i already make new
initrd....and ssi-ksync....but the problem is still there.....plz anyone
help me....cause the deadline is 1 sept to complete the work....thanks...
love Is in The Air....but hard to get it...
So...what we must do ?
> Any one can help me what's happen ??...cause i already make new
> initrd....and ssi-ksync....but the problem is still there.....plz
> anyone help me....cause the deadline is 1 sept to complete the
I dig the archieve and found that once Olivier Silber suffered same
thing. here is his tricks:
You were right, the problem was coming from the TFTPBOOT, and in fact
you must select PXE either if the package installed is an Etherboot.
What I did:
1) copy the files from /boot (initrd and vmlinuz) into the folder
2) modify my file /etc/clustertab to change from Etherboot (E) to
3) modify the file /etc/dhcpd;conf to remove the line about
"etherboot" to keep ONLY PXE booting
4) restart my primary server
try to dig the openssi archieve and search for threads with subject "Can
not start my second node (FC3/SSI 1.9.1)" for complete story.