hassio-addons / addon-adguard-home

AdGuard Home - Home Assistant Community Add-ons
https://addons.community
MIT License
388 stars 48 forks source link

Adguard not starting #341

Closed alecilo closed 2 years ago

alecilo commented 2 years ago

Problem/Motivation

Adguard fails to start after installation

Expected behavior

Starting

Actual behavior

Adguard not starting, no error in logs, seems like NGINX stuck.

Log here:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/00-banner.sh
-----------------------------------------------------------
 Add-on: AdGuard Home
 Network-wide ads & trackers blocking DNS server
-----------------------------------------------------------
 Add-on version: 4.7.3
 You are running the latest version of this add-on.
 System: Home Assistant OS 8.5  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2022.8.7
 Home Assistant Supervisor: 2022.08.5
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
cont-init: info: /etc/cont-init.d/00-banner.sh exited 0
cont-init: info: running /etc/cont-init.d/01-log-level.sh
cont-init: info: /etc/cont-init.d/01-log-level.sh exited 0
cont-init: info: running /etc/cont-init.d/adguard.sh
cont-init: info: /etc/cont-init.d/adguard.sh exited 0
cont-init: info: running /etc/cont-init.d/discovery.sh
[00:17:39] INFO: Successfully send discovery information to Home Assistant.
cont-init: info: /etc/cont-init.d/discovery.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun adguard (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
s6-rc: info: service legacy-services successfully started
[00:17:40] INFO: Starting AdGuard Home server...
2022/08/31 00:17:40.267838 [info] AdGuard Home, version v0.107.11
2022/08/31 00:17:40.269234 [info] home.upgradeSchema0to1(): called
2022/08/31 00:17:40.269282 [info] deleting /data/adguard/dnsfilter.txt as we don't need it anymore
2022/08/31 00:17:40.269358 [info] home.upgradeSchema1to2(): called
2022/08/31 00:17:40.269376 [info] deleting /data/adguard/Corefile as we don't need it anymore
2022/08/31 00:17:40.269463 [info] home.upgradeSchema2to3(): called
2022/08/31 00:17:40.270932 [info] home.upgradeSchema3to4(): called
2022/08/31 00:17:40.270969 [info] home.upgradeSchema4to5(): called
2022/08/31 00:17:40.270988 [info] home.upgradeSchema5to6(): called
2022/08/31 00:17:40.271000 [info] Upgrade yaml: 6 to 7
2022/08/31 00:17:40.271012 [info] Upgrade yaml: 7 to 8
2022/08/31 00:17:40.271026 [info] Upgrade yaml: 8 to 9
2022/08/31 00:17:40.271122 [info] Upgrade yaml: 9 to 10
2022/08/31 00:17:40.272574 [info] Upgrade yaml: 10 to 11
2022/08/31 00:17:40.273285 [info] Upgrade yaml: 11 to 12
2022/08/31 00:17:40.273314 [info] Upgrade yaml: 12 to 13
2022/08/31 00:17:40.273327 [info] Upgrade yaml: 13 to 14
2022/08/31 00:17:40.311348 [info] Initializing auth module: /data/adguard/data/sessions.db
2022/08/31 00:17:40.317337 [info] auth: initialized.  users:0  sessions:0
2022/08/31 00:17:40.317391 [info] Initialize web module
2022/08/31 00:17:40.328486 [info] AdGuard Home is available at the following addresses:
2022/08/31 00:17:40.328555 [info] Go to http://127.0.0.1:45158
2022/08/31 00:17:40.339811 [info] Starting the DNS proxy server
2022/08/31 00:17:40.339876 [info] Ratelimit is enabled and set to 20 rps
2022/08/31 00:17:40.339898 [info] The server is configured to refuse ANY requests
2022/08/31 00:17:40.339985 [info] DNS cache is enabled
2022/08/31 00:17:40.340067 [info] MaxGoroutines is set to 300
2022/08/31 00:17:40.340160 [info] Creating the UDP server socket
2022/08/31 00:17:40.341136 [info] Listening to udp://127.0.0.1:53
2022/08/31 00:17:40.341167 [info] Creating a TCP server socket
2022/08/31 00:17:40.341619 [info] Listening to tcp://127.0.0.1:53
2022/08/31 00:17:40.341845 [info] Entering the UDP listener loop on 127.0.0.1:53
2022/08/31 00:17:40.342177 [info] Entering the tcp listener loop on 127.0.0.1:53
2022/08/31 00:17:40.725020 [info] saving filter 1 contents to: /data/adguard/data/filters/1.txt
2022/08/31 00:17:40.725407 [info] updated filter 1: 923176 bytes, 47691 rules
2022/08/31 00:17:40.725432 [info] Updated filter #1.  Rules: 0 -> 47691
[00:17:40] INFO: Starting NGinx...

Steps to reproduce

Just did a fresh installation of home assistant for testing purposes and installed the latest Adguard version,

Proposed changes

sinclairpaul commented 2 years ago

Make sure you follow the docs at https://github.com/hassio-addons/addon-adguard-home/blob/main/adguard/DOCS.md#installation especially to do with assigning a static IP

alecilo commented 2 years ago

Hi, problem solved, this was due to an issue with the restore of a previous backup I made. Thanks

JabelsBS commented 1 year ago

I had to restore a previous backup and have the same problem. How did you solve this? @alecilo

alecilo commented 1 year ago

I had to restore a previous backup and have the same problem. How did you solve this? @alecilo

Sorry for the late reply, just do an host shutdown and not just an home assistant reboot