Menu
What's new
By:
Filters Better Search

AdGuardHome [RELEASE] Asuswrt-Merlin-AdGuardHome-Installer (AMAGHI)

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Ok.. AdGuardHome crashed again and caused Internet to crash

Jan 25 12:51:00 S61AdGuardHome[18126]: AdGuardHome found alive. Completing checks.
Jan 25 12:52:00 S61AdGuardHome[18281]: AdGuardHome found alive. Completing checks.
Jan 25 12:53:00 S61AdGuardHome[18435]: AdGuardHome found alive. Completing checks.
Jan 25 12:54:00 S61AdGuardHome[18594]: AdGuardHome found alive. Completing checks.
Jan 25 12:55:00 S61AdGuardHome[18749]: AdGuardHome found alive. Completing checks.
Jan 25 12:56:01 S61AdGuardHome[18914]: AdGuardHome found alive. Completing checks.
Jan 25 12:57:00 S61AdGuardHome[19063]: AdGuardHome found alive. Completing checks.
Jan 25 12:58:00 S61AdGuardHome[19217]: AdGuardHome found alive. Completing checks.
Jan 25 12:59:01 S61AdGuardHome[19373]: AdGuardHome found dead on checks. Starting before completing checks.
Jan 25 12:59:02 rc_service: service 19418:notify_rc restart_dnsmasq
Jan 25 12:59:02 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Jan 25 12:59:03 USER: Started AdGuardHome from .
Jan 25 12:59:07 S61AdGuardHome[19373]: AdGuardHome found alive. Completing checks.
Jan 25 13:00:36 syslog: wlceventd_proc_event(508): eth2: Disassoc 86:C4:43:96:E6:43, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:-79
Jan 25 13:00:59 syslog: wlceventd_proc_event(527): eth2: Auth 86:C4:43:96:E6:43, status: Successful (0), rssi:0
Jan 25 13:00:59 syslog: wlceventd_proc_event(556): eth2: Assoc 86:C4:43:96:E6:43, status: Successful (0), rssi:0
Jan 25 13:03:46 rc_service: service 20881:notify_rc restart_dnsmasq
Jan 25 13:03:46 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)

my repeated attempts to restart it couldn't help, it would crash right after restart (even after I rebooted the router AdGuard wouldn't start)
adguard-crash.png


From Sys log during restart attempts:

Jan 25 13:03:47 USER: Started AdGuardHome from .
Jan 25 13:05:14 rc_service: service 21153:notify_rc restart_dnsmasq
Jan 25 13:05:14 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Jan 25 13:05:14 USER: Started AdGuardHome from .
Jan 25 13:05:51 rc_service: service 21292:notify_rc restart_dnsmasq
Jan 25 13:05:51 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Jan 25 13:05:51 USER: Started AdGuardHome from .
Jan 25 13:08:07 rc_service: service 21673:notify_rc restart_dnsmasq
Jan 25 13:08:07 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Jan 25 13:08:08 USER: Started AdGuardHome from .
Jan 25 13:08:28 rc_service: service 21785:notify_rc restart_dnsmasq
Jan 25 13:08:28 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Jan 25 13:08:28 USER: Started AdGuardHome from .
Jan 25 13:09:23 rc_service: service 21983:notify_rc restart_dnsmasq
Jan 25 13:09:23 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Jan 25 13:09:24 USER: Started AdGuardHome from .


Also my internet wasn't working until I uninstalled AdGuardHome
 
Enhancement / feedback for consideration

Encountered a few times when running the installer, the shell just "hangs" at the last Info line. From the logs, it seems that a call to restart dnsmasq is initiated; not sure some other action(s) initiated as well.

As a last resort, a Ctrl + C is used to break out from the shell and when checking AdGuardHome status, it is dead and a restart is needed.

Perhaps it would be good to verbose the output of what is going on or "break out" of the hanging status

[Edit 1] Tried to examine the logs again and notice that during the restart of events, flexqos is also involved in the sequence. Not sure if this had potentially interrupted or cause issue

