AdGuardHome [RELEASE] Asuswrt-Merlin-AdGuardHome-Installer (AMAGHI)
- Thread starter SomeWhereOverTheRainBow
- Start date
SomeWhereOverTheRainBow
Part of the Furniture
Could be you need to exit amtm and come back in. I am not sure if it is amtm, but I am unable to produce the same error.
TCoreX
Regular Contributor
if I go in and out and start the router even with the te version is still there :/
SomeWhereOverTheRainBow
Part of the Furniture
I think it has to do with the update not directly hitting their release channel servers yet. I think it only gets update nightly and they just pushed that update.
SomeWhereOverTheRainBow
Part of the Furniture
That is the flaw in the design of including beta and edge. I need to fill @thelonelycoder In on how to parse my .config file to see if it is using edge or beta so it won't check for the version on those builds.
look at my other message, should be resolved. It appears to have been a bad cronjob. BTW, for those who happen to be victums of one of my mishaps. The installer has a very good needed backup function, that will restore everything. if any of you decide to ever make a backup before deciding to uninstall.
did a clean re-install again, it was working fine for couple of hours I guess. Just checked now and its' down (Internet works though)
are there any other logs we can check? BTW I enabled all of the block lists in AdGuardHome dashboard, except for location-based, may be this has something to do with crashes, may be it cannot handle multiple block lists?
here is the system log, not sure when it stopped
Code:
Jan 25 13:58:39 AdGuardHome[8545]: 2022/01/25 13:58:39.986581 [info] Listening to udp://[::]:53
Jan 25 13:58:39 AdGuardHome[8545]: 2022/01/25 13:58:39.986703 [info] Creating a TCP server socket
Jan 25 13:58:39 AdGuardHome[8545]: 2022/01/25 13:58:39.986977 [info] Listening to tcp://[::]:53
Jan 25 13:58:39 AdGuardHome[8545]: 2022/01/25 13:58:39.987247 [info] Entering the UDP listener loop on [::]:53
Jan 25 13:58:39 AdGuardHome[8545]: 2022/01/25 13:58:39.987658 [info] Entering the tcp listener loop on [::]:53
Jan 25 13:58:43 AdGuardHome[8545]: 2022/01/25 13:58:43.944036 [info] wrong upstream format: bad ipport address "[]:553": bad ip address ""
Jan 25 13:58:56 AdGuardHome[8545]: 2022/01/25 13:58:56.447901 [info] wrong upstream format: bad ipport address "[]:553": bad ip address ""
Jan 25 13:59:08 AdGuardHome[8545]: 2022/01/25 13:59:08.530930 [info] wrong upstream format: bad ipport address "[]:553": bad ip address ""
Jan 25 13:59:34 AdGuardHome[8545]: 2022/01/25 13:59:34.337721 [info] Start reconfiguring the server
Jan 25 13:59:34 AdGuardHome[8545]: 2022/01/25 13:59:34.337871 [info] Stopping the DNS proxy server
Jan 25 13:59:34 AdGuardHome[8545]: 2022/01/25 13:59:34.338180 [info] Stopped the DNS proxy server
Jan 25 13:59:34 AdGuardHome[8545]: 2022/01/25 13:59:34.445774 [info] Starting the DNS proxy server
Jan 25 13:59:34 AdGuardHome[8545]: 2022/01/25 13:59:34.445921 [info] Ratelimit is enabled and set to 20 rps
Jan 25 13:59:34 AdGuardHome[8545]: 2022/01/25 13:59:34.445993 [info] The server is configured to refuse ANY requests
Jan 25 13:59:34 AdGuardHome[8545]: 2022/01/25 13:59:34.446058 [info] DNS cache is enabled
Jan 25 13:59:34 AdGuardHome[8545]: 2022/01/25 13:59:34.446126 [info] MaxGoroutines is set to 300
Jan 25 13:59:34 AdGuardHome[8545]: 2022/01/25 13:59:34.446216 [info] Creating the UDP server socket
Jan 25 13:59:34 AdGuardHome[8545]: 2022/01/25 13:59:34.446514 [info] Listening to udp://[::]:53
Jan 25 13:59:34 AdGuardHome[8545]: 2022/01/25 13:59:34.446646 [info] Creating a TCP server socket
Jan 25 13:59:34 AdGuardHome[8545]: 2022/01/25 13:59:34.446901 [info] Listening to tcp://[::]:53
Jan 25 13:59:34 AdGuardHome[8545]: 2022/01/25 13:59:34.447202 [info] Entering the UDP listener loop on [::]:53
Jan 25 13:59:34 AdGuardHome[8545]: 2022/01/25 13:59:34.447682 [info] Entering the tcp listener loop on [::]:53
Jan 25 13:59:59 AdGuardHome[8545]: 2022/01/25 13:59:59.665062 [info] saving filter 2 contents to: /tmp/mnt/sdb1/entware/etc/AdGuardHome/data/filters/2.txt
Jan 25 13:59:59 AdGuardHome[8545]: 2022/01/25 13:59:59.665909 [info] updated filter 2: 264722 bytes, 7069 rules
Jan 25 13:59:59 AdGuardHome[8545]: 2022/01/25 13:59:59.666305 [info] Updated filter #2. Rules: 0 -> 7069
Jan 25 18:00:00 S61AdGuardHome[10587]: AdGuardHome found alive. Completing checks.
Jan 25 14:00:57 AdGuardHome[8545]: 2022/01/25 14:00:57.091928 [info] saving filter 1643118891 contents to: /tmp/mnt/sdb1/entware/etc/AdGuardHome/data/filters/1643118891.txt
Jan 25 14:00:57 AdGuardHome[8545]: 2022/01/25 14:00:57.093217 [info] updated filter 1643118891: 295106 bytes, 10357 rules
Jan 25 14:01:03 AdGuardHome[8545]: 2022/01/25 14:01:03.719265 [info] saving filter 1643118892 contents to: /tmp/mnt/sdb1/entware/etc/AdGuardHome/data/filters/1643118892.txt
Jan 25 14:01:03 AdGuardHome[8545]: 2022/01/25 14:01:03.719607 [info] updated filter 1643118892: 5758 bytes, 11 rules
Jan 25 14:01:05 AdGuardHome[8545]: 2022/01/25 14:01:05.118897 [info] saving filter 1643118893 contents to: /tmp/mnt/sdb1/entware/etc/AdGuardHome/data/filters/1643118893.txt
Jan 25 14:01:05 AdGuardHome[8545]: 2022/01/25 14:01:05.120139 [info] updated filter 1643118893: 1023400 bytes, 52087 rules
Jan 25 14:01:12 AdGuardHome[8545]: 2022/01/25 14:01:12.373516 [info] saving filter 1643118894 contents to: /tmp/mnt/sdb1/entware/etc/AdGuardHome/data/filters/1643118894.txt
Jan 25 14:01:12 AdGuardHome[8545]: 2022/01/25 14:01:12.374344 [info] updated filter 1643118894: 10607 bytes, 154 rules
Jan 25 14:01:19 AdGuardHome[8545]: 2022/01/25 14:01:19.479179 [info] saving filter 1643118895 contents to: /tmp/mnt/sdb1/entware/etc/AdGuardHome/data/filters/1643118895.txt
Jan 25 14:01:19 AdGuardHome[8545]: 2022/01/25 14:01:19.479618 [info] updated filter 1643118895: 72311 bytes, 3680 rules
Jan 25 14:01:29 AdGuardHome[8545]: 2022/01/25 14:01:29.876118 [info] saving filter 1643118896 contents to: /tmp/mnt/sdb1/entware/etc/AdGuardHome/data/filters/1643118896.txt
Jan 25 14:01:29 AdGuardHome[8545]: 2022/01/25 14:01:29.877366 [info] updated filter 1643118896: 189935 bytes, 6740 rules
Jan 25 14:01:30 AdGuardHome[8545]: 2022/01/25 14:01:30.261048 [info] saving filter 1643118897 contents to: /tmp/mnt/sdb1/entware/etc/AdGuardHome/data/filters/1643118897.txt
Jan 25 14:01:30 AdGuardHome[8545]: 2022/01/25 14:01:30.261833 [info] updated filter 1643118897: 18590 bytes, 696 rules
Jan 25 14:01:30 AdGuardHome[8545]: 2022/01/25 14:01:30.610744 [info] saving filter 1643118898 contents to: /tmp/mnt/sdb1/entware/etc/AdGuardHome/data/filters/1643118898.txt
Jan 25 14:01:30 AdGuardHome[8545]: 2022/01/25 14:01:30.611118 [info] updated filter 1643118898: 8299 bytes, 419 rules
Jan 25 14:01:31 AdGuardHome[8545]: 2022/01/25 14:01:31.063662 [info] saving filter 1643118899 contents to: /tmp/mnt/sdb1/entware/etc/AdGuardHome/data/filters/1643118899.txt
Jan 25 14:01:31 AdGuardHome[8545]: 2022/01/25 14:01:31.064901 [info] updated filter 1643118899: 368556 bytes, 13822 rules
Jan 25 14:01:32 AdGuardHome[8545]: 2022/01/25 14:01:32.151762 [info] saving filter 1643118900 contents to: /tmp/mnt/sdb1/entware/etc/AdGuardHome/data/filters/1643118900.txt
Jan 25 14:01:32 AdGuardHome[8545]: 2022/01/25 14:01:32.152467 [info] updated filter 1643118900: 98678 bytes, 5402 rules
Jan 25 18:15:09 syslog: wlceventd_proc_event(508): eth1: Disassoc 5C:49:7D:8F:08:79, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jan 25 18:15:09 syslog: wlceventd_proc_event(491): eth1: Deauth_ind 5C:49:7D:8F:08:79, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Jan 25 18:15:35 syslog: wlceventd_proc_event(527): eth1: Auth 5C:49:7D:8F:08:79, status: Successful (0), rssi:0
Jan 25 18:15:35 syslog: wlceventd_proc_event(556): eth1: Assoc 5C:49:7D:8F:08:79, status: Successful (0), rssi:0
Jan 25 14:17:08 AdGuardHome[13004]: 2022/01/25 14:17:08.780378 [info] AdGuard Home, version v0.107.3
Jan 25 14:17:08 AdGuardHome[13004]: 2022/01/25 14:17:08.780799 [info] AdGuard Home is running as a service
Jan 25 14:17:08 AdGuardHome[13004]: 2022/01/25 14:17:08.820694 [info] Initializing auth module: /tmp/mnt/sdb1/entware/etc/AdGuardHome/data/sessions.db
Jan 25 14:17:08 AdGuardHome[13004]: 2022/01/25 14:17:08.826142 [info] auth: initialized. users:1 sessions:1
Jan 25 14:17:08 AdGuardHome[13004]: 2022/01/25 14:17:08.826506 [info] Initialize web module
Jan 25 14:17:09 AdGuardHome[13004]: 2022/01/25 14:17:09.276106 [info] AdGuard Home is available at the following addresses:
Jan 25 14:17:09 AdGuardHome[13004]: 2022/01/25 14:17:09.278840 [info] Go to http://127.0.0.1:14711
Jan 25 14:17:09 AdGuardHome[13004]: 2022/01/25 14:17:09.279106 [info] Go to http://127.0.1.1:14711
Jan 25 14:17:09 AdGuardHome[13004]: 2022/01/25 14:17:09.279268 [info] Go to http://192.168.1.1:14711
Jan 25 14:17:09 AdGuardHome[13004]: 2022/01/25 14:17:09.279431 [info] Go to http://5.193.162.86:14711
Jan 25 18:17:10 rc_service: service 13025:notify_rc restart_dnsmasq
Jan 25 18:17:10 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Jan 25 18:17:11 USER: Started AdGuardHome from .
Jan 25 14:17:16 AdGuardHome[13004]: 2022/01/25 14:17:16.725703 [info] Starting the DNS proxy server
Jan 25 14:17:16 AdGuardHome[13004]: 2022/01/25 14:17:16.726230 [info] Ratelimit is enabled and set to 20 rps
Jan 25 14:17:16 AdGuardHome[13004]: 2022/01/25 14:17:16.726821 [info] The server is configured to refuse ANY requests
Jan 25 14:17:16 AdGuardHome[13004]: 2022/01/25 14:17:16.727067 [info] DNS cache is enabled
Jan 25 14:17:16 AdGuardHome[13004]: 2022/01/25 14:17:16.727239 [info] MaxGoroutines is set to 300
Jan 25 14:17:16 AdGuardHome[13004]: 2022/01/25 14:17:16.727402 [info] Creating the UDP server socket
Jan 25 14:17:16 AdGuardHome[13004]: 2022/01/25 14:17:16.749497 [info] Listening to udp://[::]:53
Jan 25 14:17:16 AdGuardHome[13004]: 2022/01/25 14:17:16.749654 [info] Creating a TCP server socket
Jan 25 14:17:16 AdGuardHome[13004]: 2022/01/25 14:17:16.749893 [info] Listening to tcp://[::]:53
Jan 25 14:17:16 AdGuardHome[13004]: 2022/01/25 14:17:16.790015 [info] Entering the UDP listener loop on [::]:53
Jan 25 14:17:16 AdGuardHome[13004]: 2022/01/25 14:17:16.790706 [info] Entering the tcp listener loop on [::]:53
Jan 25 20:15:30 syslog: wlceventd_proc_event(508): eth1: Disassoc 6C:70:9F:67:75:A8, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:-69
Last edited:
SomeWhereOverTheRainBow
Part of the Furniture
I pushed an update recently that changes the nslookup check have you downloaded that patch? If not, you may need to do so.
SomeWhereOverTheRainBow
Part of the Furniture
It appears its not actually a bug, apparently AdGuardHome on most linux setup reports to system log using UTC time. The time is correct, and the date is correct. AdGuardHome only reports using the UTC though. This may have to be feature request someone puts in for.
Network Time Security support · Issue #2267 · AdguardTeam/AdGuardHome
Prerequisites 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 Problem Description Network Time Prot...
github.com
SomeWhereOverTheRainBow
Part of the Furniture
From what I can tell, it can handle a reasonable amount of blocklist. make sure you also have a swap file of at least 2gb. I was easily hitting 512mb on my swap when I pushed the block list beyond the max. I had more than a million domains (actually a couple of million). Even then, I was still able to load web pages.
I am seeing some concerning messages inside you log
Code:
Jan 25 13:58:43 AdGuardHome[8545]: 2022/01/25 13:58:43.944036 [info] wrong upstream format: bad ipport address "[]:553": bad ip address ""
Jan 25 13:58:56 AdGuardHome[8545]: 2022/01/25 13:58:56.447901 [info] wrong upstream format: bad ipport address "[]:553": bad ip address ""
Jan 25 13:59:08 AdGuardHome[8545]: 2022/01/25 13:59:08.530930 [info] wrong upstream format: bad ipport address "[]:553": bad ip address ""
Jan 25 13:59:34 AdGuardHome[8545]: 2022/01/25 13:59:34.337721 [info] Start reconfiguring the serverthat may indicate your dns configuration on the upstream settings is failing.
One issue I faced is after every reboot, AGH GUI top clients cannot resolve LAN IP to client hostname. After manually restart AGH, it can then show the local hostname correctly. Now I added restart in post-mount, and the top clients part is display correctly after every reboot. Not sure if the services started too early or something else that started afterwards causing this. Somehow a restart in a later startup process seems to solve it for me.
Also, every time I start/restart AGH, there are syslog for every hosts [error] hosts container. In GUI Settings -> Client settings, I can see local host name source rDNS. Only 192.168.1.1 and 127.0.0.1 source is etc/hosts
Also, every time I start/restart AGH, there are syslog for every hosts [error] hosts container. In GUI Settings -> Client settings, I can see local host name source rDNS. Only 192.168.1.1 and 127.0.0.1 source is etc/hosts
SomeWhereOverTheRainBow
Part of the Furniture
I can resolve this issue. Thanks for the heads up. I also potentially got a fix for the system log time. I am currently working on it.
SomeWhereOverTheRainBow
Part of the Furniture
Here is the current feature request.It appears its not actually a bug, apparently AdGuardHome on most linux setup reports to system log using UTC time. The time is correct, and the date is correct. AdGuardHome only reports using the UTC though. This may have to be feature request someone puts in for.
Network Time Security support · Issue #2267 · AdguardTeam/AdGuardHome
Prerequisites 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 Problem Description Network Time Prot...
Have "-l syslog" and "log_localtime=true" honor the env TZ data or "/etc/localtime" · Issue #4207 · AdguardTeam/AdGuardHome
Have a question or an idea? Please search it on our forum to make sure it was not yet asked. If you cannot find what you had in mind, please submit it here. Prerequisites Please answer the followin...
github.com
SomeWhereOverTheRainBow
Part of the Furniture
Release v1.0.8
- S61 is migrating to S99 to prevent any conflicts with any other running DNS Daemons.
- bunch of reconfigurations to optimize loading of AdGuardHome.
Hi could anyone help. I get this error when trying to install on an RT-AC86U
Code:
Info: Downloading installer
Info: Downloading AdGuardHome_linux_arm64.tar.gz
fatal error: out of memory allocating heap arena map
runtime stack:
runtime.throw(0x90cd42, 0x27)
runtime/panic.go:1117 +0x54 fp=0x7fc4e4ebf0 sp=0x7fc4e4ebc0 pc=0x444a4
runtime.(*mheap).sysAlloc(0x21f0ee0, 0x400000, 0x7fc4e4ed08, 0x35ef0)
runtime/malloc.go:739 +0x5dc fp=0x7fc4e4eca0 sp=0x7fc4e4ebf0 pc=0x1bb6c
runtime.(*mheap).grow(0x21f0ee0, 0x1, 0x0)
runtime/mheap.go:1346 +0x80 fp=0x7fc4e4ed10 sp=0x7fc4e4eca0 pc=0x360f0
runtime.(*mheap).allocSpan(0x21f0ee0, 0x1, 0x2c00, 0x0)
runtime/mheap.go:1173 +0x670 fp=0x7fc4e4eda0 sp=0x7fc4e4ed10 pc=0x35f20
runtime.(*mheap).alloc.func1()
runtime/mheap.go:910 +0x54 fp=0x7fc4e4edf0 sp=0x7fc4e4eda0 pc=0x72344
runtime.(*mheap).alloc(0x21f0ee0, 0x1, 0x7fc4e4012c, 0x26844)
runtime/mheap.go:904 +0x64 fp=0x7fc4e4ee40 sp=0x7fc4e4edf0 pc=0x35494
runtime.(*mcentral).grow(0x2203218, 0x0)
runtime/mcentral.go:232 +0x74 fp=0x7fc4e4ee90 sp=0x7fc4e4ee40 pc=0x26b44
runtime.(*mcentral).cacheSpan(0x2203218, 0x0)
runtime/mcentral.go:158 +0x344 fp=0x7fc4e4ef00 sp=0x7fc4e4ee90 pc=0x26934
runtime.(*mcache).refill(0x7f90f98108, 0x2c)
runtime/mcache.go:162 +0xc0 fp=0x7fc4e4ef60 sp=0x7fc4e4ef00 pc=0x25c70
runtime.(*mcache).nextFree(0x7f90f98108, 0x21af82c, 0x7fc4e4efe8, 0x1cf00, 0x7fc4e4f018)
runtime/malloc.go:882 +0x8c fp=0x7fc4e4efb0 sp=0x7fc4e4ef60 pc=0x1be2c
runtime.mallocgc(0x178, 0x8d3660, 0x7fc4e4f001, 0x7fc4e4f0a8)
runtime/malloc.go:1069 +0x75c fp=0x7fc4e4f060 sp=0x7fc4e4efb0 pc=0x1c71c
runtime.newobject(0x8d3660, 0x47f68)
runtime/malloc.go:1177 +0x38 fp=0x7fc4e4f090 sp=0x7fc4e4f060 pc=0x1c938
runtime.malg(0x8000, 0x0)
runtime/proc.go:3988 +0x2c fp=0x7fc4e4f0e0 sp=0x7fc4e4f090 pc=0x4f5dc
runtime.mpreinit(0x21af8e0)
runtime/os_linux.go:355 +0x28 fp=0x7fc4e4f100 sp=0x7fc4e4f0e0 pc=0x41638
runtime.mcommoninit(0x21af8e0, 0xffffffffffffffff)
runtime/proc.go:744 +0xdc fp=0x7fc4e4f150 sp=0x7fc4e4f100 pc=0x4808c
runtime.schedinit()
runtime/proc.go:637 +0x98 fp=0x7fc4e4f1b0 sp=0x7fc4e4f150 pc=0x47ba8
runtime.rt0_go(0x7fc4e4fe15, 0x7fc4e4fe36, 0x0, 0x7fc4e4fe40, 0x7fc4e4fe61, 0x7fc4e4fe6c, 0x7fc4e4fe97, 0x7fc4e4fe9f, 0x7fc4e4feaa, 0x7fc4e4febd, ...)
runtime/asm_arm64.s:82 +0xa8 fp=0x7fc4e4f1e0 sp=0x7fc4e4f1b0 pc=0x797e8
*** Error: Failed to download AdGuardHome package for your router
Info: Operation aborted. You can quit or continue
=====================================================No I dont't have a swap
Code:
admin@RT-AC86U-2848:/tmp/home/root# free
total used free shared buffers cached
Mem: 440340 380104 60236 2540 604 87928
-/+ buffers/cache: 291572 148768
Swap: 0 0 0
Code:
admin@RT-AC86U-2848:/tmp/home/root# df -kh
Filesystem Size Used Available Use% Mounted on
ubi:rootfs_ubifs 77.2M 65.5M 11.6M 85% /
devtmpfs 214.9M 0 214.9M 0% /dev
tmpfs 215.0M 380.0K 214.6M 0% /var
tmpfs 215.0M 1.9M 213.1M 1% /tmp/mnt
mtd:bootfs 4.4M 3.3M 1.1M 75% /bootfs
tmpfs 215.0M 1.9M 213.1M 1% /tmp/mnt
mtd:data 8.0M 564.0K 7.4M 7% /data
tmpfs 215.0M 1.9M 213.1M 1% /tmp
/dev/mtdblock9 47.0M 7.9M 39.1M 17% /jffs
/dev/sda1 3.7G 59.5M 3.5G 2% /tmp/mnt/usb-extthegeneralguy
New Around Here
The internet check is buggy if you already have a custom DNS server like pihole/asus router is in bridged mode.
I'd just check curl of the actual adguard release instead of an oddball nslookup.
I'd just check curl of the actual adguard release instead of an oddball nslookup.
SomeWhereOverTheRainBow
Part of the Furniture
You are out of memory as far as how much space your router ram can allocate allowing the install process.
run the command
Code:
freeand post the output.
should look something like this
Code:
/tmp/home/root# free
total used free shared buffers cached
Mem: 903544 608292 295252 7536 8000 68312
-/+ buffers/cache: 531980 371564
Swap: 2097148 0 2097148Similar threads
Similar threads
Similar threads
-
-
-
AdGuardHome AdGuardHome New Release's 2023
- Started by SomeWhereOverTheRainBow
- Replies: 288
-
scMerlin scMerlin 2.5.1 - Service and script control menu for Asuswrt-Merlin, March 13, 2024- Started by thelonelycoder
- Replies: 34
-
uKasa uKasa - A utility script that manages Kasa smart outlets and switches with Asuswrt-Merlin routers- Started by JGrana
- Replies: 29
-
Updated Hue Utility - huetil Control and manage your Hue system from Asuswrt-Merlin or Raspbian
- Started by JGrana
- Replies: 1
-
DNScrypt Dnscrypt Proxy Installer For Asuswrt-Merlin late 2023 Releases
- Started by SomeWhereOverTheRainBow
- Replies: 8
-
AdGuardHome Help for beginner with AdGuardHome Asuswrt-Merlin- Started by fanasus
- Replies: 26