@kevindm82 Lets ensure that isc-dhcp is running.

You can use this command to see if its running in memory
ps aux|grep dhcp
It should responded with something like isc-dhcp-server and some command line switches.

If its not there you can start with systemctl start isc-dhcp-server and check the status if its running with systemctl status isc-dhcp-server And finally ensure that it starts every time with ubuntu startup with systemctl enable isc-dhcp-server

If you changed the IP address of the FOG server after installing the fog program you will have to fix or fog will not image. There are hard coded IP addresses that will need to be fixed.

@dsloan-ethra So just to recap what was done here to adjust Debian 9 (where the referenced article also implies it is an issue for any Debian variant like Ubuntu) for others that might find the thread:

1. Edit /etc/mysql/mysql.conf.d/mysqld.cnf
   vi /etc/mysql/mysql.conf.d/mysqld.cnf
2. Insert the following line in the [mysqld] section
   max_connections = 8000
3. Copy the systemd service descriptor file so you can customize it
   cp /lib/systemd/system/mysql.service /etc/systemd/system/
4. Append the following lines to this file: /etc/systemd/system/mysql.service

LimitNOFILE=infinity
LimitMEMLOCK=infinity

5. Reload systemd processor
   systemctl daemon-reload
6. Reload the mysql service
   systemctl restart mysqld
7. Login to mysql as root and run the following command.
   mysql> show variables like 'max_connections';
8. The response should be something like

+-----------------+-------+
| Variable_name | Value |
+-----------------+-------+
| max_connections | 8000 |
+-----------------+-------+
1 row in set (0.01 sec)

9. Done.

These are not my words, only restated from the accepted solution here that Sebastian found and referenced: https://www.rfc3092.net/2017/06/mysql-max_connections-limited-to-214-on-ubuntu-foo/

what does df -h show you on disk usage?

?? The .fogsettings file is not (really) related to external storage.

The short answer is you can’t do it that way.

The bit longer answer is there are a few rules you are breaking.

1. You can not reshare an nfs mounted share. Meaning if you mount an external NFS device over /images you can not reshare /images out of your fog server, this isn’t allowed. Its an NFS thing not a fog thing. Fog does use the /images share so the target computer can connect to the fog server and retrieve the captured images. \
2. You can only capture images to a master node in each storage group. So this means if you have 3 fog server (1 master node and 2 storage nodes) you can only capture images to the master node in the storage group. The other 2 storage nodes are in read only mode.

Now with that said, there is a way to configure things to do what you want as long as you have a commercial NAS or one that support TFTP, NFS, and FTP services.

@datastream Ah freenas. I just looked at that wiki page. Not sure how/why that will work. Maybe I need to set this up to get a proper tutorial (if its even possible with freenas).

Here is an article with someone doing something similar to what you are doing. There are links in there that may be relevant to you: https://forums.fogproject.org/topic/11252/freenas-ftp-error

Also Wayne put together a pretty detailed install guide here: https://wiki.fogproject.org/wiki/index.php?title=CentOS_7

@sourceminer can you confirm that bg2.png exists in the path I provided? As well as direct copying bg.png to pg3.png in the exact path I provided. There is/was an issue with ubuntu where there was two data paths for fog /var/www/html/fog/service/ipxe and /var/www/fog/service/ipxe

@jcdinpgh Can you get us a clear screen shot of the error you see. The context of the error is almost as important as the error itself.

Also just to be sure this message is coming from iPXE or is it from something you are trying to launch from the iPXE menu?

In regards to the error message it almost sounds like you are passing a uefi kernel to a bios mode computer, but the error snapshot will tell us a bit more of the context.

As for my ltsp.conf that will dynamically switch between uefi and bios kernels based on the pxe booting target computer. That is a solid config if you need one.

@jcdinpgh Your setup here is very similar to a tutorial I created in 2015
ref: https://forums.fogproject.org/topic/6284/booting-mdt-2013-litetouch-with-fog/5

