DHCP Server not run at first start

[TooYoungTooSimp]

Prerequisites

Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.

• I am running the latest version
• I checked the documentation and found no answer
• I checked to make sure that this issue has not already been filed

Issue Details

• Version of AdGuard Home server:
  • 0.104.1
• How did you setup DNS configuration:
  • System
• If it's a router or IoT, please write device model:
• Operating system and version:
  • Archlinux

Expected Behavior

dhcp listen at :67 after boot

Actual Behavior

dhcp doesn't listen 67. Unless I restart adguardhome

Screenshots

Screenshot:

Additional Information

I think maybe it's because it can not bind to specific nic at very early time.
So if there's a solution to let adguard home waiting the nic goes up to bind, it should be solved.

[ameshkov]

The problem is that we cannot solve this on our own as it's not caused by us.

AdGuard Home needs to be started when the network is available, and this is specified in the service configuration.

The question is why in your case the order is wrong.

[TooYoungTooSimp]

I've rechecked the boot sequence.


Seems agh boots AFTER nic link up.(I've set After=basic.target in agh .service file)
So in conclusion, I believe my order is correct.

[ameshkov]

@TooYoungTooSimp I guess the temporary solution would be to postpone the service startup so that the iface was actually initialized.

@ainar-g this is not the first time we're facing this issue. We could implement something simple, like waiting a couple more seconds if the interface is not found on the DHCP server startup.

[TooYoungTooSimp]

I added a ExecStartPre=sleep 3, as a temporary solution. It does work now. Thanks for your kindly advice.

[nhmarujo]

I think I'm facing the same issue. When I boot the system, the DHCP Server doesn't work properly. Devices are able to connect to the network, but hang obtaining an IP address.

If I restart the service (sudo service AdGuardHome restart) then everything starts working normally.

I'm running AdGuardHome on the following setup:

• RPi 1 Model B
• Raspbian GNU/Linux 10 (buster)
• AdguardHome v0.104.1

I have checked the service configuration file (/etc/systemd/system/AdGuardHome.service) and I can see the proper configuration to wait for the network: After=syslog.target network-online.target

I also tried to add the instruction ExecStartPre=sleep 3, like suggested by @TooYoungTooSimp as a workaround, but it doesn't seem to solve the issue (I still need to restart AdGuardHome after each boot).

[TooYoungTooSimp]

I think I'm facing the same issue. When I boot the system, the DHCP Server doesn't work properly. Devices are able to connect to the network, but hang obtaining an IP address.

If I restart the service (sudo service AdGuardHome restart) then everything starts working normally.

I'm running AdGuardHome on the following setup:

• RPi 1 Model B
• Raspbian GNU/Linux 10 (buster)
• AdguardHome v0.104.1

I have checked the service configuration file (/etc/systemd/system/AdGuardHome.service) and I can see the proper configuration to wait for the network: After=syslog.target network-online.target

I also tried to add the instruction ExecStartPre=sleep 3, like suggested by @TooYoungTooSimp as a workaround, but it doesn't seem to solve the issue (I still need to restart AdGuardHome after each boot).

well, you should type the full path of sleep, like /usr/bin/sleep (use which sleep to figure out). Maybe you could give it another try.

[nhmarujo]

Actually no, just like that was fine. I just had to increase the sleep a bit in order to make it work.

Here is the service definition (/etc/systemd/system/AdGuardHome.service):

[Unit]
Description=AdGuard Home: Network-level blocker
ConditionFileIsExecutable=/home/pi/AdGuardHome/AdGuardHome
After=syslog.target network-online.target

[Service]
StartLimitInterval=5
StartLimitBurst=10
ExecStartPre=sleep 5
ExecStart=/home/pi/AdGuardHome/AdGuardHome "-s" "run"

WorkingDirectory=/home/pi/AdGuardHome

StandardOutput=file:/var/log/AdGuardHome.out
StandardError=file:/var/log/AdGuardHome.err
Restart=always
RestartSec=10
EnvironmentFile=-/etc/sysconfig/AdGuardHome

[Install]
WantedBy=multi-user.target

If I try to put the full path it actually fail to start.

Right now, I got it booting up fine with this. My issue now is that the DHCP server stops working sometimes and I need to restart the service 😞

[ainar-g]

@TooYoungTooSimp, thanks for your report! Can you set verbose: true in your config and post the log (preferably in text, but a screenshot is fine too) of AGH starting up? Thanks again!

[TooYoungTooSimp]

log.txt
@ainar-g Here's my verbose log. Hope it is helpful for you!

[TooYoungTooSimp]

I can see a line likes not finding ip address of interface ens34, my nics are managed by systemd-networkd and have static ip configuration. Is there's a way just bind on specific interface regardless it's ipaddr (a whimsical suggestion)?

[ainar-g]

@TooYoungTooSimp, thanks for the logs, they're very helpful! We need to know the IP address of the interface we're binding to, because that's the address that we send to the DHCP clients as the address of the DNS server that they should use. We're currently thinking of ways to somehow wait for the interface to get an IP.