Client PXE boot fail



  • Greetings,

    Let me preface my post by saying I am not very knowledgeable nor experienced with networking/cloning/imaging. I also apologize if I am posting in the incorrect forum. As embarrassing as it is to say, I admittedly don’t know if my problem is OS related or FOG related.

    I installed FOG 0.32 on a machine running Ubuntu 12.04. It’s connected through my network via a Linksys SD205 switch. Next to my Ubuntu machine, I have a windows 7 box intended to be a test client which is connected to my network via the same Linksys switch.

    Things went smoothly until I tried to get my windows box to PXE boot. I continue to get a “PXE-32: TFTP open timeout” error. Did I mention that I really don’t know what I’m doing?

    One final detail: both my Ubuntu & windows machines are identical HP 6000 Pro SFF PC’s with Intel 82579LM NICs.

    Any help, advice, guidance, or prayers will be much appreciated.

    JL



  • I know this thread is a little stale by now but for the sake of posterity, I was having the same issue after rebooting my FOG server (running Ubuntu 12.04 64-bit). I found that issuing:
    [CODE]sudo service tftpd-hpa stop
    sudo service tftpd-hpa start[/CODE]
    brought everything back to life

    I also found that adding
    [CODE]/bin/sleep 30 && /etc/init.d/tftpd-hpa restart[/CODE]
    to rc.local didn’t help (in fact, I already had that in my rc.local), however
    [CODE]/bin/sleep 30 && /etc/init.d/tftpd-hpa stop
    /bin/sleep 30 && /etc/init.d/tftpd-hpa start[/CODE]
    did help. Don’t know why restart didn’t (maybe my server is too quick and needs some more time before it tries to restart the service - [FONT=Consolas]/bin/sleep 60[/FONT] perhaps?)

    For the record (and to help anyone who doesn’t really understand Linux very well), my /etc/rc.local file contents are as follows:
    [CODE]#!/bin/sh -e

    rc.local

    This script is executed at the end of each multiuser runlevel.

    Make sure that the script will “exit 0” on success or any other

    value on error.

    In order to enable or disable this script just change the execution

    bits.

    By default this script does nothing.

    /bin/sleep 30 && /etc/init.d/tftpd-hpa stop
    /bin/sleep 30 && /etc/init.d/tftpd-hpa start

    exit 0[/CODE]



  • [CODE]sudo service --status-all | grep tftpd-hpa[/CODE]

    Output of the above:

    [ ? ] FOGImageReplicator
    [ ? ] FOGMulticastManager
    [ ? ] FOGScheduler
    [ ? ] acpi-support
    [ ? ] acpid
    [ ? ] alsa-restore
    [ ? ] alsa-store
    [ ? ] anacron
    [ ? ] apport
    [ ? ] atd
    [ ? ] avahi-daemon
    [ ? ] bluetooth
    [ ? ] console-setup
    [ ? ] cron
    [ ? ] cups
    [ ? ] dbus
    [ ? ] dmesg
    [ ? ] dns-clean
    [ ? ] failsafe-x
    [ ? ] friendly-recovery
    [ ? ] gssd
    [ ? ] hostname
    [ ? ] hwclock
    [ ? ] hwclock-save
    [ ? ] idmapd
    [ ? ] irqbalance
    [ ? ] killprocs
    [ ? ] lightdm
    [ ? ] modemmanager
    [ ? ] module-init-tools
    [ ? ] mysql
    [ ? ] network-interface
    [ ? ] network-interface-container
    [ ? ] network-interface-security
    [ ? ] network-manager
    [ ? ] networking
    [ ? ] ondemand
    [ ? ] plymouth
    [ ? ] plymouth-log
    [ ? ] plymouth-splash
    [ ? ] plymouth-stop
    [ ? ] plymouth-upstart-bridge
    [ ? ] portmap
    [ ? ] portmap-wait
    [ ? ] pppd-dns
    [ ? ] procps
    [ ? ] rc.local
    [ ? ] resolvconf
    [ ? ] rfkill-restore
    [ ? ] rfkill-store
    [ ? ] rpcbind-boot
    [ ? ] rsyslog
    [ ? ] sendsigs
    [ ? ] setvtrgb
    [ ? ] speech-dispatcher
    [ ? ] statd
    [ ? ] statd-mounting
    [ ? ] sudo
    [ ? ] tftpd-hpa
    [ ? ] udev
    [ ? ] udev-fallback-graphics
    [ ? ] udev-finish
    [ ? ] udevmonitor
    [ ? ] udevtrigger
    [ ? ] ufw
    [ ? ] umountfs
    [ ? ] umountnfs.sh
    [ ? ] umountroot
    [ ? ] vsftpd
    [ ? ] whoopsie
    [ ? ] xinetd


  • Moderator

    is your tftpd-hpa service running now?

    [CODE]sudo service --status-all | grep tftpd-hpa[/CODE]

    don’t miss the d in tftp[U][B]d[/B][/U]-hpa, because there is a tftp-hpa also (without the d)



  • [quote=“flex, post: 8790, member: 1530”]Hi. I just posted the fix in another thread.

    Edit etc/rc.local and add the line one up from exit 0: /bin/sleep 30 && /etc/init.d/tftpd-hpa restart

    It should look like this:

    /bin/sleep 30 && /etc/init.d/tftpd-hpa restart
    exit 0[/quote]

    Hello flex! I edited the file, but am still receiving the PXE-32 error when I reboot my client.



  • Hi. I just posted the fix in another thread.

    Edit etc/rc.local and add the line one up from exit 0: /bin/sleep 30 && /etc/init.d/tftpd-hpa restart

    It should look like this:

    /bin/sleep 30 && /etc/init.d/tftpd-hpa restart
    exit 0



  • Hi Chad! I had found a post describing the TFTP daemon startup issue. The particular post I found suggested the same code you entered except without the word “service”. Anyway, I tried again (both with & without ‘service’) and still get the same PXE-32 error on my windows box.


  • Moderator

    on the FOG server, restart the tftpd-hpa service.[CODE] sudo service tftpd-hpa stop
    sudo service tftpd-hpa start[/CODE]

    try again. Ubuntu 12.04 LTS has issues with the TFTP daemon trying to startup before the interface has an IP address. If this fixes your issue for now, there are posts on this form that show you how modify the startup script to avoid this issue.

    If restarting tftpd-hpa does not solve the issue, we’ll move on to the next step.


Log in to reply
 

504
Online

39.3k
Users

11.0k
Topics

104.6k
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.