TFTP Open Timeout

Gavin Behrens · Aug 17, 2013, 5:54 AM

pxe from different subnet is ok - one way to quickly confirm is do a ps -A |grep tftp to see if its running if it is running but no process id then certainly try the sleep - let me know in the morning… will be evening for me

Tyler Wright · Aug 17, 2013, 5:59 AM

I just remoted in and ran “ps -A | grep tftp” and I get back nothing. I guess I’ll try the “sleep 30” tomorrow.

I’ll keep you posted!

Tyler Wright · Aug 17, 2013, 6:11 AM

Well, unfortunately the sleep 30 did not make a difference. Instead of waiting until morning, I remoted into my work PC, which remoted into an old imaging server, which remoted into a computer on a different subnet that had VMware Workstation on it.

Even with the sleep 30, Fog is still not working for other subnets outside of its own.

Gavin Behrens · Aug 17, 2013, 6:20 AM

just check to see if the process is running again on the linux box “ps -A |grep tftp” if still not running check the logs /var/log on ubuntu

:$ ps -A |grep tftp
1184 ? 00:00:00 in.tftpd

Tyler Wright · Aug 17, 2013, 6:25 AM

The service is still not running. ps -A|grep tftp comes back with nothing.

I tried to find a log in /var/log that looked like tftp but I could not find one.

Gavin Behrens · Aug 17, 2013, 6:28 AM

nothing in syslog … can you post the syslog ?

Tyler Wright · Aug 17, 2013, 6:45 AM

Syslog says this:

Aug 17 02:41:08 Fog dnsmasq-tftp[885]: sent /tftpboot/pxelinux.0 to 10.120.100.41
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: error 0 TFTP Aborted received from 10.120.100.41
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: failed sending /tftpboot/pxelinux.0 to 10.120.100.41
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: sent /tftpboot/pxelinux.0 to 10.120.100.41
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/c9a90b22-2b83-11dc-9346-00e01$
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/01-00-07-e9-1a-82-98 not found
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0A786429 not found
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0A78642 not found
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0A7864 not found
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0A786 not found
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0A78 not found
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0A7 not found
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0A not found
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0 not found
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: sent /tftpboot/pxelinux.cfg/default to 10.120.100.41
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: sent /tftpboot/vesamenu.c32 to 10.120.100.41
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: sent /tftpboot/pxelinux.cfg/default to 10.120.100.41
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: sent /tftpboot/fog/bg.png to 10.120.100.41

Gavin Behrens · Aug 17, 2013, 6:56 AM

so it is proceesing the requests ok - try adding a simple task like mem test or inventory - should all work ok but to get it to boot local have a look at this [url]http://www.fogproject.org/wiki/index.php/Boot_looping_and_Chainloading[/url] - can you post the default file /tftpboot/pxelinux.cfg/default

Tyler Wright · Aug 17, 2013, 6:59 AM

Here is /tftpboot/pxelinux.cfg/default:

DEFAULT vesamenu.c32
MENU TITLE FOG Computer Cloning Solution
MENU BACKGROUND fog/bg.png
MENU MASTER PASSWD $1$0123456789
\n
menu color title 1;36;44 #ffffffff #00000000 std
\n
LABEL fog.local
localboot 0
MENU DEFAULT
MENU LABEL Boot from hard disk
TEXT HELP
Boot from the local hard drive.
If you are unsure, select this option.
ENDTEXT
\n
LABEL fog.memtest
kernel fog/memtest/memtest
MENU LABEL Run Memtest86+
TEXT HELP
Run Memtest86+ on the client computer.
ENDTEXT
\n
LABEL fog.reg
MENU LABEL Quick Host Registration and Inventory
TEXT HELP
Automatically register the client computer,
and perform a hardware inventory.
ENDTEXT
\n
LABEL fog.reginput
kernel fog/kernel/bzImage
append initrd=fog/images/init.gz root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= mode$
MENU LABEL Perform Full Host Registration and Inventory
TEXT HELP
Perform a full host registration on the client
computer, perform a hardware inventory, and
optionally image the host.
ENDTEXT
\n
LABEL fog.quickimage
MENU PASSWD $1$0123456789
kernel fog/kernel/bzImage
append initrd=fog/images/init.gz root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= mod$
MENU LABEL Quick Image
TEXT HELP
This mode will allow you to image this host quickly with
it’s default assigned image.
ENDTEXT
\n
LABEL fog.sysinfo
kernel fog/kernel/bzImage
append initrd=fog/images/init.gz root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= mod$
MENU LABEL Client System Information
TEXT HELP
View basic client information such as MAC address
and FOG compatibility.
ENDTEXT
LABEL fog.debug
MENU PASSWD $1$0123456789
kernel fog/kernel/bzImage
append initrd=fog/images/init.gz root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= mod$
MENU LABEL Debug Mode
TEXT HELP
Debug mode will load the boot image and load a prompt so
you can run any commands you wish.
ENDTEXT
\n
PROMPT 0
TIMEOUT 30\n

Gavin Behrens · Aug 17, 2013, 7:04 AM

just try updating PXELINUX as described [url]http://www.fogproject.org/wiki/index.php/Boot_looping_and_Chainloading[/url]

Tyler Wright · Aug 17, 2013, 7:18 AM

I did. It had no effect.

Tyler Wright · Aug 17, 2013, 7:21 AM

On the subnet where I have my Fog server setup, it PXE boots just fine. On any other subnet, it will not get a DHCP address which leads it to be unable to PXE boot.

Gavin Behrens · Aug 17, 2013, 7:25 AM

so if that subnet isn’t getting dhcp - is there a scope set on the windows box for that subnet with a pool set - is the pool exhausted ? check to see if the pool isn’t exhausted …

Gavin Behrens · Aug 17, 2013, 7:27 AM

i was under the impression it was getting an ip address ??? you syslog post [B]“sent /tftpboot/fog/bg.png to 10.120.100.41” [/B]

right ?[B][/B]

Gavin Behrens · Aug 17, 2013, 7:36 AM

also check to make sure you are able to route to your fog server …

Gavin Behrens · Aug 17, 2013, 7:42 AM

firewall rules ???

Tyler Wright · Aug 17, 2013, 12:14 PM

The pool is definitely not exhausted. If it boots to Windows, it gets its DHCP address.

Yes (to your second post).

In my internal network, there is no firewall whatsoever.

Gavin Behrens · Aug 17, 2013, 1:05 PM

tftp on fog ok - running confirmed
dhcp - giving addresses options 66&67 set ok
routing ok
firewall rules (any,any) nothing should be blocked …ok
try from the windows box (10.120.100.x subnet right?) command prompt tftp [I]foghost[/I] get pxelinux.0 ?

Gavin Behrens · Aug 17, 2013, 1:12 PM

sorry still won’t fix it anyways
the workstation in the pxe process isn’t being allocated an ip address but an up and running os can ?- can you post a screen shot?

Tyler Wright · Aug 17, 2013, 3:57 PM

On a Windows box in the 10.110.100.x subnet, the OS pulls this from my DHCP server:

DHCP Enabled: Yes
Autoconfiguration Enabled: Yes
IPv4 Address: 10.110.100.92
Subnet Mask: 255.255.254.0
Default Gateway: 10.110.100.254
DHCP Server: 10.200.200.3

However, if I PXE boot, it never gets DHCP so it doesn’t continue into PXE.

I use to use Alitirs and it worked just fine. We had its PXE server set to “Use the DHCP port.”

TFTP Open Timeout

187

12.0k

17.3k

155.2k