0.107.30 failed to start #5872
Comments
|
我也是, 我的現象是更新完之後他能正常運行, 但是大陸内的域名都無法解析, Google這些卻沒問題, 我最開始懷疑是dnsmasq出問題了, 排查半天沒發現有什麽問題, 然後重啓了一下ADG發現怎麽開都運行不起來了, 換成0.107.29正常運行解析也都正常, 看更新日志檔也搞不太清楚是何種變更導致的... |
点页面上update后，遇到一样问题，请问怎样回滚到0.107.29？ |
我是openwrt用的luci-app-adguardhome, 如果你和我一樣的話, 在/usr/bin/AdGuardHome下刪掉現存的AdGuardHome文件, 去https://github.com/AdguardTeam/AdGuardHome/releases/tag/v0.107.29下載你對應系統和處理器架構的編譯版本, 將tar.gz解壓后把裏面的AdGuardHome文件移到/usr/bin/AdGuardHome, 記得給執行權限chmod +x /usr/bin/AdGuardHome/AdGuardHome然後重新在openwrt的網頁管理面板重新勾選啓用和重定向保存應用即可 |
我是通过 官方给的这条命令自动安装的，暂时还不清楚怎样回滚到0.107.29 |
你是什麽系統呢? 解題思路都一樣, 本質上是換掉他的core, 你可以用例如htop這樣的命令來檢查adg的可執行文件路徑, 然後cd進去看看目錄結構, 嘗試用舊的替換掉新的 
|
我安装在Openwrt上的。只需替换掉它的AdGuardHome可执行文件吗？别的文件（夹）需要删掉吗？ |
只需要替換可執行文件, 這樣攔截規則和配置文件都不會丟失, 我這樣做沒有問題, 替換爲0.107.29全都恢復正常了 |
谢谢指导！已经成功回滚到0.107.29，一切恢复正常！ |
You can revert to previous version to resolve this issues. |
|
Seems like OpenWrt has a complicated relationship with some socket flags. We'll try to ship a fix soon. |
|
Could any of you please try |
|
@ainar-g v0.107.31 now it's work. |
|
Fri Jun 9 03:53:52 2023 daemon.err AdGuardHome[26506]: |
|
@qpzr, thanks for the logs. That seems like a separate issue that could arise from one of the libraries we use for DNSCrypt. We'll look into it. |
Merge in GO/dnsproxy from 5872-fix-dnscrypt-reset to master Updates AdguardTeam/AdGuardHome#5872. Squashed commit of the following: commit e1cd69e Author: Eugene Burkov <E.Burkov@AdGuard.COM> Date: Fri Jun 9 17:17:27 2023 +0300 upstream: imp docs commit a0b07ac Author: Eugene Burkov <E.Burkov@AdGuard.COM> Date: Fri Jun 9 16:08:51 2023 +0300 upstream: use defer commit 9b16ffe Author: Eugene Burkov <E.Burkov@AdGuard.COM> Date: Fri Jun 9 15:57:57 2023 +0300 upstream: imp code commit aa64e19 Author: Eugene Burkov <E.Burkov@AdGuard.COM> Date: Fri Jun 9 15:55:51 2023 +0300 upstream: imp code commit 477f0cd Author: Eugene Burkov <E.Burkov@AdGuard.COM> Date: Fri Jun 9 14:52:18 2023 +0300 upstream: fix dnscrypt reset
Windows me too |
Merge in DNS/adguard-home from upd-proxy to master Updates #5872. Squashed commit of the following: commit fac8d1c Author: Eugene Burkov <E.Burkov@AdGuard.COM> Date: Fri Jun 9 19:18:35 2023 +0300 all: fix chlog commit 10f64ba Author: Eugene Burkov <E.Burkov@AdGuard.COM> Date: Fri Jun 9 19:14:07 2023 +0300 all: log changes commit 14410c4 Author: Eugene Burkov <E.Burkov@AdGuard.COM> Date: Fri Jun 9 18:48:09 2023 +0300 all: upd proxy
|
@qpzr, could you please check v0.107.32? |
|
|
0.107.32 works fine |
|
Thanks for confirming. We'll close the issue then. |
Prerequisites
I have checked the Wiki and Discussions and found no answer
I have searched other issues and found no duplicates
I want to report a bug and not ask a question
Operating system type
Linux, OpenWrt
CPU architecture
ARMv5
Installation
GitHub releases or script from README
Setup
On a router, DHCP is handled by the router
AdGuard Home version
0.107.30
Description
What did you do?
Regular upgrades
Expected result
Start normally
Actual result
Startup failed
Screenshots (if applicable)
Additional information
0.107.30 failed to boot, demoted back to 0.107.29 normal boot, with two versions of the boot log：
0.107.30：
2023/06/07 22:39:43.937044 [info] AdGuard Home, version v0.107.30
2023/06/07 22:39:44.057230 [info] tls: using default ciphers
2023/06/07 22:39:44.062198 [info] safesearch default: disabled
2023/06/07 22:39:44.078845 [info] Initializing auth module: /tmp/mnt/sda1/asusware.arm/etc/AdGuardHome/data/sessions.db
2023/06/07 22:39:44.105575 [info] auth: initialized. users:1 sessions:5
2023/06/07 22:39:44.105718 [info] web: initializing
2023/06/07 22:39:45.794297 [info] dnsproxy: cache: enabled, size 4096 b
2023/06/07 22:39:45.794378 [info] dnsproxy: max goroutines is set to 300
2023/06/07 22:39:45.795698 [info] AdGuard Home is available at the following addresses:
2023/06/07 22:39:45.798693 [info] go to http://127.0.0.1:3000
2023/06/07 22:39:45.798761 [info] go to http://127.0.1.1:3000
2023/06/07 22:39:45.798800 [info] go to http://[::1]:3000
2023/06/07 22:39:45.798833 [info] go to http://[fe80::2cc3:1aff:fe21:dd15%ifb0]:3000
2023/06/07 22:39:45.798863 [info] go to http://[fe80::f80a:7bff:fedb:1748%ifb1]:3000
2023/06/07 22:39:45.798893 [info] go to http://[fe80::200:ff:fe00:0%fwd0]:3000
2023/06/07 22:39:45.798931 [info] go to http://[fe80::200:ff:fe00:0%fwd1]:3000
2023/06/07 22:39:45.798971 [info] go to http://[fe80::200:ff:fe00:0%agg]:3000
2023/06/07 22:39:45.799005 [info] go to http://[fe80::200:ff:fe00:0%dpsta]:3000
2023/06/07 22:39:45.799035 [info] go to http://[fe80::6adb:54ff:fe43:c207%eth1]:3000
2023/06/07 22:39:45.799067 [info] go to http://[fe80::6adb:54ff:fe43:c20b%eth2]:3000
2023/06/07 22:39:45.799097 [info] go to http://[fe80::6adb:54ff:fe43:c207%vlan1]:3000
2023/06/07 22:39:45.799125 [info] go to http://[fe80::6adb:54ff:fe43:c207%vlan2]:3000
2023/06/07 22:39:45.799153 [info] go to http://192.168.50.1:3000
2023/06/07 22:39:45.799181 [info] go to http://[fe80::6adb:54ff:fe43:c207%br0]:3000
2023/06/07 22:39:45.799209 [info] go to http://211.161.154.190:3000
2023/06/07 22:40:06.228723 [info] dnsproxy: starting dns proxy server
2023/06/07 22:40:06.269296 [info] The server is configured to refuse ANY requests
2023/06/07 22:40:06.269364 [info] dnsproxy: cache: enabled, size 4194304 b
2023/06/07 22:40:06.269461 [info] dnsproxy: max goroutines is set to 300
2023/06/07 22:40:06.421765 [info] dnsproxy: creating udp server socket 0.0.0.0:53
2023/06/07 22:40:06.546840 [fatal] couldn't start forwarding DNS server: starting listeners: listening on udp addr 0.0.0.0:53: listening to udp socket: listen udp 0.0.0.0:53: setting SO_REUSEPORT: protocol not available
0.107.29：
2023/06/07 22:47:23.505701 [info] AdGuard Home, version v0.107.29
2023/06/07 22:47:23.558214 [info] tls: using default ciphers
2023/06/07 22:47:23.562481 [info] safesearch default: disabled
2023/06/07 22:47:23.625630 [info] Initializing auth module: /tmp/mnt/sda1/asusware.arm/etc/AdGuardHome/data/sessions.db
2023/06/07 22:47:23.645181 [info] auth: initialized. users:1 sessions:5
2023/06/07 22:47:23.645277 [info] web: initializing
2023/06/07 22:47:25.378297 [info] dnsproxy: cache: enabled, size 4096 b
2023/06/07 22:47:25.378394 [info] MaxGoroutines is set to 300
2023/06/07 22:47:25.380035 [info] AdGuard Home is available at the following addresses:
2023/06/07 22:47:25.383658 [info] go to http://127.0.0.1:3000
2023/06/07 22:47:25.383790 [info] go to http://127.0.1.1:3000
2023/06/07 22:47:25.383831 [info] go to http://[::1]:3000
2023/06/07 22:47:25.383876 [info] go to http://[fe80::50c5:d4ff:fec1:62e3%ifb0]:3000
2023/06/07 22:47:25.383913 [info] go to http://[fe80::b887:45ff:fec9:7c9d%ifb1]:3000
2023/06/07 22:47:25.383945 [info] go to http://[fe80::200:ff:fe00:0%fwd0]:3000
2023/06/07 22:47:25.383980 [info] go to http://[fe80::200:ff:fe00:0%fwd1]:3000
2023/06/07 22:47:25.384012 [info] go to http://[fe80::200:ff:fe00:0%agg]:3000
2023/06/07 22:47:25.384041 [info] go to http://[fe80::200:ff:fe00:0%dpsta]:3000
2023/06/07 22:47:25.384070 [info] go to http://[fe80::6adb:54ff:fe43:c207%eth1]:3000
2023/06/07 22:47:25.384098 [info] go to http://[fe80::6adb:54ff:fe43:c20b%eth2]:3000
2023/06/07 22:47:25.384128 [info] go to http://[fe80::6adb:54ff:fe43:c207%vlan1]:3000
2023/06/07 22:47:25.384157 [info] go to http://[fe80::6adb:54ff:fe43:c207%vlan2]:3000
2023/06/07 22:47:25.384185 [info] go to http://192.168.50.1:3000
2023/06/07 22:47:25.384214 [info] go to http://[fe80::6adb:54ff:fe43:c207%br0]:3000
2023/06/07 22:47:25.384241 [info] go to http://211.161.154.189:3000
2023/06/07 22:47:44.776124 [info] Starting the DNS proxy server
2023/06/07 22:47:44.776240 [info] The server is configured to refuse ANY requests
2023/06/07 22:47:44.776290 [info] dnsproxy: cache: enabled, size 4194304 b
2023/06/07 22:47:44.776359 [info] MaxGoroutines is set to 300
2023/06/07 22:47:44.776514 [info] Creating the UDP server socket
2023/06/07 22:47:44.776811 [info] Listening to udp://[::]:53
2023/06/07 22:47:44.776881 [info] Creating a TCP server socket
2023/06/07 22:47:44.777038 [info] Listening to tcp://[::]:53
2023/06/07 22:47:44.777347 [info] Entering the UDP listener loop on [::]:53
2023/06/07 22:47:44.777816 [info] Entering the tcp listener loop on [::]:53
2023/06/07 22:47:45.056579 [info] home: language is set to zh-cn
2023/06/07 22:47:45.056661 [info] home: theme is set to auto
2023/06/07 22:47:45.977573 [info] warning: cannot check capability cap_net_bind_service: invalid argument
2023/06/07 22:47:49.542527 [info] warning: cannot check capability cap_net_bind_service: invalid argument
2023/06/07 22:47:49.560247 [info] home: language is set to zh-cn
2023/06/07 22:47:49.560330 [info] home: theme is set to auto
The text was updated successfully, but these errors were encountered: