Well,

Based on the information you’ve provided, while the ftp user and password “seem” OK, they’re not okay.

Check the Storage Management Page, specifically the Storage Nodes and select yours.

You should see, under the Management Username and password, the user and password fog is attempting to use to login to FTP.

If you try to access the ftp using the user fog and the password from the aforementioned area, it should let you in, if it doesn’t you likely need to change the Linux FOG User (fog) on your system.

Thank you for the information. Actually, the hard drive was too far gone, I tried RAW and no luck with that it crashed quite quickly. I have copied using another utility for now.

It wasn’t the fact that it wasn’t running at hour 22, but rather it wasn’t taking any comma values.

Have you taken a look at the FOG Server to ensure firewalls are disabled?
In Ubuntu is verified with:
[code]sudo service ufw disable[/code]

In CentOS you need to ALSO disable selinux:
[code]chkconfig iptables off
service iptables stop
sed -i ‘s/SELINUX=enforcing/SELINUX=disabled/’ /etc/sysconfig/selinux
sed -i ‘s/SELINUX=enforcing/SELINUX=disabled/’ /etc/selinux/config
reboot[/code]

Have you verified that the permissions of the /tftpboot directory are correct? They should be set to:
[code]chown -R fog:root /tftpboot[/code]

If you are going to deploy to them then they need to be part of a domain, and you will need to have at least some sort of shared storage that groups of them will have access to. Otherwise there is no way to get the data from point A to point B.

ooops. Thanks for explaining the process. There was a 44 instead of a 04 in the mac address. My fault.

[quote=“Wolfbane8653, post: 30806, member: 3362”]That means you are on the release of v1.1.1. The node problem is a gui/mysql bug. This is just a cosmetic bug and will not effect the storage node functionality. This show be fixed in the next release. It may not be fixed in the next revision.[/quote]

Hi Wolfbane,

Yeah I thought so as I was more than happy with the replication results and the fact that everything worked, Graphs dont bother me too much as I rarely look at the gui 🙂

Been having a think, I have two sites that are linked by a stretched LAN and are around 2 miles apart, I have a storage node on Site B and the FOG Server on site A, do you think it would benefit more setting up the second node as a separate storage group and allocating the images stored on it to the machines on Site B. Thinking it would be a better way as opposed to pulling the images across the link. I can create additional storage nodes to facilitate multi-cast jobs on each site or is it a bit overkill? 🙂

Obviously I would have to have dedicated images for each site but as I have one image that caters for the 4 desktop models and 3 laptop models its not to messy.

Be interesting to see what your thoughts are.

Cheers
Rob

Sorry, I didn’t mean to drop a second thread into this question on the “TFTP boot fails”. I thought they were related but I see now this is a different question entirely. When you boot do you get something like this;

[CODE]
Interl® Boot Agent GE v1.3.66
Copyright © 1997-2010, Intel Corp

Client MAC Addr: F0 DE F1 99 72 C6 GUID: 81F1D9AE AA51 CD11 B3A0 8E5CCB381DF1
Client IP: 172.18.68.24 MASK: 255.255.252.0 DHCP IP: 10.20.1.10
GATEWAY IP: 172.18.68.1
TFTP
PXE-M0F: Exiting Intel Boot Agent
[/CODE]

If so, what do the Client IP: MASK: and DHCP IP: say? It might be the DHCP server is out in the wrong domain or something like that.

[quote=“Sivasubramaniam.T, post: 30781, member: 22852”]Hi,

I am using Fog 1.1.1 on Ubuntu 13.04 (64bit)

First time I have done full host registration and downloaded the image properly.

After registration and imaging, Second time when I try to quick image it get stuck at [url]http://x.x.x.x/fog/service/ipxe.boot.php[/url]…

I have tried changing the boot option to Sanboot/grub/exit style.

I have tried with different kernels.

I have tried with multiple systems. It happens the same with all. Image attached for reference.

Thanks&Regards,
Siva[/quote]

Have you verified that the firewall is disabled, or at the least, allowing Web Traffic to it?

To disable firewall in Ubuntu run:
[code]sudo ufw disable[/code]

Ok, testing 🙂

[code]
— fog.upload.dist 2014-06-19 09:07:10.000000000 -0400
+++ fog.upload 2014-06-19 09:32:02.000000000 -0400
@@ -94,8 +94,8 @@
fi
fi
diskSize=parted -s $hd u kB print | grep "Disk" | grep -v "Flags" | sed 's/Disk \/dev\/[a-zA-Z0-9]*: //' | sed 's/kB//';

partitionStart=`fdisk -lu | grep $part | awk '{print $3}'`; if [ "$osid" == "1" ]; then partitionStart=`fdisk -lu | grep $part | awk '{print $3}'`; if [ "$partitionStart" == "" ]; then partitionStart="63"; fi

@@ -136,22 +136,22 @@
echo “Done”;
if [ “$osid” == “5” ] || [ “$osid” == “6” ] || [ “$osid” == “7” ]; then
if [ “$win7partcnt” == “1” ]; then

