Struggling with PXE booting during Provisioning

Support
#1

Hello all,

I have been following the yakaz.com tutorial as well as the Foreman
docs and other bits and bobs found on Google.

My set up is Foreman 0.4 on Ubuntu 10.04 LTS x86_64 and the client I
am trying to build is VMware based also 10.04 LTS x86_64

I have followed the tutorial pretty faithfully with only a few minor
changes and have DHCP and TFTP working. However I did have to change
the "pxelinux.cfg" and "boot" directories to 755 to get the client to
see pxelinux.0. I am also using "/var/lib/tftpboot" rather than
"/tftpboot" to keep standards compliant and using the files from the
Ubuntu netboot.tgz.

I can get the client to pick up a lease and after the chmod 755 it can
now see pxelinux.0 and try to load from the menu a kernel, after which
it all starts to fall over.

The message on the client is:

Trying to load: pxelinux.cfg/default
Could not find kernel image: menu

I have logging on tftpd-hpa that seems to show a lot of files missing.
Am I missing something obvious?

Jim

Nov 25 13:04:30 puppet dhcpd: DHCPDISCOVER from 00:50:56:9f:00:37 via eth0
Nov 25 13:04:31 puppet dhcpd: DHCPOFFER on 192.168.1.59 to
00:50:56:9f:00:37 via eth0
Nov 25 13:04:32 puppet dhcpd: DHCPREQUEST for 192.168.1.59
(192.168.1.111) from 00:50:56:9f:00:37 via eth0
Nov 25 13:04:32 puppet dhcpd: DHCPACK on 192.168.1.59 to
00:50:56:9f:00:37 via eth0
Nov 25 13:04:32 puppet in.tftpd[7836]: RRQ from 192.168.1.59 filename
/pxelinux.0
Nov 25 13:04:32 puppet in.tftpd[7836]: tftp: client does not accept options
Nov 25 13:04:32 puppet in.tftpd[7837]: RRQ from 192.168.1.59 filename
/pxelinux.0
Nov 25 13:04:32 puppet in.tftpd[7838]: RRQ from 192.168.1.59 filename
/pxelinux.cfg/421f93fe-b671-2df3-0b55-b1bcf59b601e
Nov 25 13:04:32 puppet in.tftpd[7838]: sending NAK (1, File not found)
to 192.168.1.59
Nov 25 13:04:32 puppet in.tftpd[7839]: RRQ from 192.168.1.59 filename
/pxelinux.cfg/01-00-50-56-9f-00-37
Nov 25 13:04:32 puppet in.tftpd[7839]: sending NAK (1, File not found)
to 192.168.1.59
Nov 25 13:04:32 puppet in.tftpd[7840]: RRQ from 192.168.1.59 filename
/pxelinux.cfg/C0A8013B
Nov 25 13:04:32 puppet in.tftpd[7840]: sending NAK (1, File not found)
to 192.168.1.59
Nov 25 13:04:32 puppet in.tftpd[7841]: RRQ from 192.168.1.59 filename
/pxelinux.cfg/C0A8013
Nov 25 13:04:32 puppet in.tftpd[7841]: sending NAK (1, File not found)
to 192.168.1.59
Nov 25 13:04:32 puppet in.tftpd[7842]: RRQ from 192.168.1.59 filename
/pxelinux.cfg/C0A801
Nov 25 13:04:32 puppet in.tftpd[7842]: sending NAK (1, File not found)
to 192.168.1.59
Nov 25 13:04:32 puppet in.tftpd[7843]: RRQ from 192.168.1.59 filename
/pxelinux.cfg/C0A80
Nov 25 13:04:32 puppet in.tftpd[7843]: sending NAK (1, File not found)
to 192.168.1.59
Nov 25 13:04:32 puppet in.tftpd[7844]: RRQ from 192.168.1.59 filename
/pxelinux.cfg/C0A8
Nov 25 13:04:32 puppet in.tftpd[7844]: sending NAK (1, File not found)
to 192.168.1.59
Nov 25 13:04:32 puppet in.tftpd[7845]: RRQ from 192.168.1.59 filename
/pxelinux.cfg/C0A
Nov 25 13:04:32 puppet in.tftpd[7845]: sending NAK (1, File not found)
to 192.168.1.59
Nov 25 13:04:32 puppet in.tftpd[7846]: RRQ from 192.168.1.59 filename
/pxelinux.cfg/C0
Nov 25 13:04:32 puppet in.tftpd[7846]: sending NAK (1, File not found)
to 192.168.1.59
Nov 25 13:04:32 puppet in.tftpd[7847]: RRQ from 192.168.1.59 filename
/pxelinux.cfg/C
Nov 25 13:04:32 puppet in.tftpd[7847]: sending NAK (1, File not found)
to 192.168.1.59
Nov 25 13:04:32 puppet in.tftpd[7848]: RRQ from 192.168.1.59 filename
/pxelinux.cfg/default
Nov 25 13:04:32 puppet in.tftpd[7849]: RRQ from 192.168.1.59 filename /menu
Nov 25 13:04:32 puppet in.tftpd[7849]: sending NAK (1, File not found)
to 192.168.1.59
Nov 25 13:04:32 puppet in.tftpd[7850]: RRQ from 192.168.1.59 filename /menu.cbt
Nov 25 13:04:32 puppet in.tftpd[7850]: sending NAK (1, File not found)
to 192.168.1.59
Nov 25 13:04:32 puppet in.tftpd[7851]: RRQ from 192.168.1.59 filename /menu.0
Nov 25 13:04:32 puppet in.tftpd[7851]: sending NAK (1, File not found)
to 192.168.1.59
Nov 25 13:04:32 puppet in.tftpd[7852]: RRQ from 192.168.1.59 filename /menu.com
Nov 25 13:04:32 puppet in.tftpd[7852]: sending NAK (1, File not found)
to 192.168.1.59
Nov 25 13:04:32 puppet in.tftpd[7853]: RRQ from 192.168.1.59 filename /menu.c32
Nov 25 13:04:32 puppet in.tftpd[7853]: sending NAK (1, File not found)
to 192.168.1.59