[Edit 2] Looking at the changes made for 1.07, assume there is a cron job added as part of the update/installation. It seems that in the event the update to 1.07 fails (as what I had encounter), the cron job will not be added. Will have to initiate the installer again and attempt to install again

[Edit 3] The check to determine if AdGuardHome is still alive makes use of a nslookup test. When I shell into the router and did a nslookup of google.com, it seems that the lookup is through the router's WAN DNS server. As such, not sure if this is the correct test AdGuardHome should be doing or it implies that there is an issue with the setup

[Edit 4] For some reason, the check seems to be not in a interval of 6hrs
Code: 
Jan 25 18:42:34 RT-AC86U-7510 S61AdGuardHome[15934]: AdGuardHome found alive. Completing checks.
Jan 25 18:44:56 RT-AC86U-7510 S61AdGuardHome[23106]: AdGuardHome found alive. Completing checks.
Jan 25 18:46:56 RT-AC86U-7510 S61AdGuardHome[23726]: AdGuardHome found alive. Completing checks.
Jan 25 18:48:57 RT-AC86U-7510 S61AdGuardHome[25710]: AdGuardHome found alive. Completing checks.
Jan 25 18:49:34 RT-AC86U-7510 S61AdGuardHome[21342]: AdGuardHome found alive. Completing checks.

1643104906152.png
 
Last edited:
Updated to v1.0.7.
Noticed the addition of cron job * */6 * * * /opt/etc/init.d/S61AdGuardHome check >/dev/null 2>&1 #S61AdGuardHome# which should run every 6 hours. Somehow in syslog, there is logs every minute that AdGuardHome found alive. Completing checks. What should be the correct mechanism?

Edit: it seems to have stopped after half an hour.
Just realized there are some logs seems regarding hosts file. Even before the update there are such logs.
Code: 
Jan 25 10:10:39 RT-AC86U-DBA8 AdGuardHome[6318]: 2022/01/25 10:10:39.631037 [error] hosts container: host "My_Computer.lan" is invalid, ignoring
Jan 25 10:10:39 RT-AC86U-DBA8 AdGuardHome[6318]: 2022/01/25 10:10:39.631271 [error] hosts container: host "My_Computer" is invalid, ignoring
 
Last edited:
SomeWhereOverTheRainBow said:
What is your router model and firmware version? Also what value do you get when you run

ls /opt/sbin

In the command line?

Edit***

From the looks of it, it appears your router failed to download a viable adguardhome binary, and the installer caught that.
Click to expand...
Thanks
Manage to fix the issue.
Clean up dnsmaq entries from manaul installation. Switch dhcp to router. Create swap file.
 
unknownz said:
Enhancement / feedback for consideration

Encountered a few times when running the installer, the shell just "hangs" at the last Info line. From the logs, it seems that a call to restart dnsmasq is initiated; not sure some other action(s) initiated as well.

As a last resort, a Ctrl + C is used to break out from the shell and when checking AdGuardHome status, it is dead and a restart is needed.

Perhaps it would be good to verbose the output of what is going on or "break out" of the hanging status

[Edit 1] Tried to examine the logs again and notice that during the restart of events, flexqos is also involved in the sequence. Not sure if this had potentially interrupted or cause issue

[Edit 2] Looking at the changes made for 1.07, assume there is a cron job added as part of the update/installation. It seems that in the event the update to 1.07 fails (as what I had encounter), the cron job will not be added. Will have to initiate the installer again and attempt to install again

[Edit 3] The check to determine if AdGuardHome is still alive makes use of a nslookup test. When I shell into the router and did a nslookup of google.com, it seems that the lookup is through the router's WAN DNS server. As such, not sure if this is the correct test AdGuardHome should be doing or it implies that there is an issue with the setup

[Edit 4] For some reason, the check seems to be not in a interval of 6hrs
Code: 
Jan 25 18:42:34 RT-AC86U-7510 S61AdGuardHome[15934]: AdGuardHome found alive. Completing checks.
Jan 25 18:44:56 RT-AC86U-7510 S61AdGuardHome[23106]: AdGuardHome found alive. Completing checks.
Jan 25 18:46:56 RT-AC86U-7510 S61AdGuardHome[23726]: AdGuardHome found alive. Completing checks.
Jan 25 18:48:57 RT-AC86U-7510 S61AdGuardHome[25710]: AdGuardHome found alive. Completing checks.
Jan 25 18:49:34 RT-AC86U-7510 S61AdGuardHome[21342]: AdGuardHome found alive. Completing checks.