win7part1start=`parted -s $hd u kB print | sed -e '/^.1/!d' -e 's/^ [0-9]*[ ]*//' -e 's/kB .*//'`; win7part1start=`parted -s $hd u kB print | sed -e '/^.1/!d' -e 's/^ [0-9]*[ ]*//' -e 's/kB .*//' -e 's/\..*$//'`; if [ "$win7part1start" == "" ]; then handleError "Unable to determine disk start location."; fi adjustedfdsize=`expr $sizefd '+' $win7part1start`; parted -s $hd u kB rm 1 &>/dev/null; parted -s $hd -a opt u kB mkpart primary ntfs 2048s ${adjustedfdsize}kB &>/dev/null; parted -s $hd u kB set 1 boot on &>/dev/null parted -s $hd -a opt u kB mkpart primary ntfs ${partitionStart}s ${adjustedfdsize}kB &>/dev/null; parted -s $hd u kB set 1 boot on &>/dev/null elif [ "$win7partcnt" == "2" ]; then win7part2start=`parted -s $hd u B print | sed -e '/^.2/!d' -e 's/^ [0-9]*[ ]*//' -e 's/kB .*//'`; win7part2start=`parted -s $hd u B print | sed -e '/^.2/!d' -e 's/^ [0-9]*[ ]*//' -e 's/kB .*//' -e 's/\..*$//'`; if [ "$win7part2start" == "" ]; then handleError "Unable to determine disk start location."; fi adjustedfdsize=`expr $sizefd '+' $win7part2start`; parted -s $hd -a opt u kB mkpart primary ntfs ${defaultpart2start}B ${adjustedfdsize}kB &>/dev/null; parted -s $hd u kB set 1 boot on &>/dev/null parted -s $hd u kB set 1 boot on &>/dev/null else handleError "Invalid partition count."; fi

[/code]

my suggestion, install phpmyadmin

some people have reported issues with the Optiplex 760 and gotten them to work using the Official Kernel 3.0.1

Tom,

You are awesome. Worked like a charm. Feel free to move this to the Linux Problems forum if you feel appropriate. I couldn’t decide between the two.

Magnus

I ran into a lot of the problems. Since it’s only an imaging server I literally opened up TCP/UPD 0:65535 ports and disabled Selinux. Everything works great now.

Use my tutorial to create an NTFS partition on the disk and try to push your image again.

[url]http://fogproject.org/forum/threads/quick-format-to-ntfs-with-fog-for-noobs.10349/[/url]

when i try to build udpcast manualy i get the following error’s

root@fog:/root/udpcast-20120424# ./configure
checking for gcc… gcc
checking whether the C compiler works… yes
checking for C compiler default output file name… a.out
checking for suffix of executables…
checking whether we are cross compiling… configure: error: in /root/udpcast-20120424': configure: error: cannot run C compiled programs. If you meant to cross compile, use –host’.
See `config.log’ for more details.

[quote=“Flavalf, post: 30776, member: 24625”]Thank you Jaymes for your answer, I see there is plenty of messages claiming the team’s help on the forum and it’s not the best part of the job to answer and debug users … but it’s the price of fame.;)

I have to say, my point was not to blame FOG, I never thought the cause was the program.
You know, I’m just a teacher who is in charge ( with small time … ) of the network of my college ( nearly 400 Pcs ), and I just want with my poor knowledges to learn how it works and how it can works better !
For sure, using FOG is already a great gain of time and headache for me and I thank you guys again.

So, I will investigate my network as you told me and give feedback as i can.[/quote]

I wasn’t trying to say you were claiming a bug per say, but then it could be! We change and break things often! So run some of these test on an isolated network and see if that helps to increase your imaging speeds. If not we can work from there!

Thanks for being understanding, and good luck!

Ok, No Issues bro. I will try with different possible ways to fix this and let you know. Thanks for your support.

I have something to add to this. Have been using .32 without issues. Recently received a batch of HP z230 workstations. Updated to the newest fog kernel and had no issue uploading a custom image with the 32bit win 7 installed on it. But when I attempt to upload a custom image (that I created from the install dvd) with 64bit Win 7 installed, I get the error. So it seemed like something with 64bit win. Wiping the partitions, and clearing mbr doesn’t seem to help.

Three observations here…

The original “untouched” 64bit hp load can be imaged with no issues, although it looks like it may take 8 hours to do so If I pull the original hp hard drive that came with the machine, and replace it with a 1TB Western Digital (Blue) drive…off of my shelf…things work perfectly. No problem uploading a win7, 64 bit imge. I checked the original hp load, and it is using the gpt partition. Sectors are also 512 bytes.

Like others, I am in a production environment, and was hoping to hold off on updating fog server until after summer 2014.

Anyone else experience this? Any ideas?
tia

-Rick

try fog configuration -> fog settings -> fog boot settings
try messing with the fog_boot_exit_type … see which one works best for you.