Hi Sylvia, this is very strange and the only place I can suspect is the network.
On the client node (with interrupted installation) you can use busybox to set an IP on eth0 and ping addresses. Can you ping the server? Does the server see the packets? Which interfaces do you see on the clients with "busybox ifconfig -a"? Do you see number of RX/TX packets changing? Is the eth0 interface really working? On the other hand: you say the oscar-server does see the DHCP REQUESTS from the client. You should try debugging the dhcpd reactions. dhcpd should actually say why it doesn't offer a new lease to the client. Is the request coming from the same MAC address as the first time (when the client got the PXE boot response)? Best regards, Erich On Wednesday 06 December 2006 12:34, Sylvia Gelman wrote: > Hi, > > we tried now various things but we don´t get much further... > > > So besides the myrinet card you have one or two ethernet interfaces? If > > you > > have two, you should try plugging the cable into the other port. > we have 1 Myrinet and 1 Ethernet, so that´s ok. > > > > From the config file for the install kernel: > > CONFIG_EEPRO100=y > > CONFIG_E100=y > > So these drivers are compiled into the kernel, not available as modules. > so this is fine too ... > > > Try "busybox -h". > this was a very good hint, so we could analyse a bit more. > > we put on the Server in /tftpboot/pxelinux.cfg a file named like the > MacAdress of the client, the line APPEND looks like this: > APPEND vga=extended initrd=initrd.img root=/dev/ram > MONITOR_SERVER=10.7.11.254 MONITOR_CONSOLE=yes HOSTNAME=abakus01 > DOMAINNAME=cluster.test.de DEVICE=eth0 IPADDR=10.7.11.1 > NETMASK=255.255.255.0 BROADCAST=10.7.11.255 GATEWAY=10.7.11.254 > IMAGESERVER=10.7.11.254 > > now we boot the client and it has an IP-Adresse, route seems to be fine > too, but he stops at the skript get_boel_binaries_tarball because it > don´t know the variable IMAGESERVER > > when we start the command in the console: > rcync -av $IMAGESERVER::$IMAGENAME /tmp/boel_binaries > we get the error: no route to host > > also the ping_test failes > > so why the dhcp-Server doesn´t respond to the DHCPREQUEST (on the Server > we see the REQUESTS) > and why the client has no route to host, even the default route is ok? > > thanks in advance for any more hints! > > Sylvia ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Oscar-users mailing list Oscar-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oscar-users