View attachment 38894
Click to expand...
chongnt said:
Updated to v1.0.7.
Noticed the addition of cron job * */6 * * * /opt/etc/init.d/S61AdGuardHome check >/dev/null 2>&1 #S61AdGuardHome# which should run every 6 hours. Somehow in syslog, there is logs every minute that AdGuardHome found alive. Completing checks. What should be the correct mechanism?

Edit: it seems to have stopped after half an hour.
Just realized there are some logs seems regarding hosts file. Even before the update there are such logs.
Code: 
Jan 25 10:10:39 RT-AC86U-DBA8 AdGuardHome[6318]: 2022/01/25 10:10:39.631037 [error] hosts container: host "My_Computer.lan" is invalid, ignoring
Jan 25 10:10:39 RT-AC86U-DBA8 AdGuardHome[6318]: 2022/01/25 10:10:39.631271 [error] hosts container: host "My_Computer" is invalid, ignoring
Click to expand...
Yes the check first checks if Adguard home is even running,if it inst it restarts it. If it is , there is also the scenario that you have no DNS connection, because Adguard home is somehow incompacitated but still running. In this scenario, I could still ping www.google.com, but I would be unable to do DNS lookups. The loop is designed to continue, until you have internet. I will adjust it now that I see peoples internet connections could be the culprit behind why their adguardhome is not working.

@unknownz

if you are manually running

Code: 
/opt/etc/init.d/S61AdGuardHome check

Code: 
Jan 25 18:42:34 RT-AC86U-7510 S61AdGuardHome[15934]: AdGuardHome found alive. Completing checks.
Jan 25 18:44:56 RT-AC86U-7510 S61AdGuardHome[23106]: AdGuardHome found alive. Completing checks.
Jan 25 18:46:56 RT-AC86U-7510 S61AdGuardHome[23726]: AdGuardHome found alive. Completing checks.
Jan 25 18:48:57 RT-AC86U-7510 S61AdGuardHome[25710]: AdGuardHome found alive. Completing checks.
Jan 25 18:49:34 RT-AC86U-7510 S61AdGuardHome[21342]: AdGuardHome found alive. Completing checks.

The number [23106] in the logs next to S61AdGuardHome's name indicates that the check was invoked 4 separate instances, this number would be the same if it was for the same instance.

That would explain the extra logs. whenever you invoke check, now it test to see if adguardhome is active, before attempting to check on things. I highjacked this mechanism for a reason. People complaining AdguardHome of it crashing after 8 to 10 hours.
 
Last edited:
chongnt said:
Updated to v1.0.7.
Noticed the addition of cron job * */6 * * * /opt/etc/init.d/S61AdGuardHome check >/dev/null 2>&1 #S61AdGuardHome# which should run every 6 hours. Somehow in syslog, there is logs every minute that AdGuardHome found alive. Completing checks. What should be the correct mechanism?
Click to expand...
cron syntax is incorrect for every 6 hours, it should be something like this to run on the hour every 6 hours
Code: 
0 */6 * * *
1643114377007.png
 
MorlinArt said:
Ok.. AdGuardHome crashed again and caused Internet to crash