#2

Most of those files are provided by syslinux. You have to symlink or
copy them to your tftp directory. Look at the puppet-foreman module
on github, it does this for you in the foreman-proxy section.

Where ever you got your default menu file should have those missing
files also.

··· On Nov 25, 7:37 am, James Bailey wrote: > Hello all, > > I have been following the yakaz.com tutorial as well as the Foreman > docs and other bits and bobs found on Google. > > http://engineering.yakaz.com/managing-an-infrastructure-datacenter-wi... > > My set up is Foreman 0.4 on Ubuntu 10.04 LTS x86_64 and the client I > am trying to build is VMware based also 10.04 LTS x86_64 > > I have followed the tutorial pretty faithfully with only a few minor > changes and have DHCP and TFTP working. However I did have to change > the "pxelinux.cfg" and "boot" directories to 755 to get the client to > see pxelinux.0. I am also using "/var/lib/tftpboot" rather than > "/tftpboot" to keep standards compliant and using the files from the > Ubuntu netboot.tgz. > > I can get the client to pick up a lease and after the chmod 755 it can > now see pxelinux.0 and try to load from the menu a kernel, after which > it all starts to fall over. > > The message on the client is: > > Trying to load: pxelinux.cfg/default > Could not find kernel image: menu > > I have logging on tftpd-hpa that seems to show a lot of files missing. > Am I missing something obvious? > > Jim > > Nov 25 13:04:30 puppet dhcpd: DHCPDISCOVER from 00:50:56:9f:00:37 via eth0 > Nov 25 13:04:31 puppet dhcpd: DHCPOFFER on 192.168.1.59 to > 00:50:56:9f:00:37 via eth0 > Nov 25 13:04:32 puppet dhcpd: DHCPREQUEST for 192.168.1.59 > (192.168.1.111) from 00:50:56:9f:00:37 via eth0 > Nov 25 13:04:32 puppet dhcpd: DHCPACK on 192.168.1.59 to > 00:50:56:9f:00:37 via eth0 > Nov 25 13:04:32 puppet in.tftpd[7836]: RRQ from 192.168.1.59 filename > /pxelinux.0 > Nov 25 13:04:32 puppet in.tftpd[7836]: tftp: client does not accept options > Nov 25 13:04:32 puppet in.tftpd[7837]: RRQ from 192.168.1.59 filename > /pxelinux.0 > Nov 25 13:04:32 puppet in.tftpd[7838]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/421f93fe-b671-2df3-0b55-b1bcf59b601e > Nov 25 13:04:32 puppet in.tftpd[7838]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7839]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/01-00-50-56-9f-00-37 > Nov 25 13:04:32 puppet in.tftpd[7839]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7840]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/C0A8013B > Nov 25 13:04:32 puppet in.tftpd[7840]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7841]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/C0A8013 > Nov 25 13:04:32 puppet in.tftpd[7841]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7842]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/C0A801 > Nov 25 13:04:32 puppet in.tftpd[7842]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7843]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/C0A80 > Nov 25 13:04:32 puppet in.tftpd[7843]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7844]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/C0A8 > Nov 25 13:04:32 puppet in.tftpd[7844]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7845]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/C0A > Nov 25 13:04:32 puppet in.tftpd[7845]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7846]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/C0 > Nov 25 13:04:32 puppet in.tftpd[7846]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7847]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/C > Nov 25 13:04:32 puppet in.tftpd[7847]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7848]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/default > Nov 25 13:04:32 puppet in.tftpd[7849]: RRQ from 192.168.1.59 filename /menu > Nov 25 13:04:32 puppet in.tftpd[7849]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7850]: RRQ from 192.168.1.59 filename /menu.cbt > Nov 25 13:04:32 puppet in.tftpd[7850]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7851]: RRQ from 192.168.1.59 filename /menu.0 > Nov 25 13:04:32 puppet in.tftpd[7851]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7852]: RRQ from 192.168.1.59 filename /menu.com > Nov 25 13:04:32 puppet in.tftpd[7852]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7853]: RRQ from 192.168.1.59 filename /menu.c32 > Nov 25 13:04:32 puppet in.tftpd[7853]: sending NAK (1, File not found) > to 192.168.1.59
#3