But since then changes in fog has made hosting files under http sometimes problematic because of the http redirection. If you can get uefi to boot then bios should work too.

Also you might want to drop transferring bootmgr.exe since it should be inside your boot.wim file. Wimboot should extract it and launch it.

If you are on 1.4.0 the developers are going to ask you to update to version 1.4.4 to ensure what you are experiencing has not already been resolved.

WOL is tricky to setup.

1. Are all of your computers on the same subnet (vlan) as the FOG server?
2. Do you have any routers between?
3. Is WOL enabled on all computers?
4. Is it just a specific model of computer that won’t WOL?

@sbergeron ok give me a few minutes to come up with a sql query. We need to ensure that the mac address is actually being recorded correctly in the database.

@sbergeron See that is what I was referring to with the multiple interfaces. What is going on is that iPXE (the tool that creates the boot menu) is/only looks at the first two mac addresses in the device.

(correction, it looks at the fist three interfaces) ref: https://github.com/FOGProject/fogproject/blob/master/src/ipxe/src/ipxescript

I’m still not sure how its getting to the iPXE menu at this point, because if all of the first 3 interfaces do not get an IP address then it should error out.

as for the sql statement, I don’t think we need it at this point but I’ll document it here just in case.

Select h.hostName, m.hmMAC, length(m.hmMAC) from hosts h left join hostMAC m on h.hostID=m.hmHostID where h.hostName='<name of host>';

@sbergeron Well I think I know why its messing up, but we may need to get a developer in the mix here to fix it. It can be fixed its just going to take some noodling.

[for developers] @Developers
In the ipxe script that is in the ipxe boot kernel it tries net0-net2 to get a dhcp address failing that it ties dhcp all, which is where its probably getting an IP address on the net3-net7 interfaces. Then it chains to default.ipxe

In default.ipxe it executes this ipxe script:

#!ipxe
cpuid --ext 29 && set arch x86_64 || set arch i386
params
param mac0 ${net0/mac}
param arch ${arch}
param platform ${platform}
param product ${product}
param manufacturer ${product}
param ipxever ${version}
param filename ${filename}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:bootme
chain http://<fog_server_ip>/fog/service/ipxe/boot.php##params

Where again it only looks at net0-net2. I think to fix this we need to make mac0 be the interface that is actually getting the IP address and not just the first network interface detected. I realize this is a rare case where we have a device that has more than 3 mac addresses being returned. But if it happened once, it will happen again (IMO).

get rid of the extra “$” before 192 in your fog menu

second issue is your path to the ISO image.

/var/www/fog/service/ipxe/DLCD/DLC.iso is the linux file path since you are trying to access that iso over http you need this path:

http://192.168.25.66/fog/service/ipxe/DLCD/DLC.iso

@tfoote01 The fix was to disable the rogue dhcp server that was giving conflicting information to the target computer ( in Tyler’s case )

If you are having a similar issue, please open a new thread with your specific details. We like to keep specific conditions to their own threads if possible.

@greg-plamondon Whelp, that’s why I’m not a programmer

Here is what needs to be fixed, sorry.

This is the bad line

if [ $ustat -eq 0 && $cstat -eq 0 ]; then

This is what it should have been

if [[ $ustat -eq 0 && $cstat -eq 0 ]]; then

Awe, crud and then the next errors you will find are a few lines down.

		if [ $ustat -eq 1 ]; then
			echo "## DHCP failed on $iface ##"
		fi
		if [ $cstat -eq 1 ]; then
			echo "## The Master FOG server failed responded to our query ##"
		fi

need to have the brackets too

		if [[ $ustat -eq 1 ]]; then
			echo "## DHCP failed on $iface ##"
		fi
		if [[ $cstat -eq 1 ]]; then
			echo "## The Master FOG server failed responded to our query ##"
		fi

It looks like the instructions from the wiki came from here: https://forums.fogproject.org/topic/6162/firewall-configuration

