Pxe boot files are 0 bytes

Support
1

That's usually caused when the URL that that the proxy retrieves them from
does not actually exist. You've got two courses of action:

  1. Figure out what's wrong with your media URLs, then delete the 0size
    files are toggle boot on a Centos-6.3 host to cause the proxy to redownload
    them
  2. Download the two files yourself and overwrite the 0size ones. The proxy
    won't re-download if the files already exist.

HTH,
Greg

··· On 13 May 2013 18:22, Sean Alderman wrote:

Greetings,
I’m new to foreman. I’ve been building a lab environment to discover
how we can leverage foreman with puppet. On my foreman server I’m running
everything the smart proxy uses locally…bind, dhcpd, tftpd, puppetmaster,
etc. on CentOS 6.3 (with selinux in permissive mode).

When creating a new host from the foreman UI, everything seems to process
through correctly. I have had some smart-proxy struggles so far, but I am
no longer getting errors when I create a new host. Unfortunately, when I
PXE boot the new host, it reports that it can not find the image
boot/CentOS-6.3-x86_64-vmlinuz. A quick look the TFTP directory on the
server shows:

[root@firewall boot]# pwd
/var/lib/tftpboot/boot
[root@firewall boot]# ls -axl
total 8
drwxr-xr-x. 2 foreman-proxy foreman-proxy 4096 May 13 13:10 .
drwxr-xr-x. 5 foreman-proxy root 4096 May 10 15:01 …
-rw-r–r–. 1 foreman-proxy foreman-proxy 0 May 13 13:10
CentOS-6.3-x86_64-initrd.img
-rw-r–r–. 1 foreman-proxy foreman-proxy 0 May 13 13:10
CentOS-6.3-x86_64-vmlinuz

Could anyone help me identify why these files are 0 bytes?

2

Thank you, it would seem I had a bad CentOS Mirror … which I'm not
exactly sure how it got there to begin with so, I've resolved it and am
building successfully.

Moving onto Oracle Linux and Solaris.

Thanks for the fast reply.

··· On Monday, May 13, 2013 1:33:50 PM UTC-4, Greg Sutcliffe wrote: > > On 13 May 2013 18:22, Sean Alderman <salde...@udayton.edu >wrote: > >> Greetings, >> I'm new to foreman. I've been building a lab environment to discover >> how we can leverage foreman with puppet. On my foreman server I'm running >> everything the smart proxy uses locally...bind, dhcpd, tftpd, puppetmaster, >> etc. on CentOS 6.3 (with selinux in permissive mode). >> >> When creating a new host from the foreman UI, everything seems to process >> through correctly. I have had some smart-proxy struggles so far, but I am >> no longer getting errors when I create a new host. Unfortunately, when I >> PXE boot the new host, it reports that it can not find the image >> boot/CentOS-6.3-x86_64-vmlinuz. A quick look the TFTP directory on the >> server shows: >> >> [root@firewall boot]# pwd >> /var/lib/tftpboot/boot >> [root@firewall boot]# ls -axl >> total 8 >> drwxr-xr-x. 2 foreman-proxy foreman-proxy 4096 May 13 13:10 . >> drwxr-xr-x. 5 foreman-proxy root 4096 May 10 15:01 .. >> -rw-r--r--. 1 foreman-proxy foreman-proxy 0 May 13 13:10 >> CentOS-6.3-x86_64-initrd.img >> -rw-r--r--. 1 foreman-proxy foreman-proxy 0 May 13 13:10 >> CentOS-6.3-x86_64-vmlinuz >> >> Could anyone help me identify why these files are 0 bytes? >> > > That's usually caused when the URL that that the proxy retrieves them from > does not actually exist. You've got two courses of action: > > 1) Figure out what's wrong with your media URLs, then delete the 0size > files are toggle boot on a Centos-6.3 host to cause the proxy to redownload > them > 2) Download the two files yourself and overwrite the 0size ones. The proxy > won't re-download if the files already exist. > > HTH, > Greg >