Sorry, a closer look showed me that the first series of "File not
found" isn't an error. PXE will look for files in a specific order,
so it looks first for a menu file named after the PXE booting system's
MAC and other details. The last in that chain I think is default.
Could you post your default file? Does it try to reference another
menu file named "menu" ?

The other possibility is something I ran into before using FOG, which
is the "MENU" option in the defaults file is not supported. I think
that's when you reference "DEFAULT menu.c32" rather than "DEFAULT
vesamenu.c32" , but that's a guess from the behavior I've seen
previously. If that's incorrect someone please correct me.

  • Trey
··· On Nov 25, 7:37 am, James Bailey wrote: > Hello all, > > I have been following the yakaz.com tutorial as well as the Foreman > docs and other bits and bobs found on Google. > > http://engineering.yakaz.com/managing-an-infrastructure-datacenter-wi... > > My set up is Foreman 0.4 on Ubuntu 10.04 LTS x86_64 and the client I > am trying to build is VMware based also 10.04 LTS x86_64 > > I have followed the tutorial pretty faithfully with only a few minor > changes and have DHCP and TFTP working. However I did have to change > the "pxelinux.cfg" and "boot" directories to 755 to get the client to > see pxelinux.0. I am also using "/var/lib/tftpboot" rather than > "/tftpboot" to keep standards compliant and using the files from the > Ubuntu netboot.tgz. > > I can get the client to pick up a lease and after the chmod 755 it can > now see pxelinux.0 and try to load from the menu a kernel, after which > it all starts to fall over. > > The message on the client is: > > Trying to load: pxelinux.cfg/default > Could not find kernel image: menu > > I have logging on tftpd-hpa that seems to show a lot of files missing. > Am I missing something obvious? > > Jim > > Nov 25 13:04:30 puppet dhcpd: DHCPDISCOVER from 00:50:56:9f:00:37 via eth0 > Nov 25 13:04:31 puppet dhcpd: DHCPOFFER on 192.168.1.59 to > 00:50:56:9f:00:37 via eth0 > Nov 25 13:04:32 puppet dhcpd: DHCPREQUEST for 192.168.1.59 > (192.168.1.111) from 00:50:56:9f:00:37 via eth0 > Nov 25 13:04:32 puppet dhcpd: DHCPACK on 192.168.1.59 to > 00:50:56:9f:00:37 via eth0 > Nov 25 13:04:32 puppet in.tftpd[7836]: RRQ from 192.168.1.59 filename > /pxelinux.0 > Nov 25 13:04:32 puppet in.tftpd[7836]: tftp: client does not accept options > Nov 25 13:04:32 puppet in.tftpd[7837]: RRQ from 192.168.1.59 filename > /pxelinux.0 > Nov 25 13:04:32 puppet in.tftpd[7838]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/421f93fe-b671-2df3-0b55-b1bcf59b601e > Nov 25 13:04:32 puppet in.tftpd[7838]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7839]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/01-00-50-56-9f-00-37 > Nov 25 13:04:32 puppet in.tftpd[7839]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7840]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/C0A8013B > Nov 25 13:04:32 puppet in.tftpd[7840]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7841]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/C0A8013 > Nov 25 13:04:32 puppet in.tftpd[7841]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7842]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/C0A801 > Nov 25 13:04:32 puppet in.tftpd[7842]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7843]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/C0A80 > Nov 25 13:04:32 puppet in.tftpd[7843]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7844]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/C0A8 > Nov 25 13:04:32 puppet in.tftpd[7844]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7845]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/C0A > Nov 25 13:04:32 puppet in.tftpd[7845]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7846]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/C0 > Nov 25 13:04:32 puppet in.tftpd[7846]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7847]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/C > Nov 25 13:04:32 puppet in.tftpd[7847]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7848]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/default > Nov 25 13:04:32 puppet in.tftpd[7849]: RRQ from 192.168.1.59 filename /menu > Nov 25 13:04:32 puppet in.tftpd[7849]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7850]: RRQ from 192.168.1.59 filename /menu.cbt > Nov 25 13:04:32 puppet in.tftpd[7850]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7851]: RRQ from 192.168.1.59 filename /menu.0 > Nov 25 13:04:32 puppet in.tftpd[7851]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7852]: RRQ from 192.168.1.59 filename /menu.com > Nov 25 13:04:32 puppet in.tftpd[7852]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7853]: RRQ from 192.168.1.59 filename /menu.c32 > Nov 25 13:04:32 puppet in.tftpd[7853]: sending NAK (1, File not found) > to 192.168.1.59
#4

