Hmm, that must be it then in that case. We use Lync here. Ok, thanks I will look at putting the FOG server on it’s own VLAN. I only use it for imaging anyway so it shouldn’t cause too many problems.

Thanks for the info.

Yes, I have tried with a few different machines. Each machine seems to be consistently failing now.

Hi, so I have been having some problems with fog lately. The issue is very difficult to pinpoint as it sometimes works flawlessly and sometimes does not.
For example, I booted to FOG and registered a host, assigned the image and imaged a machine perfectly all working great. Then rebooted and tried to get to get back into the FOG menu but all I got was default.ipxe…timed out. I read that there have been some problems with booting iPXE so I tried [URL=‘http://fogproject.org/wiki/index.php/Chainloading_PXE_to_iPXE_using_pxelinux.0’]chainloading PXE to iPXE. [/URL]This seemed to be working for me as the FOG menu came back. But when I try to load any of the menu items, the client can’t interact with the network.
For example at the moment, I can go to my advanced boot menu, [URL=‘http://fogproject.org/forum/threads/fog-0-33b-edit-pxe-menu.10403/#post-26425’]details about this computer[/URL] and it will show an IP of 10.129.1.124 but when I go to the main menu and “check client system information”, I get lots of “DHCP/BOOTP: Reply not for us…” messages.
[IMG]http://i.imgur.com/fjbDym8.jpg[/IMG]
When the “check client system information” finally loads, I try to check the assigned IP details and it doesn’t show anything for eth0 as if it hasn’t been able to initialize it.
[IMG]http://i.imgur.com/ZN0yj68.jpg[/IMG]

Any idea where to go next for troubleshooting?

Output from Syslog when booting to FOG:
[CODE]Oct 8 13:29:22 rndubuntu dnsmasq-dhcp[6454]: 3196037634 available DHCP subnet: 10.129.1.4/255.255.252.0
Oct 8 13:29:22 rndubuntu dnsmasq-dhcp[6454]: 3196037634 vendor class: PXEClient:Arch:00000:UNDI:002001
Oct 8 13:29:22 rndubuntu dnsmasq-dhcp[6454]: 3196037634 user class: iPXE
Oct 8 13:29:22 rndubuntu dnsmasq-dhcp[6454]: 3196037634 PXE(eth0) 00:24:e8:b3:c7:8c proxy
Oct 8 13:29:22 rndubuntu dnsmasq-dhcp[6454]: 3196037634 tags: eth0
Oct 8 13:29:22 rndubuntu dnsmasq-dhcp[6454]: 3196037634 bootfile name: undionly.kpxe
Oct 8 13:29:22 rndubuntu dnsmasq-dhcp[6454]: 3196037634 next server: 10.129.1.4
Oct 8 13:29:22 rndubuntu dnsmasq-dhcp[6454]: 3196037634 broadcast response
Oct 8 13:29:22 rndubuntu dnsmasq-dhcp[6454]: 3196037634 sent size: 1 option: 53 message-type 2
Oct 8 13:29:22 rndubuntu dnsmasq-dhcp[6454]: 3196037634 sent size: 4 option: 54 server-identifier 10.129.1.4
Oct 8 13:29:22 rndubuntu dnsmasq-dhcp[6454]: 3196037634 sent size: 9 option: 60 vendor-class 50:58:45:43:6c:69:65:6e:74
Oct 8 13:29:22 rndubuntu dnsmasq-dhcp[6454]: 3196037634 sent size: 17 option: 97 client-machine-id 00:4c:4c:45:44:00:31:37:10:80:57:ca:c0:4f…
Oct 8 13:29:22 rndubuntu dnsmasq-dhcp[6454]: 3196037634 sent size: 41 option: 43 vendor-encap 06:01:03:0a:04:00:50:58:45:08:07:80:00:01…
Oct 8 13:29:22 rndubuntu dnsmasq-dhcp[6454]: 3196037634 available DHCP subnet: 10.129.1.4/255.255.252.0
Oct 8 13:29:22 rndubuntu dnsmasq-dhcp[6454]: 3196037634 vendor class: PXEClient:Arch:00000:UNDI:002001
Oct 8 13:29:22 rndubuntu dnsmasq-dhcp[6454]: 3196037634 user class: iPXE
[/CODE]

Apache2 access.log
[CODE]10.129.1.124 - - [08/Oct/2014:13:32:52 +0100] “GET /fog/service/ipxe/boot.php?mac=00%3A24%3Ae8%3Ab3%3Ac7%3A8c HTTP/1.1” 200 3101 “-” “iPXE/1.0.0+ (53653)”
10.129.1.124 - - [08/Oct/2014:13:32:52 +0100] “GET /fog/service/ipxe/bg.png HTTP/1.1” 200 45139 “-” “iPXE/1.0.0+ (53653)”
10.129.1.124 - - [08/Oct/2014:13:32:55 +0100] “GET /fog/service/ipxe/advanced.php HTTP/1.1” 200 1567 “-” “iPXE/1.0.0+ (53653)”
10.129.1.124 - - [08/Oct/2014:13:32:57 +0100] “GET /fog/gparted/vmlinuz HTTP/1.1” 200 2650370 “-” “iPXE/1.0.0+ (53653)”
10.129.1.124 - - [08/Oct/2014:13:32:58 +0100] “GET /fog/gparted/initrd.img HTTP/1.1” 200 16241083 “-” “iPXE/1.0.0+ (53653)”
[/CODE]

Attached the foginstall.log file if that’s any use too.
Appreciate the help!

[url=“/_imported_xf_attachments/1/1414_foginstall.log.txt?:”]foginstall.log.txt[/url]

[CODE]sudo ufw disable
Firewall stopped and disabled on system startup[/CODE]

I have done that now. I don’t have the offending machine anymore but when I get it back I will test it and report.

Thanks.

Didn’t want to start a new thread as I think my issue is similar. I have tried everything posted here but the problem remains. tftp timeout on downloading /default.ipxe

One major difference, I can tftp locally and download the file so I don’t think it’s permissions.
No IP Tables running. SELinux is disabled.

One thing of note… any time I reboot the server, I get the Database Schema Installer / Updater which a MySQL service restart clears.

Server moved from an old laptop to a Dell PowerEdge 2900. Move went fine and I was able to test earlier in the month but now when I go to use it, the default.ipxe times out. I have been able to register and backup / deploy images with this exact setup less than two weeks ago so I am assuming an update that I pushed through recently has caused it to break. Here’s my apt history from when it last worked - approximately…
[CODE]
Start-Date: 2014-08-14 06:42:31
Install: linux-image-extra-3.13.0-34-generic:amd64 (3.13.0-34.60, automatic), linux-image-3.13.0-34-generic:amd64 (3.13.0-34.60, automatic), linux-headers-3.13.0-34-generic:amd64 (3.13.0-34.60, automatic), linux-headers-3.13.0-34:amd64 (3.13.0-34.60, automatic)
Upgrade: linux-headers-generic:amd64 (3.13.0.33.39, 3.13.0.34.40), linux-libc-dev:amd64 (3.13.0-33.58, 3.13.0-34.60), linux-image-generic:amd64 (3.13.0.33.39, 3.13.0.34.40), linux-generic:amd64 (3.13.0.33.39, 3.13.0.34.40)
End-Date: 2014-08-14 06:43:13

Start-Date: 2014-08-14 11:35:25
Commandline: apt-get install dnsmasq
Install: libnetfilter-conntrack3:amd64 (1.0.4-1, automatic), libmnl0:amd64 (1.0.3-3ubuntu1, automatic), dnsmasq-base:amd64 (2.68-1, automatic), dnsmasq:amd64 (2.68-1)
End-Date: 2014-08-14 11:35:28

Start-Date: 2014-08-25 12:27:17
Commandline: apt-get install whois
Install: whois:amd64 (5.1.1)
End-Date: 2014-08-25 12:27:20

Start-Date: 2014-08-25 12:28:11
Commandline: apt-get upgrade
Upgrade: python3-problem-report:amd64 (2.14.1-0ubuntu3.2, 2.14.1-0ubuntu3.3), libsystemd-login0:amd64 (204-5ubuntu20.3, 204-5ubuntu20.4), accountsservice:amd64 (0.6.35-0ubuntu7, 0.6.35-0ubuntu7.1), libgirepository-1.0-1:amd64 (1.40.0-1ubuntu0.1, 1.40.0-1ubuntu0.2), systemd-services:amd64 (204-5ubuntu20.3, 204-5ubuntu20.4), rpcbind:amd64 (0.2.1-2ubuntu1, 0.2.1-2ubuntu2.1), libsystemd-daemon0:amd64 (204-5ubuntu20.3, 204-5ubuntu20.4), libpam-systemd:amd64 (204-5ubuntu20.3, 204-5ubuntu20.4), udev:amd64 (204-5ubuntu20.3, 204-5ubuntu20.4), libudev1:amd64 (204-5ubuntu20.3, 204-5ubuntu20.4), gir1.2-glib-2.0:amd64 (1.40.0-1ubuntu0.1, 1.40.0-1ubuntu0.2), python3-distupgrade:amd64 (0.220.2, 0.220.4), python3-gi:amd64 (3.12.0-1, 3.12.0-1ubuntu1), apport:amd64 (2.14.1-0ubuntu3.2, 2.14.1-0ubuntu3.3), libaccountsservice0:amd64 (0.6.35-0ubuntu7, 0.6.35-0ubuntu7.1), python3-apport:amd64 (2.14.1-0ubuntu3.2, 2.14.1-0ubuntu3.3), ubuntu-release-upgrader-core:amd64 (0.220.2, 0.220.4), net-tools:amd64 (1.60-25ubuntu2, 1.60-25ubuntu2.1)
End-Date: 2014-08-25 12:28:49

Start-Date: 2014-08-25 12:41:11
Commandline: apt-get autoremove
Remove: linux-image-extra-3.13.0-32-generic:amd64 (3.13.0-32.57), linux-image-3.13.0-32-generic:amd64 (3.13.0-32.57), linux-headers-3.13.0-32-generic:amd64 (3.13.0-32.57), linux-headers-3.13.0-32:amd64 (3.13.0-32.57)
End-Date: 2014-08-25 12:41:22

Start-Date: 2014-08-29 06:42:00
Install: linux-headers-3.13.0-35:amd64 (3.13.0-35.62, automatic), linux-image-extra-3.13.0-35-generic:amd64 (3.13.0-35.62, automatic), linux-image-3.13.0-35-generic:amd64 (3.13.0-35.62, automatic), linux-headers-3.13.0-35-generic:amd64 (3.13.0-35.62, automatic)
Upgrade: linux-headers-generic:amd64 (3.13.0.34.40, 3.13.0.35.42), multiarch-support:amd64 (2.19-0ubuntu6.1, 2.19-0ubuntu6.3), libc-dev-bin:amd64 (2.19-0ubuntu6.1, 2.19-0ubuntu6.3), libc-bin:amd64 (2.19-0ubuntu6.1, 2.19-0ubuntu6.3), libc6:amd64 (2.19-0ubuntu6.1, 2.19-0ubuntu6.3), linux-libc-dev:amd64 (3.13.0-34.60, 3.13.0-35.62), linux-image-generic:amd64 (3.13.0.34.40, 3.13.0.35.42), libc6-dev:amd64 (2.19-0ubuntu6.1, 2.19-0ubuntu6.3), linux-generic:amd64 (3.13.0.34.40, 3.13.0.35.42)
End-Date: 2014-08-29 06:42:46
[/CODE]

Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-35-generic x86_64)
Fog 1.2.0
Non-modifiable DHCP server so using DNS-Masq which worked perfectly when testing earlier in the month.

I can attach my foginstall.log if required.

UPDATE it is still working on a different laptop (it definitely wasn’t working on any machine on Friday so something that I changed has made it work a little better).
I have updated the BIOS on the non-working machine and it is still the same.

Non working machine - Dell Latitude E5420, A14 BIOS

Ok, thanks for the post. It’s fixed now and it was the very last step that did it. A few notes on the instructions above. Like you requested, I did each step one at a time.

[quote=“mecsr, post: 27208, member: 23886”]
[B]Symlink method[/B]

1. delete the current /etc/resolv.conf file with this command “sudo rm /etc/resolv.conf”[/quote]
   /etc/resolv.conf -> This is already a symlink to the master file /run/resolvconf/resolv.conf

[quote=“mecsr, post: 27208, member: 23886”]
2. edit the master resolv.conf file with the command “nano /run/resolvconf/resolv.conf”
The format of the file is nameserver definitions…
For a dns server definition, you use nameserver, you can define more than one, each has its own line
nameserver [I]your.Network’s.DnsServer.Address [/I]
For example, if you wanted the server to use google public dns, you would have one line say
nameserver 8.8.8.8
[/quote]
/run/resolvconf/resolv.conf -> this file is modified automatically on resolvconf service restart

[quote="mecsr, post: 27208, member: 23886
If you are on a enterprise type network that has a domain name you use the search line and the supersede statement
The “search” line syntax -
search [I]your.appended.domainName[/I]

The supersede statement, this is a multiple line statement with the second line indented with a space-
supersede domain-name “[I]your.appended.domainName[/I]”; (Quotes are apart of the syntax)
prepend domain-name-servers [I]your.primary.dnsServer.address[/I];

(in case anyone hasn’t used nano before, to save and close the file, ctrl + x, then y )

3. Create the symlink to the master file with the command “sudo ln -s /run/resolvconf/resolv.conf”

4. Restart the resolvconf service and the dnsmasq service with “sudo service resolvconf restart” and “sudo service dnsmasq restart”
   [I]Note: If the “port=0” line in /etc/dnsmasq.d/ltsp.conf is still commented out, go uncomment it before your restart the dnsmasq[/I] [I]service[/I]

5. Do a quick test with “sudo apt-get update” if it succeeds than hooray! otherwise try the next method.
   [/quote]

This solution didn’t work. The files were automatically modified on service restart.

[quote=“mecsr, post: 27208, member: 23886”]
[B]resolvconf interfaces file[/B]
[I]If the symlink method alone didn’t work, it may be necessary to edit the files specific to each network interface, these instructions assume you only have one ethernet device named eth0, but these steps can easily apply to any additional interfaces.[/I]

1. Edit the eth0 dhclient file with “sudo nano /run/resolvconf/interfaces/eth0.dhclient”
   If you have a domain name, you need a domain line. It is the same as the “search” line in resolv.conf,
   except you domain instead of search. i.e. “domain your.appended.domainName” (without quotes)

The only other lines you need are the nameserver lines which use the same syntax as the resolv.conf file shown above

so just put in your nameserver definitions the same as before
[/quote]

I didn’t have an eth0.dhclient file.

[quote=“mecsr, post: 27208, member: 23886”]
2. Edit the eth0.inet file with “sudo nano /run/resolvconf/interfaces/eth0.inet”
In this file you only need one line defining your primary dns server with a single nameserver line

3. Restart the resolvconf service and the dnsmasq service with “sudo service resolvconf restart” & “sudo service dnsmasq restart”

4. Do a quick test with “sudo apt-get update” if it succeeds than hooray! otherwise try the next method.
   [/quote]

My eth0.inet file already had the correct info in it. I also had an lo.dnsmasq file with one line in it
[CODE]nameserver 127.0.0.1[/CODE]
So I modified this file with the correct details but, once again, on service restart the file reverted to the original values.

[quote=“mecsr, post: 27208, member: 23886”]
[B]resolvconf interface order and base config files[/B]
[I]If the above 2 methods still didn’t do the trick, try editing these 2 more config files. You may try restarting the service after each file to see if you only needed to edit one of them rather than both.[/I]

1. Edit the base file with “sudo nano /etc/resolvconf/resolv.conf.d/base”
   The syntax of this file is the same as the master resolv.conf file[/quote]

I modified the base file with the values and restarted the service but the /etc/resolv.conf did not reflect the changes

[quote=“mecsr, post: 27208, member: 23886”]
2. Edit the interface order with “sudo nano /etc/resolvconf/interface-order”
This file should already have lots of information in it. I edited so that the top two interfaces are
eth0.dhcp
eth*
It is likely that you only need to have eth* at the top, but this is what I have working. Keep all the rest of the interface order
as it is.

3. Restart the resolvconf service and the dnsmasq service with “sudo service resolvconf restart” & “sudo service dnsmasq restart”

4. Do a quick test with “sudo apt-get update” if it succeeds than hooray! otherwise, the problem is something different or the linux distro your using uses the resolvconf service completely differently than ubuntu 14.04 and would require additional research.

I hope this helps. Good luck

Thanks,
-JJ[/quote]

This final step was the one that worked. I only put eth* at the top of the interface-order file and restarted the service. Did a quick ping test… success! Checked the /etc/resolv.conf and it had pulled the details from eth0.inet

So it seems the real problem is the lo.dnsmasq file which takes precedence in the interface-order
[CODE]# interface-order(5)
lo.inet*
lo.dnsmasq
lo.pdnsd
lo.!(pdns|pdns-recursor)
lo
tun*
tap*
hso*
em+([0-9])?(+([0-9]))*
p+([0-9])p+([0-9])?(+([0-9]))*
ath*
eth*
wlan*
ppp*
*
[/CODE]
The above was the original layout.

Thanks for your help JJ. It was an interesting ride and probably wouldn’t have known the flow of these files from day to day usage.

That did indeed work, thanks. If you find your other solution, I would be very pleased to see it

Hi all, I am having trouble with DNS lookups when DNSMASQ is active. Hosts do not resolve for me.

Disabling DNSMASQ allows me to lookup addresses again:
[CODE]service dnsmasq stop[/CODE]
but, of course, it breaks my setup as I don’t have access to the DHCP server.

I followed the iPXE settings in this guide to setup - [url]http://www.fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server[/url]

Any ideas what I might be missing?

Cheers,

del

UPDATE; I got it working.
I copied vmlinuz, initrd.img and filesystem.squashfs from gparted into /var/www/fog/gparted/
and then updated my iPXE menu as follows:

kernel http://${fog-ip}/fog/gparted/vmlinuz
initrd http://${fog-ip}/fog/gparted/initrd.img
imgargs vmlinuz boot=live config union=aufs noswap noprompt vga=788 fetch=http://${fog-ip}/fog/gparted/filesystem.squashfs
boot[/CODE]

All tested and working now.

Could someone do an entry for GParted? The [URL=‘http://www.fogproject.org/wiki/index.php?title=Include_GParted’]Include Gparted[/URL] wiki page is out of date now and I can’t get the ISO to boot properly using the methods above.
I get as far as the GParted grub menu but once I try to boot to gparted, I get pages of
[CODE]modprobe: module unknown not found in modules.dep[/CODE]
followed by a blackscreen.

iPXE menu entry below
[CODE]:gparted
initrd http://${fog-ip}/ISO/gparted-live-0.18.0-2-i486.iso
chain memdisk iso raw ||
goto MENU[/CODE]

I found this which appears to be the same issue (a memdisk issue) but I am not sure how to implement the fix.
[url]http://gparted-forum.surf4.info/viewtopic.php?id=16884[/url]