This article is for trouble shooting on the Linux iPXE server setup via our manual. If you have used a different manual or setup some of the trouble shoot guidance might not be helpful. If you still encounter issues after below steps, email our support team at support@global-emea.com or create a ticket via this support page. In case you've used a different setup, please explain what you've done and/or share that manual.
If the DHCP service does not start and gives the error:
O 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 Wed 2021-06-16 14:53:05 CEST; 59min ago
Docs: man:dhcpd(8)
Process: 1637 ExecStart=/bin/sh -ec CONFIG_FILE=/etc/dhcp/dhcpd.conf; if [ -f /etc/ltsp/dhcpd.conf ]; then CONFIG_FILE=/etc/ltsp/dhcpd.conf; fi;>
Main PID: 1637 (code=exited, status=1/FAILURE)
jun 16 14:53:05 wd-Latitude-E6530 dhcpd[1637]:
jun 16 14:53:05 wd-Latitude-E6530 dhcpd[1637]: If you think you have received this message due to a bug rather
jun 16 14:53:05 wd-Latitude-E6530 dhcpd[1637]: than a configuration issue please read the section on submitting
jun 16 14:53:05 wd-Latitude-E6530 dhcpd[1637]: bugs on either our web page at www.isc.org or in the README file
jun 16 14:53:05 wd-Latitude-E6530 dhcpd[1637]: before submitting a bug. These pages explain the proper
jun 16 14:53:05 wd-Latitude-E6530 dhcpd[1637]: process and the information we find helpful for debugging.
jun 16 14:53:05 wd-Latitude-E6530 dhcpd[1637]:
jun 16 14:53:05 wd-Latitude-E6530 dhcpd[1637]: exiting.
jun 16 14:53:05 wd-Latitude-E6530 systemd[1]: isc-dhcp-server.service: Main process exited, code=exited, status=1/FAILURE
jun 16 14:53:05 wd-Latitude-E6530 systemd[1]: isc-dhcp-server.service: Failed with result 'exit-code'.
Main error line: isc-dhcp-server.service: Failed with result 'exit-code'.
The service must be restarted. The normal one, shown below, might not work;
$ sudo systemctl restart isc-dhcp-server
Therefor we recommend this one, to gain root access first.:
$ sudo su
Then, to get the DHCP service restarted:
$ systemctl restart isc-dhcp-server.serviceType below to see the status:
$ systemctl status isc-dhcp-server.serviceNow the feedback should be green (See below) with active (running).
● isc-dhcp-server.service - ISC DHCP IPv4 server
Loaded: loaded (/lib/systemd/system/isc-dhcp-server.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2021-11-17 13:24:02 GMT; 3s ago
Docs: man:dhcpd(8)
Main PID: 9966 (dhcpd)
Tasks: 4 (limit: 18668)
Memory: 4.4M
CGroup: /system.slice/isc-dhcp-server.service
If it is still not working, some trouble shooting has to be done. Let's first see if you have an IP address shown on the port that is used for DHCP. In this expample we do use eno1 but this might be different for you, examples are enpos31f6, eth1, eth0, eno1, eno2, enp1s0, enp4s0f0. There are many more options.
First type ifconfig and see if the NIC has an IP adrress. See here the example.
eno1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether xx:xx:xx:xx:xx:xx txqueuelen 1000 (Ethernet)
RX packets 569 bytes 136549 (136.5 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1712 bytes 324559 (324.5 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0xec200000-ec220000
Above does not give any IP meaning there is no static IP. So let's force an IP:
$ ifconfig eno1 10.10.10.1
Note: This will force eno1 to use 10.0.10.1 as a static IP, which we need for this setup. If you use a different range, please use that static IP for this server. Also the port name might be different for you
If you now type ifconfig again it should show the IP here:
eno1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 10.10.10.1 netmask 255.0.0.0 broadcast 10.255.255.255
ether xx:xx:xx:xx:xx:xx txqueuelen 1000 (Ethernet)
RX packets 569 bytes 136549 (136.5 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1712 bytes 324559 (324.5 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0xec200000-ec220000
Now restart the services:
netplan apply apt update -y && apt install -y iptables-persistent iptables-save > /etc/iptables/rules.v4 systemctl restart isc-dhcp-server.service systemctl status isc-dhcp-server.service
The outcome of above should result in to below:
● isc-dhcp-server.service - ISC DHCP IPv4 server
Loaded: loaded (/lib/systemd/system/isc-dhcp-server.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2021-11-17 13:24:02 GMT; 3s ago
Docs: man:dhcpd(8)
Main PID: 9966 (dhcpd)
Tasks: 4 (limit: 18668)
Memory: 4.4M
CGroup: /system.slice/isc-dhcp-server.service
In case this is still not working type below and take a picture of the screen.
type: journalctl _PID=[PID_ID] above has 9966 as ID: Main PID: 9966 (dhcpd)
Like:
journalctl _PID=9966
This will show some red text, this will guide you why this is happening. Send this to our support team to be reviewed.
If this article was not helpful and more help is needed please contact us via one of below option.
| Email us | Submit a ticket | Give us a call |
Our official support hours are 8:00 am to 16:30 pm, after those hours emailing us or submitting a ticket would be the best option.
When contacting our support team, please refer to the article you’ve checked and if possible add a picture of the error and add information on the hardware that’s giving the error. Make always sure you’re using the latest version.