> Hello all,
>
> I have been following the yakaz.com tutorial as well as the Foreman
> docs and other bits and bobs found on Google.
>
> http://engineering.yakaz.com/managing-an-infrastructure-datacenter-with-foreman-and-puppet.html
>
> My set up is Foreman 0.4 on Ubuntu 10.04 LTS x86_64 and the client I
> am trying to build is VMware based also 10.04 LTS x86_64
>
> I have followed the tutorial pretty faithfully with only a few minor
> changes and have DHCP and TFTP working. However I did have to change
> the "pxelinux.cfg" and "boot" directories to 755 to get the client to
> see pxelinux.0. I am also using "/var/lib/tftpboot" rather than
> "/tftpboot" to keep standards compliant and using the files from the
> Ubuntu netboot.tgz.
>
> I can get the client to pick up a lease and after the chmod 755 it can
> now see pxelinux.0 and try to load from the menu a kernel, after which
> it all starts to fall over.
>
not sure why you see the menu at all, are you sure the server is
managed and in build mode?

if it is, it should simply start the provisioning process.
once done, it might show you a menu (with a default timeout to boot from disk).

Ohad

··· On Fri, Nov 25, 2011 at 3:37 PM, James Bailey wrote: > The message on the client is: > > Trying to load: pxelinux.cfg/default > Could not find kernel image: menu > > I have logging on tftpd-hpa that seems to show a lot of files missing. > Am I missing something obvious? > > Jim > > Nov 25 13:04:30 puppet dhcpd: DHCPDISCOVER from 00:50:56:9f:00:37 via eth0 > Nov 25 13:04:31 puppet dhcpd: DHCPOFFER on 192.168.1.59 to > 00:50:56:9f:00:37 via eth0 > Nov 25 13:04:32 puppet dhcpd: DHCPREQUEST for 192.168.1.59 > (192.168.1.111) from 00:50:56:9f:00:37 via eth0 > Nov 25 13:04:32 puppet dhcpd: DHCPACK on 192.168.1.59 to > 00:50:56:9f:00:37 via eth0 > Nov 25 13:04:32 puppet in.tftpd[7836]: RRQ from 192.168.1.59 filename > /pxelinux.0 > Nov 25 13:04:32 puppet in.tftpd[7836]: tftp: client does not accept options > Nov 25 13:04:32 puppet in.tftpd[7837]: RRQ from 192.168.1.59 filename > /pxelinux.0 > Nov 25 13:04:32 puppet in.tftpd[7838]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/421f93fe-b671-2df3-0b55-b1bcf59b601e > Nov 25 13:04:32 puppet in.tftpd[7838]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7839]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/01-00-50-56-9f-00-37 > Nov 25 13:04:32 puppet in.tftpd[7839]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7840]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/C0A8013B > Nov 25 13:04:32 puppet in.tftpd[7840]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7841]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/C0A8013 > Nov 25 13:04:32 puppet in.tftpd[7841]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7842]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/C0A801 > Nov 25 13:04:32 puppet in.tftpd[7842]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7843]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/C0A80 > Nov 25 13:04:32 puppet in.tftpd[7843]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7844]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/C0A8 > Nov 25 13:04:32 puppet in.tftpd[7844]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7845]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/C0A > Nov 25 13:04:32 puppet in.tftpd[7845]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7846]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/C0 > Nov 25 13:04:32 puppet in.tftpd[7846]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7847]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/C > Nov 25 13:04:32 puppet in.tftpd[7847]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7848]: RRQ from 192.168.1.59 filename > /pxelinux.cfg/default > Nov 25 13:04:32 puppet in.tftpd[7849]: RRQ from 192.168.1.59 filename /menu > Nov 25 13:04:32 puppet in.tftpd[7849]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7850]: RRQ from 192.168.1.59 filename /menu.cbt > Nov 25 13:04:32 puppet in.tftpd[7850]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7851]: RRQ from 192.168.1.59 filename /menu.0 > Nov 25 13:04:32 puppet in.tftpd[7851]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7852]: RRQ from 192.168.1.59 filename /menu.com > Nov 25 13:04:32 puppet in.tftpd[7852]: sending NAK (1, File not found) > to 192.168.1.59 > Nov 25 13:04:32 puppet in.tftpd[7853]: RRQ from 192.168.1.59 filename /menu.c32 > Nov 25 13:04:32 puppet in.tftpd[7853]: sending NAK (1, File not found) > to 192.168.1.59 > > -- > You received this message because you are subscribed to the Google Groups "Foreman users" group. > To post to this group, send email to foreman-users@googlegroups.com. > To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en. > >
#5