Jan 25 12:51:00 S61AdGuardHome[18126]: AdGuardHome found alive. Completing checks.
Jan 25 12:52:00 S61AdGuardHome[18281]: AdGuardHome found alive. Completing checks.
Jan 25 12:53:00 S61AdGuardHome[18435]: AdGuardHome found alive. Completing checks.
Jan 25 12:54:00 S61AdGuardHome[18594]: AdGuardHome found alive. Completing checks.
Jan 25 12:55:00 S61AdGuardHome[18749]: AdGuardHome found alive. Completing checks.
Jan 25 12:56:01 S61AdGuardHome[18914]: AdGuardHome found alive. Completing checks.
Jan 25 12:57:00 S61AdGuardHome[19063]: AdGuardHome found alive. Completing checks.
Jan 25 12:58:00 S61AdGuardHome[19217]: AdGuardHome found alive. Completing checks.
Jan 25 12:59:01 S61AdGuardHome[19373]: AdGuardHome found dead on checks. Starting before completing checks.
Jan 25 12:59:02 rc_service: service 19418:notify_rc restart_dnsmasq
Jan 25 12:59:02 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Jan 25 12:59:03 USER: Started AdGuardHome from .
Jan 25 12:59:07 S61AdGuardHome[19373]: AdGuardHome found alive. Completing checks.
Jan 25 13:00:36 syslog: wlceventd_proc_event(508): eth2: Disassoc 86:C4:43:96:E6:43, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:-79
Jan 25 13:00:59 syslog: wlceventd_proc_event(527): eth2: Auth 86:C4:43:96:E6:43, status: Successful (0), rssi:0
Jan 25 13:00:59 syslog: wlceventd_proc_event(556): eth2: Assoc 86:C4:43:96:E6:43, status: Successful (0), rssi:0
Jan 25 13:03:46 rc_service: service 20881:notify_rc restart_dnsmasq
Jan 25 13:03:46 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)

my repeated attempts to restart it couldn't help, it would crash right after restart (even after I rebooted the router AdGuard wouldn't start)
View attachment 38893

From Sys log during restart attempts:

Jan 25 13:03:47 USER: Started AdGuardHome from .
Jan 25 13:05:14 rc_service: service 21153:notify_rc restart_dnsmasq
Jan 25 13:05:14 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Jan 25 13:05:14 USER: Started AdGuardHome from .
Jan 25 13:05:51 rc_service: service 21292:notify_rc restart_dnsmasq
Jan 25 13:05:51 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Jan 25 13:05:51 USER: Started AdGuardHome from .
Jan 25 13:08:07 rc_service: service 21673:notify_rc restart_dnsmasq
Jan 25 13:08:07 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Jan 25 13:08:08 USER: Started AdGuardHome from .
Jan 25 13:08:28 rc_service: service 21785:notify_rc restart_dnsmasq
Jan 25 13:08:28 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Jan 25 13:08:28 USER: Started AdGuardHome from .
Jan 25 13:09:23 rc_service: service 21983:notify_rc restart_dnsmasq
Jan 25 13:09:23 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Jan 25 13:09:24 USER: Started AdGuardHome from .


Also my internet wasn't working until I uninstalled AdGuardHome
Click to expand...
is there any erraneous entries inside your
Code: 
/etc/host
file?
 
MorlinArt said:
Ok.. AdGuardHome crashed again and caused Internet to crash

Jan 25 12:51:00 S61AdGuardHome[18126]: AdGuardHome found alive. Completing checks.
Jan 25 12:52:00 S61AdGuardHome[18281]: AdGuardHome found alive. Completing checks.
Jan 25 12:53:00 S61AdGuardHome[18435]: AdGuardHome found alive. Completing checks.
Jan 25 12:54:00 S61AdGuardHome[18594]: AdGuardHome found alive. Completing checks.
Jan 25 12:55:00 S61AdGuardHome[18749]: AdGuardHome found alive. Completing checks.
Jan 25 12:56:01 S61AdGuardHome[18914]: AdGuardHome found alive. Completing checks.
Jan 25 12:57:00 S61AdGuardHome[19063]: AdGuardHome found alive. Completing checks.
Jan 25 12:58:00 S61AdGuardHome[19217]: AdGuardHome found alive. Completing checks.
Jan 25 12:59:01 S61AdGuardHome[19373]: AdGuardHome found dead on checks. Starting before completing checks.
Jan 25 12:59:02 rc_service: service 19418:notify_rc restart_dnsmasq
Jan 25 12:59:02 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Jan 25 12:59:03 USER: Started AdGuardHome from .
Jan 25 12:59:07 S61AdGuardHome[19373]: AdGuardHome found alive. Completing checks.
Jan 25 13:00:36 syslog: wlceventd_proc_event(508): eth2: Disassoc 86:C4:43:96:E6:43, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:-79
Jan 25 13:00:59 syslog: wlceventd_proc_event(527): eth2: Auth 86:C4:43:96:E6:43, status: Successful (0), rssi:0
Jan 25 13:00:59 syslog: wlceventd_proc_event(556): eth2: Assoc 86:C4:43:96:E6:43, status: Successful (0), rssi:0
Jan 25 13:03:46 rc_service: service 20881:notify_rc restart_dnsmasq
Jan 25 13:03:46 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)

my repeated attempts to restart it couldn't help, it would crash right after restart (even after I rebooted the router AdGuard wouldn't start)
View attachment 38893

From Sys log during restart attempts:

Jan 25 13:03:47 USER: Started AdGuardHome from .
Jan 25 13:05:14 rc_service: service 21153:notify_rc restart_dnsmasq
Jan 25 13:05:14 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Jan 25 13:05:14 USER: Started AdGuardHome from .
Jan 25 13:05:51 rc_service: service 21292:notify_rc restart_dnsmasq
Jan 25 13:05:51 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Jan 25 13:05:51 USER: Started AdGuardHome from .
Jan 25 13:08:07 rc_service: service 21673:notify_rc restart_dnsmasq
Jan 25 13:08:07 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Jan 25 13:08:08 USER: Started AdGuardHome from .
Jan 25 13:08:28 rc_service: service 21785:notify_rc restart_dnsmasq
Jan 25 13:08:28 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Jan 25 13:08:28 USER: Started AdGuardHome from .
Jan 25 13:09:23 rc_service: service 21983:notify_rc restart_dnsmasq
Jan 25 13:09:23 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Jan 25 13:09:24 USER: Started AdGuardHome from .


Also my internet wasn't working until I uninstalled AdGuardHome
Click to expand...
Should be resolved now hopefully. Faulty cronjob syntax may have been the culprit.
 
MorlinArt said:
no, just these
Code: 
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
127.0.0.1    localhost
255.255.255.255    broadcasthost
::1             localhost
Click to expand...
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.
 
Something weird observed in the logs after the minor update to v1.07
For some reason AdGuardHome is not observing the correct time zone (GMT +8)

Doing a
Bash: 
AdGuardHome check
causes the command to "hang" also

Code: 
Jan 25 21:37:39 RT-AC86U-7510 dnsmasq[13033]: using only locally-known addresses for 8.4.6.7.0.2.3.0.0.3.6.0.4.2.ip6.arpa
Jan 25 21:37:39 RT-AC86U-7510 dnsmasq[13033]: using only locally-known addresses for 10.in-addr.arpa
Jan 25 21:37:39 RT-AC86U-7510 dnsmasq[13033]: using only locally-known addresses for 168.192.in-addr.arpa
Jan 25 21:37:39 RT-AC86U-7510 dnsmasq[13033]: using only locally-known addresses for _dns.resolver.arpa
Jan 25 21:37:39 RT-AC86U-7510 dnsmasq[13033]: using only locally-known addresses for use-application-dns.net
Jan 25 21:37:39 RT-AC86U-7510 dnsmasq[13033]: using only locally-known addresses for kylim-home
Jan 25 13:37:49 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:37:49.682650 [info] Starting the DNS proxy server
Jan 25 13:37:49 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:37:49.683540 [info] Ratelimit is enabled and set to 20 rps
Jan 25 13:37:49 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:37:49.683780 [info] The server is configured to refuse ANY requests
Jan 25 13:37:49 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:37:49.683959 [info] DNS cache is enabled
Jan 25 13:37:49 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:37:49.684129 [info] MaxGoroutines is set to 300
Jan 25 13:37:49 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:37:49.684321 [info] Creating the UDP server socket
Jan 25 13:37:49 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:37:49.684743 [info] Listening to udp://[::]:53
Jan 25 13:37:49 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:37:49.684897 [info] Creating a TCP server socket
Jan 25 13:37:49 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:37:49.685134 [info] Listening to tcp://[::]:53
Jan 25 13:37:49 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:37:49.691102 [info] Entering the UDP listener loop on [::]:53
Jan 25 13:37:49 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:37:49.691281 [info] Entering the tcp listener loop on [::]:53
Jan 25 21:38:00 RT-AC86U-7510 FlexQoS: /jffs/addons/flexqos/flexqos.sh (pid=13159) called in unattended mode with 1 args: -check
Jan 25 21:38:00 RT-AC86U-7510 FlexQoS: iptables rules already present
Jan 25 21:38:00 RT-AC86U-7510 FlexQoS: No TC modifications necessary
Jan 25 13:38:14 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:38:14.479057 [info] Received signal "interrupt"
Jan 25 13:38:14 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:38:14.479155 [info] stopping AdGuard Home
Jan 25 13:38:14 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:38:14.479175 [info] stopping http server...
Jan 25 13:38:14 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:38:14.502813 [info] stopped http server
Jan 25 13:38:18 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:38:18.627759 [info] Stopping the DNS proxy server
Jan 25 13:38:18 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:38:18.628057 [info] Stopped the DNS proxy server
 
