Thanks Tom! That did it!
I had database issues with the restart, though. It wanted me to update the database (as during initial installation) and when I clicked it, I received a long list of errors due to the database already being there. I followed some of the fixes on modifying the config.class.php and .fogsettings with no luck. I re-installed FOG which required me to do some dnsmasq changes as well. FOG is working again, but I’ll continue to restart and try more fixes.
Thanks again!!!
I have finished the re-install and so far so good! I am both capturing and deploying images, even the laptop I initially noticed the problem with is taking the restored-from-back-up image.
I am currently restoring the rest of the images and will test more tomorrow. I will even restart the FOG server and hope this doesn’t happen again! Haha!
At this time, I think all of the ‘fixes’ for me trying to get the original TFTP timeout issue resolved (before I tried dnsmasq) may be the cause for this. With my inexperience with Linux I was trying what worked for others without actually knowing what I was changing.
The only issue I seem to have now is after I installed dnsmasq, I can no longer browse the internet. It’s a dns issue, for sure, as I can ping IPs, just not names. This also was happening before I re-installed. I’ll work that issue out with the dnsmasq peeps.
I will update after the re-start!
Ahh, my fault, sorry, I was typing with my head over my shoulders. Here is an actual copy/paste of the etc/exports
/images *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
/images/dev *(rw,sync,no_wdelay,no_root_squash,insecure)
I too, don’t like re-installing as we never find out the cause. However, another install would help my experience doing so, and doing a fresh setup knowing I will need to use dnsmasq would be good for me as well.
I’ve got a back-up of all the created images anway, which makes it even less of a hassle.
I certainly appreciate all of the awesome help you’ve provided!
I will update after I get the install complete.
It is a head scratcher, for sure! Do you think a re-install is in order at this point?
Hmm, I seem to have some issue with getting the info posted. I cannot attach the plain text file, and when I try to post as I have been posting, it says it is spam. 
Here is the output of what I am able to get by the spam filter. It basically continues down listing each of the images similar to the “VEIGoldenImage” and “VEIUbuntu1404x647010” files below.
@VEI-FOG:~# ls -alR /images
/images:
total 92
drwxrwxrwx 23 root root 4096 Mar 5 11:07 .
drwxr-xr-x 25 root root 4096 Feb 10 11:04 …
drwxrwxrwx 2 root root 4096 Mar 5 11:07 dev
-rwxrwxrwx 1 root root 0 Feb 25 16:36 .mntcheck
drwxrwxrwx 2 root root 4096 Feb 10 11:04 postdownloadscripts
drwxrwxrwx 2 root root 4096 Feb 19 15:25 PRC04
drwxrwxrwx 2 root root 4096 Feb 18 17:08 VEIGoldenImage
drwxrwxrwx 2 root root 4096 Mar 5 10:38 VEIUbuntu1404x647010
drwxrwxrwx 2 root root 4096 Feb 12 14:21 VEIWin75520Laptop
drwxrwxrwx 2 root root 4096 Feb 11 14:41 Win76430
drwxrwxrwx 2 root root 4096 Feb 12 14:08 Win7Accounting
drwxrwxrwx 2 root root 4096 Feb 16 16:47 Win7Acer4620Laptop
drwxrwxrwx 2 root root 4096 Feb 13 11:20 Win7BaseImage
drwxrwxrwx 2 root root 4096 Feb 13 12:07 Win7CivilDesigner
drwxrwxrwx 2 root root 4096 Feb 12 15:32 Win7CivilEngineer
drwxrwxrwx 2 root root 4096 Feb 16 17:09 Win7CostControls
drwxrwxrwx 2 root root 4096 Feb 12 15:38 Win7IEwCAD
drwxrwxrwx 2 root root 4096 Feb 12 15:28 Win7InstrumentElectrical
drwxrwxrwx 2 root root 4096 Feb 16 14:12 Win7Mechanical
drwxrwxrwx 2 root root 4096 Feb 18 15:10 Win7PipingwCAD
drwxrwxrwx 2 root root 4096 Feb 12 15:25 Win7Process
drwxrwxrwx 2 root root 4096 Feb 12 15:49 Win7ProjectControls
drwxrwxrwx 2 root root 4096 Mar 5 10:55 Win7TestImage
drwxrwxrwx 2 root root 4096 Feb 19 09:06 Win7ZboxAcer
/images/dev:
total 8
drwxrwxrwx 2 root root 4096 Mar 5 11:07 .
drwxrwxrwx 23 root root 4096 Mar 5 11:07 …
-rwxrwxrwx 1 root root 0 Feb 25 16:38 .mntcheck
/images/postdownloadscripts:
total 12
drwxrwxrwx 2 root root 4096 Feb 10 11:04 .
drwxrwxrwx 23 root root 4096 Mar 5 11:07 …
-rwxrwxrwx 1 root root 233 Feb 10 11:04 fog.postdownload
/images/PRC04:
total 56336000
drwxrwxrwx 2 root root 4096 Feb 19 15:25 .
drwxrwxrwx 23 root root 4096 Mar 5 11:07 …
-rwxrwxrwx 1 root root 512 Feb 19 15:24 d1.mbr
-rwxrwxrwx 1 root root 78557 Feb 19 15:24 d1p1.img
-rwxrwxrwx 1 root root 192215879 Feb 19 15:25 d1p2.img
-rwxrwxrwx 1 root root 57495742045 Feb 19 16:54 d1p3.img
/images/VEIGoldenImage:
total 12590772
drwxrwxrwx 2 root root 4096 Feb 18 17:08 .
drwxrwxrwx 23 root root 4096 Mar 5 11:07 …
-rwxrwxrwx 1 root root 1 Feb 18 16:55 d1.fixed_size_partitions
-rwxrwxrwx 1 root root 0 Feb 18 16:58 d1.has_grub
-rwxrwxrwx 1 root root 1048576 Feb 18 16:58 d1.mbr
-rwxrwxrwx 1 root root 259 Feb 18 16:58 d1.minimum.partitions
-rwxrwxrwx 1 root root 15 Feb 18 16:55 d1.original.fstypes
-rwxrwxrwx 1 root root 259 Feb 18 16:55 d1.original.partitions
-rwxrwxrwx 1 root root 0 Feb 18 16:55 d1.original.swapuuids
-rwxrwxrwx 1 root root 8141788569 Feb 18 17:08 d1p1.img
-rwxrwxrwx 1 root root 4750076687 Feb 18 16:31 VEIGoldenImage
/images/VEIUbuntu1404x647010:
total 1788480
drwxrwxrwx 2 root root 4096 Mar 5 10:38 .
drwxrwxrwx 23 root root 4096 Mar 5 11:07 …
-rwxrwxrwx 1 root root 4 Mar 5 10:34 d1.fixed_size_partitions
-rwxrwxrwx 1 root root 0 Mar 5 10:34 d1.has_grub
-rwxrwxrwx 1 root root 1048576 Mar 5 10:34 d1.mbr
-rwxrwxrwx 1 root root 310 Mar 5 10:34 d1.minimum.partitions
-rwxrwxrwx 1 root root 48 Mar 5 10:34 d1.original.fstypes
-rwxrwxrwx 1 root root 310 Mar 5 10:34 d1.original.partitions
-rwxrwxrwx 1 root root 47 Mar 5 10:38 d1.original.swapuuids
-rwxrwxrwx 1 root root 1830317087 Mar 5 10:38 d1p1.img
-rwxrwxrwx 1 root root 551 Mar 5 10:38 d1p2.img
Below are the results of the commands.
root@VEI-3000D:/home/administrator# sudo mkdir -p /mnt/nfstest && sudo mount -v 10.0.2.250:/images /mnt/nfstest
mount: no type was given - I’ll assume nfs because of the colon
mount.nfs: timeout set for Thu Mar 5 08:41:21 2015
mount.nfs: trying text-based options ‘vers=4,addr=10.0.2.250,clientaddr=10.0.2.153’
root@VEI-3000D:/home/administrator# sudo ls -al /mnt/nfstest
total 12
drwxrwxrwx 22 root root 4096 Feb 27 09:45 .
drwxr-xr-x 3 root root 4096 Mar 5 08:37 …
drwxrwxrwx 2 root root 4096 Feb 19 16:54 dev
root@VEI-3000D:/home/administrator# sudo umount /mnt/nfstest
root@VEI-3000D:/home/administrator#
Oddly enough, I have done some testing and I am able to capture images via FOG. However, I receive the ‘permissions denied’ error any time I try to deploy an image using various workstations and images. Any ideas on why this is happening?
Thanks again!
My fog servers IP is 10.0.2.250
Yes! There is now a difference with those commands. They seem to be working now! (I did have to install nfs-common on the workstation).
root@VEI-3000D:/home/administrator# sudo mkdir -p /mnt/nfstest && mount -v 10.0.2.250:/images /mnt/nfstest
mount: no type was given - I’ll assume nfs because of the colon
mount.nfs: timeout set for Wed Mar 4 11:14:44 2015
mount.nfs: trying text-based options ‘vers=4,addr=10.0.2.250,clientaddr=10.0.2.153’
root@VEI-3000D:/home/administrator# sudo umount /mnt/nfstest
root@VEI-3000D:/home/administrator# sudo mount -v 10.0.2.250:/images/dev /mnt/nfstest
mount: no type was given - I’ll assume nfs because of the colon
mount.nfs: timeout set for Wed Mar 4 11:15:30 2015
mount.nfs: trying text-based options ‘vers=4,addr=10.0.2.250,clientaddr=10.0.2.153’
root@VEI-3000D:/home/administrator# sudo umount /mnt/nfstest && rmdir /mnt/nfstest
root@VEI-3000D:/home/administrator#
Alright, from a workstation on the same subnet I tried the commands you listed…here are the results.
root@VEI-3000D:~# sudo mkdir -p /mnt/nfstest && mount -v 10.0.2.250:/images /nfstest
mount: no type was given - I’ll assume nfs because of the colon
mount: mount point /nfstest does not exist
root@VEI-3000D:~# sudo umount /nfstest
umount: /nfstest: not found
root@VEI-3000D:~# sudo mount -v 10.0.2.250:/images/dev /nfstest
mount: no type was given - I’ll assume nfs because of the colon
mount: mount point /nfstest does not exist
root@VEI-3000D:~# umount /nfstest && rmdir /nfstest
umount: /nfstest: not found
And, just for further testing to eliminate the folder not being there, I tried to mount to the /images folder.
root@VEI-3000D:~# sudo mount -v 10.0.2.250:/images
mount: can’t find 10.0.2.250:/images in /etc/fstab or /etc/mtab
root@VEI-3000D:~#
Thank you again for your help!!!
Wayne, I have disconnected the drive, no change.
Frank, I have attached the output of the permissions. I am loading another PC with Ubuntu to help with testing.
The FOG setup should have made the share able to be mounted even after a restart, correct?
Thank you again, for your help. Getting into Linux has a decently steep learning curve and I appreciate your help!
[url=“/_imported_xf_attachments/1/1721_IMAG2054.jpg?:”]IMAG2054.jpg[/url]
Hello again, I have been using FOG for about a month or so with great success. I have uploaded about 30 different images to the server without a problem…until now.
I restarted the FOG server to install an internal back-up drive. I received the TFTP timeout, but then remembered to restart tftpd-hpa which resolved that issue.
I was able to register a new host, but now receive “Permission Denied” on the host when attempting to mount the /images folder on the server.
Most issues I see with this are when people move their /images folder to a different location. I have not made any changes other than the drive (which I have not mounted) and the restart.
I have tried a few fixes with no luck.
So far I have made sure the firewall is turned off, and /etc/exports looks like this…
/images *(ro_sync,no_wdelay,insecure_locks,no_root_squash,insecure)
/images/dev *(rw,sync,no_wdelay,no_root_squash,insecure)
This is on Ubuntu 14.04 with FOG 1.2.0
Again, this has been running well until the restart. Being so new to this, is there anything else I should check that a restart may have done?
Thank you again for your help!
[url=“/_imported_xf_attachments/1/1716_IMAG2053.jpg?:”]IMAG2053.jpg[/url]
Update It was the leftover opt 67 pointing to the incorrect boot file causing the issue I was having after installing DNSMASQ.
Well, I was going through and found that I already had a link from .kpxe to .0, I made sure the permissions were the same on both files…and just for fun I decided to see what happened and I actually just pulled up the FOG menu on the workstation which I just registered.
I am now capturing my first image! I ‘think’ I may have left option 66/67 active in my DHCP server which was causing the issue.
I have been going back and forth between my landesk PXE setup and the FOG setup when a new image was needed.
I will test my theory and update.
Thank you all, very much, for your help and suggestions in getting this going!
[quote=“Junkhacker, post: 42057, member: 21583”]have you tried Tom’s suggestion? [CODE]sudo ufw disable[/CODE][/quote]
Yes, disabling the firewall was one of the steps in the config.
I’ve got it connected through an un-managed switch for the “imaging bench” (server resides in the same room for now), which connects to the rest of the network/servers through a layer 3 switch.
I read somewhere that some switches will only pass a file with a “.0” at the end…I am wondering if that might be the case here…Any thoughts on that?
Oh, ok…Yes, I have already initialized the database when it asked.
I am not able to ‘get’ from a workstation, still.
[quote=“Jaymes Driver, post: 41993, member: 3582”]When you say workstation, you mean a windows machine in the same network as the FOG server? If your DHCP options are correct, you should at least get some kind of out put.
I highly recommend DNSMASQ. It seems that you are having difficulty resolving your bootfile name.
Alright, I followed this setup and I am now getting through. However, I am unclear what the instructions meant by “update the schema…” for the iPXE boot.
When I PXE boot from a workstation, I choose “boot to network”, which then gets me to the attached screen/error.
Would you enlighten me further, please? I’d hate to mess something up when the resolution seems so close!
Thank you again for all your help!
[url=“/_imported_xf_attachments/1/1674_IMAG2049.jpg?:”]IMAG2049.jpg[/url]
[quote=“Wolfbane8653, post: 41991, member: 3362”]so you are getting Failed and not “Received XXXX bytes in X.X seconds…” on the client.
I know this is for debian but you showed that iptables were installed so please run the following on the server and rerun the tftp tests on the client.
[CODE]iptables -F
iptables -X
iptables -t nat -F
iptables -t nat -X
iptables -t mangle -F
iptables -t mangle -X
iptables -P INPUT ACCEPT
iptables -P OUTPUT ACCEPT
iptables -P FORWARD ACCEPT[/CODE][/quote]
Done, still the same outcome. Thank you.
Jaymes, thank you, I will give that a try if there isn’t something obvious I have simply overlooked in my config causing the issue.
My environment is an interesting mix, for sure. I would not be surprised if it is causing the issue as well.
[quote=“Wolfbane8653, post: 41984, member: 3362”]Please try the information in this wiki.
[url]http://fogproject.org/wiki/index.php/Tftp_timeout[/url]…[/quote]
Thank you, I have followed this guide and everything seems to be working with the exception of being able to “get undionly.kpxe” from a workstation (on the server it works.)
[quote=“Uncle Frank, post: 41961, member: 28116”]TFTP configuration is under /etc/default/tftp-hpa (maybe a little different on Ubuntu but should still be in that directory!):
[CODE]# /etc/default/tftpd-hpa
TFTP_USERNAME=“root”
TFTP_DIRECTORY=“/tftpboot”
TFTP_ADDRESS=“0.0.0.0:69”
TFTP_OPTIONS=“-s”[/CODE]
Maybe firewall rules prevent you from connecting via TFTP from the outside?! Please post the output of the following command run on the FOG server:
[CODE]iptables -L -n -v[/CODE][/quote]
Yes, the /tftpd-hpa file looked exactly like that, in the same path.
Here is the output…Thank you for your help!
Chain INPUT (policy ACCEPT 714K packets, 82M bytes)
pkts bytes target prot opt in out source destination
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 27794 packets, 4641K bytes)
pkts bytes target prot opt in out source destination
Greetings, I have setup FOG 1.2 on Ubuntu 14.04 on a dedicated “server”. I get a PXE-E32 TFTP open timeout error when attempting to PXE boot a workstation. I followed the fog wiki on the config.
I can ping the server, and can “get undionly.kpxe” on the server, but not on a workstation.
I have followed several checklists, but cannot figure out what about the config won’t allow the tftp connection.
Any suggestions on what to check/try next?
Any help is greatly appreciated!!!