DHCP Service Issue
-
Server
- FOG Version: 1.4.4
- OS: Ubuntu 16.04 LTS
Client
- Service Version:
- OS:
Description
I have just installed FOG on a clean install of Ubuntu. Upon restarting Ubuntu, I noticed that my DHCP was not working. Based on suggestions previously given to me on the forum, I performed a few troubleshooting steps.
First, I entered the following into the terminal:
sudo systemctl status isc-dhcp-server.service
and received the following result:
isc-dhcp-server.service - ISC DHCP IPv4 server Loaded: loaded (/lib/systemd/system/isc-dhcp-server.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2017-09-05 09:57:22 EDT; 1min 43s ago Docs: man:dhcpd(8) Process: 2087 ExecStart=/bin/sh -ec CONFIG_FILE=/etc/dhcp/dhcpd.conf; if [ -f /etc/ltsp/dhcpd.conf ]; then CONFIG_FILE=/etc/ltsp/dhcpd.con Main PID: 2087 (code=exited, status=1/FAILURE) Sep 05 09:57:22 threeriversfog-laptop sh[2087]: Not configured to listen on any interfaces! Sep 05 09:57:22 threeriversfog-laptop sh[2087]: If you think you have received this message due to a bug rather Sep 05 09:57:22 threeriversfog-laptop sh[2087]: than a configuration issue please read the section on submitting Sep 05 09:57:22 threeriversfog-laptop sh[2087]: bugs on either our web page at www.isc.org or in the README file Sep 05 09:57:22 threeriversfog-laptop sh[2087]: before submitting a bug. These pages explain the proper Sep 05 09:57:22 threeriversfog-laptop sh[2087]: process and the information we find helpful for debugging.. Sep 05 09:57:22 threeriversfog-laptop sh[2087]: exiting. Sep 05 09:57:22 threeriversfog-laptop systemd[1]: isc-dhcp-server.service: Main process exited, code=exited, status=1/FAILURE Sep 05 09:57:22 threeriversfog-laptop systemd[1]: isc-dhcp-server.service: Unit entered failed state. Sep 05 09:57:22 threeriversfog-laptop systemd[1]: isc-dhcp-server.service: Failed with result 'exit-code'.
I also entered this command into the terminal:
sudo ip a s
which returned the following:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 70:e2:4c:68:0e:ca brd ff:ff:ff:ff:ff:ff
Any ideas about what could be going wrong? Thanks in advance!
-
Please review your isc-dhcp server configuration file. I’m suspecting that its not set. Refer to this example for the proper settings: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Example_1
-
@mikec96 There is no IP address configured on the interface
enp2s0
?? What do you see when runningip link
andifconfig -a
? -
@george1421 Is the isc-dhcp server configuration file separate from the dhcpd.conf file? My dhcpd.conf file does not seem to have anything relating to the isc-dhcp section. Below is a copy of the file:
# DHCP Server Configuration file\n#see /usr/share/doc/dhcp*/dhcpd.conf.sample # This file was created by FOG #Definition of PXE-specific options # Code 1: Multicast IP Address of bootfile # Code 2: UDP Port that client should monitor for MTFTP Responses # Code 3: UDP Port that MTFTP servers are using to listen for MTFTP requests # Code 4: Number of seconds a client must listen for activity before trying # to start a new MTFTP transfer # Code 5: Number of seconds a client must listen before trying to restart # a MTFTP transfer option space PXE; option PXE.mtftp-ip code 1 = ip-address; option PXE.mtftp-cport code 2 = unsigned integer 16; option PXE.mtftp-sport code 3 = unsigned integer 16; option PXE.mtftp-tmout code 4 = unsigned integer 8; option PXE.mtftp-delay code 5 = unsigned integer 8; option arch code 93 = unsigned integer 16; use-host-decl-names on; ddns-update-style interim; ignore client-updates; # Specify subnet of ether device you do NOT want service. # For systems with two or more ethernet devices. # subnet 136.165.0.0 netmask 255.255.0.0 {} subnet 192.168.1.0 netmask 255.255.255.0{ option subnet-mask 255.255.255.0; range dynamic-bootp 192.168.1.10 192.168.1.254; default-lease-time 21600; max-lease-time 43200; #option routers 0.0.0.0 #option routers 0.0.0.0 next-server 192.168.1.1; class "Legacy" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000"; filename "undionly.kkpxe"; } class "UEFI-32-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002"; filename "i386-efi/ipxe.efi"; } class "UEFI-32-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006"; filename "i386-efi/ipxe.efi"; } class "UEFI-64-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007"; filename "ipxe.efi"; } class "UEFI-64-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00008"; filename "ipxe.efi"; } class "UEFI-64-3" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00009"; filename "ipxe.efi"; } class "SURFACE-PRO-4" { match if substring(option vendor-class-identifier, 0, 32) = "PXEClient:Arch:00007:UNDI:003016"; filename "ipxe7156.efi"; } class "Apple-Intel-Netboot" { match if substring(option vendor-class-identifier, 0, 14) = "AAPLBSDPC/i386"; option dhcp-parameter-request-list 1,3,17,43,60; if (option dhcp-message-type = 8) { option vendor-class-identifier "AAPLBSDPC"; if (substring(option vendor-encapsulated-options, 0, 3) = 01:01:01) { # BSDP List option vendor-encapsulated-options 01:01:01:04:02:80:00:07:04:81:00:05:2a:09:0D:81:00:05:2a:08:69:50:58:45:2d:46:4f:47; filename "ipxe.efi"; } } } }
-
@Sebastian-Roth Apparently not, even though I specified 192.168.1.1 in the installation. I installed FOG while connected to the internet, then disconnected from the internet for use in an isolated network.
Here is the
ip link
result:1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether 70:e2:4c:68:0e:ca brd ff:ff:ff:ff:ff:ff
And here is the
ifconfig -a
result:enp2s0 Link encap:Ethernet HWaddr 70:e2:4c:68:0e:ca UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:1031 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:213387 (213.3 KB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:18542 errors:0 dropped:0 overruns:0 frame:0 TX packets:18542 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1371382 (1.3 MB) TX bytes:1371382 (1.3 MB)
-
@mikec96 you need to get a static IP address defined for your fog server. That is the first part of the issue. Your dhcp server settings appear correct, so that isn’t the problem.
-
@george1421 Thank you very much for your help! This might sound like a stupid question, but would I need to do that within Ubuntu’s “Network Connections” tool, or is that something I would need to set within FOG during installation or through the FOG web portal?
-
@mikec96 first step is the network connection tool. You need to make linux happy first then rerun the fog installer to get fog realigned with the new IP address.
-
@george1421 I just set the static IP, and everything works beautifully now! I tested connecting another machine and performing a PXE boot as well. Thanks for your help!
-
@mikec96 Case closed now?
-
@george1421 Yes, I’m all set. Am I able to mark the post as solved, or do I not have that ability?