DHCP Fails only on second install on same hardware
Hey there, I am doing multiple installs on the same hardware via autoyast as I try different configurations. My setup is boot from a PXE server, retrieve my autoyast control file via http and retrieve my SuSE packages via http. My DHCP server is also my tftp server hosting my PXE setup while the http server, hosting the autoyast control file and SuSE packages are on a different server. I run the system through an install, everything's fine. Then, on a second try the system will get it's DHCP information to boot from the PXE server, the kernel and initrd will start up and then attempt to get the DHCP information from within linux at this point where it hangs; however, if I jump to a different tty to see the logs I can see it did indeed get a valid interface configuration from the DHCP server and I can further confirm this by checking the logs; unfortunatly, at this point it does not contact my httpd server for the control file or the packages. I tail the logs on that server and they come up empty. Eventually it will time out and give me an error saying auto installation is impossible and force me into a manual install. Now, if I attempt to do this exact same thing on a new piece of hardware it works fine, until the second time I try to go through an install. Then I can reproduce the problem exactly. Is something changing on the system that autoyast is picking up after an initial install that is preventing a second install from happening? Is there perhaps a problem with my DHCP server? Any help would be much appreciated. Thanks, -Nick
Well, after playing around some more it looks like I found the problem. The problem seems to be with dhcpd and not with autoyast at all. If I expire the lease for the machine I am installing on between installs everything works fine. -Nick On Mon, 12 Jul 2004, Nicholas DeClario wrote:
Hey there,
I am doing multiple installs on the same hardware via autoyast as I try different configurations. My setup is boot from a PXE server, retrieve my autoyast control file via http and retrieve my SuSE packages via http. My DHCP server is also my tftp server hosting my PXE setup while the http server, hosting the autoyast control file and SuSE packages are on a different server.
I run the system through an install, everything's fine. Then, on a second try the system will get it's DHCP information to boot from the PXE server, the kernel and initrd will start up and then attempt to get the DHCP information from within linux at this point where it hangs; however, if I jump to a different tty to see the logs I can see it did indeed get a valid interface configuration from the DHCP server and I can further confirm this by checking the logs; unfortunatly, at this point it does not contact my httpd server for the control file or the packages. I tail the logs on that server and they come up empty.
Eventually it will time out and give me an error saying auto installation is impossible and force me into a manual install.
Now, if I attempt to do this exact same thing on a new piece of hardware it works fine, until the second time I try to go through an install. Then I can reproduce the problem exactly.
Is something changing on the system that autoyast is picking up after an initial install that is preventing a second install from happening? Is there perhaps a problem with my DHCP server? Any help would be much appreciated.
Thanks, -Nick
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
Oh well. Looks like I got a little ahead of myself when I said I solved the problem. Now I believe I solved it. Yesterday when I expired the leases everything worked. Three times in a row. Then it died again. It would just hang after trying to aquire DHCP. Then I tried going through manual mode. I had the same problem. This was via an http install. So I quickly setup my control file and SuSE image via FTP and gave that a try. Manual mode worked no problem. I had a different problem with autoyast at this point though. Now it would continue after the obtaining the DHCP information, download the 'root' image but hang. After reading through a few more docs I found this option 'load_ramdisk=1'. I added that and voila, all is working fine. I have done numerous installs using this method and everything appears to be working fine. So now my question, is anyone else having these difficulties doing an http install??? -Nick On Tue, 13 Jul 2004, Nicholas DeClario wrote:
Well, after playing around some more it looks like I found the problem. The problem seems to be with dhcpd and not with autoyast at all. If I expire the lease for the machine I am installing on between installs everything works fine.
-Nick
On Mon, 12 Jul 2004, Nicholas DeClario wrote:
Hey there,
I am doing multiple installs on the same hardware via autoyast as I try different configurations. My setup is boot from a PXE server, retrieve my autoyast control file via http and retrieve my SuSE packages via http. My DHCP server is also my tftp server hosting my PXE setup while the http server, hosting the autoyast control file and SuSE packages are on a different server.
I run the system through an install, everything's fine. Then, on a second try the system will get it's DHCP information to boot from the PXE server, the kernel and initrd will start up and then attempt to get the DHCP information from within linux at this point where it hangs; however, if I jump to a different tty to see the logs I can see it did indeed get a valid interface configuration from the DHCP server and I can further confirm this by checking the logs; unfortunatly, at this point it does not contact my httpd server for the control file or the packages. I tail the logs on that server and they come up empty.
Eventually it will time out and give me an error saying auto installation is impossible and force me into a manual install.
Now, if I attempt to do this exact same thing on a new piece of hardware it works fine, until the second time I try to go through an install. Then I can reproduce the problem exactly.
Is something changing on the system that autoyast is picking up after an initial install that is preventing a second install from happening? Is there perhaps a problem with my DHCP server? Any help would be much appreciated.
Thanks, -Nick
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
participants (1)
-
Nicholas DeClario