Nevermind I was able to fix the issue. Basically what had happened was that somehow the connection of “auto eth0” didn’t have the correct ip configuration settings because when I typed in the “gateway” Ip address section, the IP “vanished.” I just figured out that one must hit “enter” after you type in the IP address in the gateway IP address section. How annoying.

Very noobish mistake and now I know for next time.

Check /etc/hosts for your hostname.
Check /etc/httpd/conf/httpd.conf or other apache conf file for this directive:
ServerName [url=“http://www.example.com:80”]www.example.com:80[/url]
Check /etc/sysconfig/network for the :
HOSTNAME= xxxxxx directive

Somewhere you haven’t defined your machines hostname and apache is saying, “ok fine, we’re ‘localhost’ then . . .”

Here is the Fog.log file
thanks

[url=“/_imported_xf_attachments/0/93_fog.log.txt?:”]fog.log.txt[/url]

It could use some cleaning, but this is the jist.

Amazing, I have been working on this thing for a month now and everyday I have to figure out something new.
I’m about to give up.

Thanks anyway.

Bump!
No one can help me ?

Solved!

[url]http://fogproject.org/forum/threads/deployed-images-hang-at-3.576/[/url]

Reloaded FOG onto a Dell OptiPlex 320 with Ubuntu 10.x. Worked like a dream. I was also able to copy my master image to the new load with no issues (just had to rename it to a existing image in the new FOG DB).

Assuming you installed DHCP with FOG…
[COLOR=#000000]/etc/init.d/dhcp3-server start or [COLOR=#000000]/etc/init.d/dhcp3-server restart[/COLOR][/COLOR]

[COLOR=#000000][COLOR=#000000]Take out the variables and just hook the FOG server to a switch abd the PC(s) you want to test with to it also. [/COLOR][/COLOR]

i figure out the issue
found same issue and answer at [url]http://fogproject.org/forum/threads/unable-to-connect-to-tftp-server.85/[/url]
thanks

Thanks works

This code worked for me.
<tr>
<td class=“c”><a href=“?node=tasks&type=group&direction=onesnap&noconfirm=<?php print $groupid; ?>”><img src=“./images/snap.png” /><p><?php print _(‘Deploy Single Snapin’); ?></p></a></td>
<td><p><?php print _(‘This option allows you to send a single snapin to a host. (Requires FOG Service to be installed on client)’); ?></p></td>
</tr>

best way to do this is put PC’s and MAC in separate vlans and dhcp scoop.

[quote=“Markverg, post: 2290, member: 383”]Kevin, we’ve been running that kernel (1037) since feb 7th only for the 780’s and the problem seems to be solved![/quote]

Would you mind posting the steps you took to do this? I remember seeing how to do it a while ago but I’m in a pinch with a similar problem (Dell 960’s) and I would like to try using a different kernel.

Edit - Nevermind, I found a link in another post that points out how to do this: [url]http://community.spiceworks.com/how_to/show/2338[/url]

I found it by making a Linux search.

The files are
[B]/var/www/fog/commons/functions.include.php[/B]
and
[B]/var/www/fog/management/lib/Host.class.php[/B]

What I did since on the current server, was to define that shutdown= was always “on”

Now I can move the computers after imaging to their correct subnet so that when they boot they will join the correct domain.

// Joakim

thanks! I’ve actually spent quite a bit of time on MSFN over the years trying to figure out the runonce and stuff like that. Hopefully we’ll only be doing 2008 but 2003 is still an option. The old Perl scripted stuff that we used a few years ago had about 30 different motherboards and all the drivers installed to each server. It was a pain and took up a lot of space but never had any HAL issues out of it. I was thinking about making a master image for 2003 with at least all the LAN drivers and chipsets. We will mostly be deploying to 1950, 2950, R series Dell and maybe [just maybe] some IBM x335. I’m going to try to avoid Windows on those as best as I can - lol