If you need to leave firewalld running then you will need to enable exceptions to the block all policy. I know that you have that script, but my guess is that you don’t have samba installed and that is why its failing.

This script

for service in http https tftp ftp mysql nfs mountd rpc-bind proxy-dhcp samba; do firewall-cmd --permanent --zone=public --add-service=$service; done
systemctl restart firewalld.service

can be rewritten as:

firewall-cmd --permanent --zone=public --add-service=http
firewall-cmd --permanent --zone=public --add-service=https
firewall-cmd --permanent --zone=public --add-service=tftp
firewall-cmd --permanent --zone=public --add-service=mysql
firewall-cmd --permanent --zone=public --add-service=nfs
firewall-cmd --permanent --zone=public --add-service=mountd
firewall-cmd --permanent --zone=public --add-service=rpc-bind
firewall-cmd --permanent --zone=public --add-service=proxy-dhcp
firewall-cmd --permanent --zone=public --add-service=samba

Again I think its the samba that is causing the query to fail

someone mess with the linux service account (user) called fog? That’s not the default web admin with the same name. What I’m talking about is the linux user called fog. That account is (should be) managed by FOG and not used for system maintenance.

Well I see a conflict here. I see you have isc-dhcp server loaded in your configuration AND you are using dnsmasq. Which one do you want to use?

In regards to dnsmasq first confirm you are running dnsmasq version 2.76 or newer by keying this into the fog server linux command prompt. dnsmasq -v Hopefully the response looks like this:

Dnsmasq version 2.76  Copyright (c) 2000-2016 Simon Kelley
Compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify

If so then please use my ltsp.conf, completely replacing yours.

# Don't function as a DNS server:
port=0

# Log lots of extra information about DHCP transactions.
log-dhcp

# Set the root directory for files available via FTP.
tftp-root=/tftpboot

# The boot filename, Server name, Server Ip Address
dhcp-boot=undionly.kpxe,,<fog_server_IP>

# Disable re-use of the DHCP servername and filename fields as extra
# option space. That's to avoid confusing some old or broken DHCP clients.
dhcp-no-override

# inspect the vendor class string and match the text to set the tag
dhcp-vendorclass=BIOS,PXEClient:Arch:00000
dhcp-vendorclass=UEFI32,PXEClient:Arch:00006
dhcp-vendorclass=UEFI,PXEClient:Arch:00007
dhcp-vendorclass=UEFI64,PXEClient:Arch:00009

# Set the boot file name based on the matching tag from the vendor class (above)
dhcp-boot=net:UEFI32,i386-efi/ipxe.efi,,<fog_server_IP>
dhcp-boot=net:UEFI,ipxe.efi,,<fog_server_IP>
dhcp-boot=net:UEFI64,ipxe.efi,,<fog_server_IP>

# PXE menu.  The first part is the text displayed to the user.  The second is the timeout, in seconds.
pxe-prompt="Booting FOG Client", 1

# The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
# Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
# This option is first and will be the default if there is no input from the user.
pxe-service=X86PC, "Boot to FOG", undionly.kpxe
pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe.efi
pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe.efi

dhcp-range=<fog_server_ip>,proxy

Don’t forget to replace the <fog_server_ip> tags with the IP address of your fog server.

Ref: https://forums.fogproject.org/topic/8725/compiling-dnsmasq-2-76-if-you-need-uefi-support/5

Now for the isc-dhcp server. You need to decide what really will be your dhcp server for the subnet where the fog server is. It can be the fog server if you are imaging on an isolated network, or it can be your building dhcp server if you want to image using your existing infrastructure.

If you have an isolated imaging network then you can use isc-dhcp server for everything, dnsmasq is not required and will actually confuse things. If you want to image on your current production network and your production network dhcp server isn’t capable of sending out the pxe boot options, then you can use dnsmasq in concert with your existing dhcp server.

You just need to pick a path and we can help you get there.