DHCP no problem but TFTP always hangs during PXE boot even after restarting it. What gives?



  • Hi everyone

    I am using Ubuntu 14.04 LTS (64-bit)

    Fog version: 1.0.1

    Setup: Isolated / VMware Workstation 10

    Networking is not an issue. I get to register the virtual computer and go in to the FOG Management and set it to upload.

    Now the actual issue is that TFTP hangs…

    I go in to the console and type:

    ~$ sudo start isc-dhcp-server (but then it says “Job is already running: isc-dhcp-server”) So my guest is that DHCP is not an issue.

    I also tried:

    ~$ sudo restart tftpd-hpa

    I then get:

    tftpd-hpa start/running, process 4100

    TFTP still hangs (TFTP…)

    I noticed that the TFTP stops working after I finish doing the configuration for upload on the FOG Management

    Please advice


  • Developer

    [quote=“Mark Carrara, post: 28662, member: 1363”]I have downloaded Ubuntu 13.04 and will load it today. I’m sure with the help on this forum I will get moved to the new version of FOG.

    I thought I remember reading about removing some of the unused/unneeded services from FOG. I am a firm believer in software doing one thing and doing it great and not dong a dozen things well. On our network I have many servers that only do one thing like DHCP, print manger, single app server. I feel it is better for optimization and troubleshooting then having one server do multiple things.[/quote]

    I agree with you there!

    And you are correct, you can slim fog down from anything you don’t use. If you look at the installer script before you run it, you can even remove the calls there to prevent them from being installed.

    However, most of what is installed with fog is required. The only thing that is really optional would be the DHCP sever and that is why there is a question about using FOG as the DHCP. If you don’t want/need it you tell it no and it will still install happily.

    If you remove services you need to accommodate them by providing the services else where. But that would involve a custom set up and that would fall outside of the bounds of our support. Of course we will try our best to get you running, I would prefer if you install fog as it is intended and get it working, then you can play with it further from there if you wish.



  • I have downloaded Ubuntu 13.04 and will load it today. I’m sure with the help on this forum I will get moved to the new version of FOG.

    I thought I remember reading about removing some of the unused/unneeded services from FOG. I am a firm believer in software doing one thing and doing it great and not dong a dozen things well. On our network I have many servers that only do one thing like DHCP, print manger, single app server. I feel it is better for optimization and troubleshooting then having one server do multiple things.[/quote]


  • Developer

    [quote=“Mark Carrara, post: 28573, member: 1363”]I thought it was better to reply to this thread then start a new one. If that was not the case I apologize.

    To be clear this is a Ubuntu issue(bug) not Fog, that I understand and of course you can’t fix a broken Ubuntu? I know I have had other issues with how Ubuntu does things and have had to work around them. So what I am looking for is how to workaround for something that is not working. If it involves doing a fresh install I can do it.

    So to summarize what I hear is the recommendations:

    1. Clean install of Ubuntu 13 (I always install server without a GUI)
    2. Verify Ubuntu is running correctly
    3. Here I am a bit fuzzy. Do you think a new install of 1.01 is what I need to do?[/quote]

    It’s okay to ask questions, I am just sick of these topics complaining about bugs that we as developers of FOG are not capable of fixing because we do not work on the Distribution team of the OS. That is a problem Ubuntu needs to solve, but seems to be making no haste in resolving.

    1.) yes, that is fine, pure CLI is what I run too, FOG has a WEB gui, you don’t really need a fancy interface for your linux, you will only type commands to it anyway.
    2.) yes
    3.) I would use the SVN and download the latest version and install it. When 1.0.1 was released, there were bugs, we knew this but we needed to get the version to the public for testing. We are still working on the Undionly.kpxe system.

    I understand this is frustrating to you as a user because you don’t see, all the behind the scenes jabber, but I assure you, any feelings of despair we too feel on a much greater level. We are also upset that we are using a system that we are learning to use and adapting to use in FOG for us that isn’t exactly working as planned. But I stated once before, FOG is a hodge podge of free services, we do what we can with what we have. None of this software we use is specifically tailored for FOG or the purpose that FOG uses it for, there will always be obstacles to over come.



  • I thought it was better to reply to this thread then start a new one. If that was not the case I apologize.

    To be clear this is a Ubuntu issue(bug) not Fog, that I understand and of course you can’t fix a broken Ubuntu? I know I have had other issues with how Ubuntu does things and have had to work around them. So what I am looking for is how to workaround for something that is not working. If it involves doing a fresh install I can do it.

    So to summarize what I hear is the recommendations:

    1. Clean install of Ubuntu 13 (I always install server without a GUI)
    2. Verify Ubuntu is running correctly
    3. Here I am a bit fuzzy. Do you think a new install of 1.01 is what I need to do?

  • Developer

    [quote=“Mark Carrara, post: 28552, member: 1363”]From this thread and others with the OP I’m not exactly sure if the issue was resolved. I think I have the same issue. But I am using Ubuntu 12.04. You said there was a known issue with 12, but I didn’t have an issue when using FOG .32. Did something change in 1.01 to make this an issue? Would upgrading to Ubuntu 13 solve it? Or did I not set something up when I upgraded?[/quote]

    I’m not sure why you aren’t plagued with the upstart bug, but while using 0.32 on 12.04 which I still have running as a production server, every time I reboot, I restart the service because it fails to wait until my machine has an ip address for the service to start on. I appreciate your concern but when the OS claims to have a bug with the process and its upstart features, it is a bug in the OS not a bug in FOG:

    [url]https://bugs.launchpad.net/ubuntu/+source/tftp-hpa/+bug/522509[/url]

    While this page dates back to 10.04 scroll kindly to the bottom of the page and note what the user said:

    [quote]
    murzz (murzzz) wrote on 2014-04-28:#39
    Still happens for me on Ubuntu 14.04.
    Workaround in comment #30 helped, thanks.[/quote]

    Now, while the issue we are being presented with in 14.04 may not be a confirmed bug, it is confirmed that Ubuntu tends to steer away from the typical Debian mold and has shown it’s ugly head once again deriving from the working apache model of /var/www to /var/www/html, similar to the way that Red Hat distros tend to handle apache, and this may be a minor change but this is the first time we have came across this in Ubuntu and this MAY NOT be the only change, it’s the only one we have found so far. So 14.04 MAY POSSIBLY be an error with the FOG installer and how it tries to install them, but NO WHERE ON THE FORUMS ARE WE RECOMMENDING THAT USERS INSTALL OR TRY TO GET 14.04 WORKING WITH FOG!

    While I understand your frustration, I can confirm that using the 0.33b and all the way up to 1.0.1 while on Ubuntu 13, I did not experience these issues with TFTP. That is not to say that I didn’t find the error occasionally, because I did, but I would try a fresh install of Ubnuntu and FOG and the issue would go away. I uninstall and re-install FOG and Ubuntu MANY times a day just for testing against working and non-working builds, sometimes they don’t even get to reboot before I nuke them and start again. I am an avid Ubuntu user, and I have always pushed Ubuntu, and even I have been telling people to forsake Ubuntu and use a pure Debian. Doing so will do away with the issues Ubuntu is creating by mixing formats, and the tftpd-hpa start issues because it is NOT a bug with tftpd-hpa service, it is a bug with Ubuntu. BUT EVEN USERS OF UBUNTU 13 are complaining of the upstart bug:

    [quote]Omer Siar (omer-baysal) wrote on 2013-06-28:#37
    It affects me on Lubuntu 13.04 Desktop, The workaround in #30 DID NOT work for me

    Martin Pagh Goodwin (martin-goodwin-e) wrote on 2013-10-15:#38
    It affects me on Kubuntu 13.10 Desktop. I manually restart the service at the command line (sudo service tftp-hpa restart)[/quote]

    You can take my recommendation with a grain of salt. Sometimes these issues can be caused by the installer script and most of the time a re-installation will solve the issue.

    I would not recommend “Upgrading” the OS, instead I recommend a back up of FOG and a fresh build of Ubuntu 13. When you get it running, test it. Make sure it is working in your network, download and install a few things like chromium browser and make sure that download packages work. Then after you verify your installation isn’t salty, install fog.

    Don’t misinterpret my meaning behind this, I am not attacking you, I am leaving information so we can let this topic die please!



  • From this thread and others with the OP I’m not exactly sure if the issue was resolved. I think I have the same issue. But I am using Ubuntu 12.04. You said there was a known issue with 12, but I didn’t have an issue when using FOG .32. Did something change in 1.01 to make this an issue? Would upgrading to Ubuntu 13 solve it? Or did I not set something up when I upgraded?



  • Thank you for you reply.

    [LIST]
    []Were you able to replicate the same issue on Ubuntu 14.04 x64?
    [
    ]The issue magically went away somehow.
    [*]The problem I am having now is that I am unable to remove a host no matter what I try. The problem started when I tried full register and inventory instead of the quick register. Now the host is stuck on the Fog management console. The reason I am trying to remove it is so I can add it again. Trying to do a full registration and imaging did not work when I tried from the PXE boot. Now I want to try imaging doing the quick registration. Please advice on how to remove the host that just won’t go away.
    [/LIST]


  • Developer

    [quote=“TheRiceKing, post: 27320, member: 24158”]SO I guess I’m the only one that has to reboot Ubuntu every time TFTP fails to start during PXE boot? Seriously?[/quote]

    Seriously, you seem to be. In the past around version 12 of Ubuntu this was a known issue, AFAIK they fixed this in 13+ I would be willing to bet your installation even though it completed, something is not happy. You could try removing the tftpd-hpa service and re-installing it.

    [code]sudo apt-get purge tftpd-hpa
    sudo apt-get update
    sudo apt-get install tftpd-hpa[/code]

    If you stop the tftp service and start is (not restart issue the stop command, wait, issue the start command, wait) does the tftp service work?

    Ignore that last stuff I misunderstood what you meant when you said the service stopped. You mean something is killing the service or causing it not to respond, not that it started too early, is that correct?

    If it doesn’t work when you start Ubuntu, these typically fix it.

    You could try adding a delay to your upstart job
    edit your /stc/rc.local and add
    [code]/bin/sleep 30 && /etc/init.d/tftpd-hpa restart[/code]

    you could try to change the line
    [code]start on runlevel [2345][/code]

    in /etc/init/tftpd-hpa.conf to

    [code]start on (local-filesystems and net-device-up IFACE!=lo)[/code]

    I am loading up Ubuntu 14.04 now to try to test your issue.



  • SO I guess I’m the only one that has to reboot Ubuntu every time TFTP fails to start during PXE boot? Seriously?


Log in to reply
 

438
Online

39.3k
Users

11.0k
Topics

104.5k
Posts

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