unknownz said:
Something weird observed in the logs after the minor update to v1.07
For some reason AdGuardHome is not observing the correct time zone (GMT +8)

Code: 
Jan 25 21:37:39 RT-AC86U-7510 dnsmasq[13033]: using only locally-known addresses for 8.4.6.7.0.2.3.0.0.3.6.0.4.2.ip6.arpa
Jan 25 21:37:39 RT-AC86U-7510 dnsmasq[13033]: using only locally-known addresses for 10.in-addr.arpa
Jan 25 21:37:39 RT-AC86U-7510 dnsmasq[13033]: using only locally-known addresses for 168.192.in-addr.arpa
Jan 25 21:37:39 RT-AC86U-7510 dnsmasq[13033]: using only locally-known addresses for _dns.resolver.arpa
Jan 25 21:37:39 RT-AC86U-7510 dnsmasq[13033]: using only locally-known addresses for use-application-dns.net
Jan 25 21:37:39 RT-AC86U-7510 dnsmasq[13033]: using only locally-known addresses for kylim-home
Jan 25 13:37:49 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:37:49.682650 [info] Starting the DNS proxy server
Jan 25 13:37:49 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:37:49.683540 [info] Ratelimit is enabled and set to 20 rps
Jan 25 13:37:49 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:37:49.683780 [info] The server is configured to refuse ANY requests
Jan 25 13:37:49 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:37:49.683959 [info] DNS cache is enabled
Jan 25 13:37:49 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:37:49.684129 [info] MaxGoroutines is set to 300
Jan 25 13:37:49 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:37:49.684321 [info] Creating the UDP server socket
Jan 25 13:37:49 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:37:49.684743 [info] Listening to udp://[::]:53
Jan 25 13:37:49 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:37:49.684897 [info] Creating a TCP server socket
Jan 25 13:37:49 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:37:49.685134 [info] Listening to tcp://[::]:53
Jan 25 13:37:49 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:37:49.691102 [info] Entering the UDP listener loop on [::]:53
Jan 25 13:37:49 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:37:49.691281 [info] Entering the tcp listener loop on [::]:53
Jan 25 21:38:00 RT-AC86U-7510 FlexQoS: /jffs/addons/flexqos/flexqos.sh (pid=13159) called in unattended mode with 1 args: -check
Jan 25 21:38:00 RT-AC86U-7510 FlexQoS: iptables rules already present
Jan 25 21:38:00 RT-AC86U-7510 FlexQoS: No TC modifications necessary
Jan 25 13:38:14 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:38:14.479057 [info] Received signal "interrupt"
Jan 25 13:38:14 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:38:14.479155 [info] stopping AdGuard Home
Jan 25 13:38:14 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:38:14.479175 [info] stopping http server...
Jan 25 13:38:14 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:38:14.502813 [info] stopped http server
Jan 25 13:38:18 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:38:18.627759 [info] Stopping the DNS proxy server
Jan 25 13:38:18 RT-AC86U-7510 AdGuardHome[12970]: 2022/01/25 13:38:18.628057 [info] Stopped the DNS proxy server
Click to expand...
Try stopping and starting it. Also, check to make sure your clock and/ or routers timezone has not become unset. If not, then this issue purely appears to be adguardhome not passing the correct time. The only thing I can do is tell the init.d script where the tz is which I do.