I never got a chance to get it working in that contract, my perfered
method to install and then setup foreman is to use the installer
written by Ohad.

Jim

··· On 14 September 2012 06:11, gm wrote: > > Hi, > > Had you resolved the problem? I met the same issue with you, could you share > your experience? >
#6

I worked on it a little over the weekend, I think I have done
something wrong, since the files created by "Build PXE Default" in
boot directory were zero byte files. As a test I copied over the
"Ubuntu-10.04-x86_64-initrd.gz Ubuntu-10.04-x86_64-linux" from the
ubuntu-installer directory and PXE booting worked but not in an
automated way. I don't have time right now to troubleshoot further
and have hand built the systems I needed in VMware and cloned them,
then used Foreman and Puppet to build the application stack on top. I
will however revisit the problem in a few days time when I will have
more time to troubleshoot.

A big thank you for everyone's help so far and an even bigger thank
you for a great piece of software.

Jim

··· On 28 November 2011 09:09, Ohad Levy wrote: > On Fri, Nov 25, 2011 at 3:37 PM, James Bailey wrote: >> Hello all, >> >> I have been following the yakaz.com tutorial as well as the Foreman >> docs and other bits and bobs found on Google. >> >> http://engineering.yakaz.com/managing-an-infrastructure-datacenter-with-foreman-and-puppet.html >> >> My set up is Foreman 0.4 on Ubuntu 10.04 LTS x86_64 and the client I >> am trying to build is VMware based also 10.04 LTS x86_64 >> >> I have followed the tutorial pretty faithfully with only a few minor >> changes and have DHCP and TFTP working. However I did have to change >> the "pxelinux.cfg" and "boot" directories to 755 to get the client to >> see pxelinux.0. I am also using "/var/lib/tftpboot" rather than >> "/tftpboot" to keep standards compliant and using the files from the >> Ubuntu netboot.tgz. >> >> I can get the client to pick up a lease and after the chmod 755 it can >> now see pxelinux.0 and try to load from the menu a kernel, after which >> it all starts to fall over. >> > not sure why you see the menu at all, are you sure the server is > managed and in build mode? > > if it is, it should simply start the provisioning process. > once done, it might show you a menu (with a default timeout to boot from disk). >
#7