May be a bug I have to bring up with adguardhome devs
 
unknownz said:
If you look at the logs enclosed, dnsmasq was reporting the correct time and when AdGuardHome starts, the time went wrong
Click to expand...
I get that, it is purely adguardhome bug, please try stop and starting it to see if it is correctable. Other users have reported running into this issue, but claimed it went away after Restarting the AdGuardHome
 
Last edited:
SomeWhereOverTheRainBow said:
I get that, it is purely adguardhome bug, please try stop and starting it to see if it is correctable.
Click to expand...
Looks like it's a bug as you have mentioned. Was checking back all the related AdGuardHome logs and that time issue has since been there.

About the AdGuardHome check using nslookup, I mentioned earlier it seems to be using the router's WAN DNS server. Should there be correct?
 
SomeWhereOverTheRainBow said:
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.
Click to expand...

thanks... trying it now
 
You must log in or register to reply here.

Similar threads

J
AdGuardHome AdGuardHome stops working after every router reboot - have to un-/reinstall it every time
Replies
0
Views
220
jtbx
J
SomeWhereOverTheRainBow
  • Locked
AdGuardHome AdGuardHome New Release's 2023
13 14 15
Replies
288
Views
32K
visortgw
visortgw
SomeWhereOverTheRainBow
  • Locked
AdGuardHome Asuswrt-Merlin-AdGuardHome-Installer (AMAGHI) cont.
22 23 24
Replies
461
Views
55K
SomeWhereOverTheRainBow
SomeWhereOverTheRainBow
SomeWhereOverTheRainBow
DNScrypt Dnscrypt Proxy Installer For Asuswrt-Merlin late 2023 Releases
Replies
8
Views
3K
zer0bitz
zer0bitz
M
AdGuardHome Latest Entware update possibly made AdGuard Home fail
2
Replies
23
Views
6K
SomeWhereOverTheRainBow
SomeWhereOverTheRainBow
Similar threads
Thread starter Title Forum Replies Date
R DomainVPNRouting Domain VPN Routing v3.0.4 ***Release*** Asuswrt-Merlin AddOns 54
Viktor Jaep [RELEASE] ECLIPSEMON v0.0.1 - Crazy Complex Solar Eclipse Astronomical Calculator to predict if a Solar Eclipse will appear today! Asuswrt-Merlin AddOns 42
John Fitzgerald Skynet New Skynet 7.6.3 Release Asuswrt-Merlin AddOns 147
thelonelycoder amtm amtm 5.1 - the Asuswrt-Merlin Terminal Menu, December 09, 2024 Asuswrt-Merlin AddOns 69
J Entware Possible to install jdownloader on asuswrt-merlin router with entware?? Asuswrt-Merlin AddOns 9
W Skynet SOLVED: Scrollbar Disappears on Skynet Tab on Asuswrt-Merlin 386.14 Asuswrt-Merlin AddOns 10
thelonelycoder scMerlin scMerlin 2.5.8 - Service and script control menu for Asuswrt-Merlin, October 20, 2024 Asuswrt-Merlin AddOns 85
JGrana uKasa uKasa - A utility script that manages Kasa smart outlets and switches with Asuswrt-Merlin routers Asuswrt-Merlin AddOns 31
JGrana Updated Hue Utility - huetil Control and manage your Hue system from Asuswrt-Merlin or Raspbian Asuswrt-Merlin AddOns 1
8 ASUS RT-AX58U (F/W Ver.:V3.0.0.4.384.8601) with Asuswrt-Merlin 3004.388.5 - Transmission: "Could not connect to the server. You may need to reload" Asuswrt-Merlin AddOns 2

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Total: 687 (members: 11, guests: 676)
Top