>>> Hello all,
>>>
>>> I have been following the yakaz.com tutorial as well as the Foreman
>>> docs and other bits and bobs found on Google.
>>>
>>> http://engineering.yakaz.com/managing-an-infrastructure-datacenter-with-foreman-and-puppet.html
>>>
>>> My set up is Foreman 0.4 on Ubuntu 10.04 LTS x86_64 and the client I
>>> am trying to build is VMware based also 10.04 LTS x86_64
>>>
>>> I have followed the tutorial pretty faithfully with only a few minor
>>> changes and have DHCP and TFTP working. However I did have to change
>>> the "pxelinux.cfg" and "boot" directories to 755 to get the client to
>>> see pxelinux.0. I am also using "/var/lib/tftpboot" rather than
>>> "/tftpboot" to keep standards compliant and using the files from the
>>> Ubuntu netboot.tgz.
>>>
>>> I can get the client to pick up a lease and after the chmod 755 it can
>>> now see pxelinux.0 and try to load from the menu a kernel, after which
>>> it all starts to fall over.
>>>
>> not sure why you see the menu at all, are you sure the server is
>> managed and in build mode?
>>
>> if it is, it should simply start the provisioning process.
>> once done, it might show you a menu (with a default timeout to boot from disk).
>>
> I worked on it a little over the weekend, I think I have done
> something wrong, since the files created by "Build PXE Default" in
BUILD PXE default is not the host pxe default, rather the default when
no host specific match is found (e.g. a menu, recovery etc).

> boot directory were zero byte files. As a test I copied over the
> "Ubuntu-10.04-x86_64-initrd.gz Ubuntu-10.04-x86_64-linux" from the
> ubuntu-installer directory and PXE booting worked but not in an
> automated way. I don't have time right now to troubleshoot further
> and have hand built the systems I needed in VMware and cloned them,
> then used Foreman and Puppet to build the application stack on top. I
> will however revisit the problem in a few days time when I will have
> more time to troubleshoot.
>
the kernel and initrd files should be copied automatically, you are
not required to fetch them directly (assuming you have selected a tftp
proxy in your subnet).

> A big thank you for everyone's help so far and an even bigger thank
> you for a great piece of software.
:slight_smile:

Ohad

··· On Mon, Nov 28, 2011 at 2:58 PM, James Bailey wrote: > On 28 November 2011 09:09, Ohad Levy wrote: >> On Fri, Nov 25, 2011 at 3:37 PM, James Bailey wrote: