What's new

AdGuardHome AdGuardHome New Release's 2023

  • 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!

Status
Not open for further replies.
AGH devs released a new version (AdGuard Home v0.107.41) which includes a "fix" for a case of quic and h3 connection failure ( https://github.com/AdguardTeam/AdGuardHome/issues/6335 ) i didn't have this problem before, ironically, after updating, i cannot use quic and h3 servers anymore:

Server "h3://dns.google/dns-query": could not be used, please check that you've written it correctly
Server "quic://dns.adguard-dns.com": could not be used, please check that you've written it correctly

Anybody else having this problem?
Are you using the "edge" version? Also, please review AGH help wiki to see if they changed any of the upstream server formatting. They are notorious for changing the yaml config format whenever releasing a big fix.
 
I am going to be running some tests later to see if we just simply need to restart scribe on starting AdGuardhome. There may be a solution, but I just haven't had time to test it. I am still at a loss for why syslog-ng (scribe) would be breaking AdGuardhomes abilities to report to syslog. It is this breakage that makes adguardhome fail to start.

The whole issue itself is completely undetectable because the logs for starting adguardhome simply do not populate when the bug is happing. So, the user wouldn't be able to tell that it was adguardhome failing to initiate the go syslog facilitators. I had to try starting adguardhome straight from the terminal command line to be able to reproduce the issue. There, the lines that would have printed to syslog indicating the failure, printed to the terminal mentioning that adguardhome was unable to load the drivers for communicating with syslog.

The bug is only present "sometimes" when running syslog-ng. Once I restarted scribe, adguardhome worked with no problems.
Really thanks for the explanation, for me it is not super essential to use scribe so it is ok in this way without it.
 
Really thanks for the explanation, for me it is not super essential to use scribe so it is ok in this way without it.
I just launched an actual fix. So far I have only tested it. If you get the free time and would like to provide input on whether it resolves the issue, it would be appreciated. I am sure it will help other missfortunate souls who run scribe and cannot get AdGuardHome to start occasionally.

If you decide to test it, just run the command below in the terminal once you are ready:

curl -L -s -k -O https://raw.githubusercontent.com/jumpsmm7/Asuswrt-Merlin-AdGuardHome-Installer/dev/installer && sh installer dev update
 
I just launched an actual fix. So far I have only tested it. If you get the free time and would like to provide input on whether it resolves the issue, it would be appreciated. I am sure it will help other missfortunate souls who run scribe and cannot get AdGuardHome to start occasionally.

If you decide to test it, just run the command below in the terminal once you are ready:

curl -L -s -k -O https://raw.githubusercontent.com/jumpsmm7/Asuswrt-Merlin-AdGuardHome-Installer/dev/installer && sh installer dev update
Sure after work I’ll try it and I give you a feedback thanks
 
tried it right now seems to work.
These are the steps that I've carried out.
I've re-installed scribe and ui-scribe then I ran your command and AdGuard restarted correctly.

I haven't tried to reboot the router to see if AdGuard Home is loaded correctly.

I've attached the log if it can help you in some way
 

Attachments

  • log.txt
    23.7 KB · Views: 25
Last edited:
tried it right now seems to work.
These are the steps that I've carried out.
I've re-installed scribe and ui-scribe then I ran your command and AdGuard restarted correctly.

I haven't tried to reboot the router to see if AdGuard Home is loaded correctly.

I've attached the log if it can help you in some way
So, madao - I installed a super massive filterlists. I then Rebooted. it worked, but it took a minute longer than it typically does because of all my Aimesh devices.

Here is my testing defaults...


Code:
http:
  pprof:
    port: 6060
    enabled: false
  address: 0.0.0.0:3000
  session_ttl: 720h
users:
  - name: **REDACT**
    password: **REDACT**
auth_attempts: 5
block_auth_min: 15
http_proxy: ""
language: ""
theme: auto
dns:
  bind_hosts:
    - 0.0.0.0
  port: 53
  anonymize_client_ip: false
  ratelimit: 20
  ratelimit_subnet_len_ipv4: 24
  ratelimit_subnet_len_ipv6: 56
  ratelimit_whitelist: []
  refuse_any: true
  upstream_dns:
    - '[/router.asus.com/][::]:553'
    - '[/www.asusnetwork.net/][::]:553'
    - '[/www.asusrouter.com/][::]:553'
    - '[/use-application-dns.net/][::]:553'
    - '[/dns.resolver.arpa/][::]:553'
    - '[/Some-Network/][::]:553'
    - '[//][::]:553'
    - https://security.cloudflare-dns.com/dns-query
    - tls://security.cloudflare-dns.com
    - https://doh.cleanbrowsing.org/doh/security-filter/
    - tls://security-filter-dns.cleanbrowsing.org
    - https://dns11.quad9.net/dns-query
    - tls://dns11.quad9.net
  upstream_dns_file: ""
  bootstrap_dns:
    - 1.1.1.1
    - 1.0.0.1
  fallback_dns:
    - '[::]:553'
    - tcp://[::]:553
  all_servers: true
  fastest_addr: false
  fastest_timeout: 1s
  allowed_clients: []
  disallowed_clients: []
  blocked_hosts:
    - version.bind
    - id.server
    - hostname.bind
  trusted_proxies:
    - 127.0.0.0/8
    - ::1/128
  cache_size: 1048576
  cache_ttl_min: 1200
  cache_ttl_max: 14400
  cache_optimistic: true
  bogus_nxdomain: []
  aaaa_disabled: false
  enable_dnssec: true
  edns_client_subnet:
    custom_ip: ""
    enabled: false
    use_custom: false
  max_goroutines: 300
  handle_ddr: true
  ipset: []
  ipset_file: ""
  bootstrap_prefer_ipv6: false
  upstream_timeout: 10s
  private_networks: []
  use_private_ptr_resolvers: true
  local_ptr_upstreams:
    - '[::]:553'
    - '[/10.in-addr.arpa/][::]:553'
    - '[/168.192.in-addr.arpa/][::]:553'
  use_dns64: false
  dns64_prefixes: []
  serve_http3: false
  use_http3_upstreams: false
tls:
  enabled: false
  server_name: ""
  force_https: false
  port_https: 443
  port_dns_over_tls: 853
  port_dns_over_quic: 853
  port_dnscrypt: 0
  dnscrypt_config_file: ""
  allow_unencrypted_doh: false
  certificate_chain: ""
  private_key: ""
  certificate_path: ""
  private_key_path: ""
  strict_sni_check: false
querylog:
  ignored: []
  interval: 2160h
  size_memory: 1000
  enabled: true
  file_enabled: true
statistics:
  ignored: []
  interval: 24h
  enabled: true
filters:
  - enabled: true
    url: https://raw.githubusercontent.com/jumpsmm7/GeneratedAdblock/master/GeneratedDomainsConservative.0.filter
    name: DomainsConservative.0.filter
    id: 1699978789
  - enabled: true
    url: https://raw.githubusercontent.com/jumpsmm7/GeneratedAdblock/master/GeneratedDomainsConservative.1.filter
    name: DomainsConservative.1.filter
    id: 1699978790
  - enabled: true
    url: https://raw.githubusercontent.com/jumpsmm7/GeneratedAdblock/master/GeneratedDomainsConservative.2.filter
    name: DomainsConservative.2.filter
    id: 1699978791
  - enabled: true
    url: https://raw.githubusercontent.com/jumpsmm7/GeneratedAdblock/master/GeneratedDomainsConservative.3.filter
    name: DomainsConservative.3.filter
    id: 1699978792
  - enabled: true
    url: https://raw.githubusercontent.com/jumpsmm7/GeneratedAdblock/master/GeneratedDomainsConservative.4.filter
    name: DomainsConservative.4.filter
    id: 1699978793
  - enabled: true
    url: https://raw.githubusercontent.com/jumpsmm7/GeneratedAdblock/master/GeneratedDomainsConservative.5.filter
    name: DomainsConservative.5.filter
    id: 1699978794
  - enabled: true
    url: https://raw.githubusercontent.com/jumpsmm7/GeneratedAdblock/master/GeneratedDomainsConservative.6.filter
    name: DomainsConservative.6.filter
    id: 1699978795
  - enabled: true
    url: https://raw.githubusercontent.com/jumpsmm7/GeneratedAdblock/master/GeneratedDomainsConservative.7.filter
    name: DomainsConservative.7.filter
    id: 1699978796
  - enabled: true
    url: https://raw.githubusercontent.com/jumpsmm7/GeneratedAdblock/master/GeneratedDomainsConservative.8.filter
    name: DomainsConservative.8.filter
    id: 1699978797
  - enabled: true
    url: https://raw.githubusercontent.com/jumpsmm7/GeneratedAdblock/master/GeneratedDomainsConservative.9.filter
    name: DomainsConservative.9.filter
    id: 1699978798
  - enabled: true
    url: https://raw.githubusercontent.com/jumpsmm7/GeneratedAdblock/master/GeneratedDomainsConservative.10.filter
    name: DomainsConservative.10.filter
    id: 1699978799
  - enabled: true
    url: https://raw.githubusercontent.com/jumpsmm7/GeneratedAdblock/master/GeneratedDomainsConservative.11.filter
    name: DomainsConservative.11.filter
    id: 1699978800
  - enabled: true
    url: https://raw.githubusercontent.com/jumpsmm7/GeneratedAdblock/master/GeneratedDomainsConservative.12.filter
    name: DomainsConservative.12.filter
    id: 1699978801
  - enabled: true
    url: https://raw.githubusercontent.com/jumpsmm7/GeneratedAdblock/master/GeneratedDomainsConservative.13.filter
    name: DomainsConservative.13.filter
    id: 1699978802
  - enabled: true
    url: https://raw.githubusercontent.com/jumpsmm7/GeneratedAdblock/master/GeneratedDomainsConservative.14.filter
    name: DomainsConservative.14.filter
    id: 1699978803
whitelist_filters: []
user_rules: []
dhcp:
  enabled: false
  interface_name: ""
  local_domain_name: lan
  dhcpv4:
    gateway_ip: ""
    subnet_mask: ""
    range_start: ""
    range_end: ""
    lease_duration: 86400
    icmp_timeout_msec: 1000
    options: []
  dhcpv6:
    range_start: ""
    lease_duration: 86400
    ra_slaac_only: false
    ra_allow_slaac: false
filtering:
  blocking_ipv4: ""
  blocking_ipv6: ""
  blocked_services:
    schedule:
      time_zone: UTC
    ids: []
  protection_disabled_until: null
  safe_search:
    enabled: true
    bing: true
    duckduckgo: true
    google: true
    pixabay: true
    yandex: true
    youtube: true
  blocking_mode: default
  parental_block_host: family-block.dns.adguard.com
  safebrowsing_block_host: standard-block.dns.adguard.com
  rewrites: []
  safebrowsing_cache_size: 1048576
  safesearch_cache_size: 1048576
  parental_cache_size: 1048576
  cache_time: 30
  filters_update_interval: 72
  blocked_response_ttl: 10
  filtering_enabled: true
  parental_enabled: true
  safebrowsing_enabled: true
  protection_enabled: true
clients:
  runtime_sources:
    whois: true
    arp: true
    rdns: true
    dhcp: true
    hosts: true
  persistent: []
log:
  file: ""
  max_backups: 0
  max_size: 100
  max_age: 3
  compress: false
  local_time: false
  verbose: false
os:
  group: ""
  user: ""
  rlimit_nofile: 0
schema_version: 27
 
I don't have any AImesh device.
As soon as I can, probably in the week end, I reboot the router and I will confirm you if even after the reboot of the router AGH starts correctly.
 
Are you using the "edge" version? Also, please review AGH help wiki to see if they changed any of the upstream server formatting. They are notorious for changing the yaml config format whenever releasing a big fix.
Sorry for the delay I've fixed the problem by adding QUIC_GO_DISABLE_ECN=true to /opt/etc/init.d/S99AdGuardHome PREARGS section (gotta stop AGH before this and restart after) now both h3 and quic are working fine. if many people having this problem, this should be part of the default config maybe idk? or maybe this happened because of double nat.
 
Sorry for the delay I've fixed the problem by adding QUIC_GO_DISABLE_ECN=true to /opt/etc/init.d/S99AdGuardHome PREARGS section (gotta stop AGH before this and restart after) now both h3 and quic are working fine.
I figured it was something the AdGuardHome developers changed. Strange I haven't discovered this option yet, but it doesn't surprise me that the AGH development team changed something again. Do you mind sharing where you read about this option at ? I would like to read more about it to access if it is needed the "average" users use case.

I just read about it here https://github.com/AdguardTeam/AdGuardHome/issues/6422 , it turns out it relates to the kernel version on whether the option is needed or not. The option disables the additional congestion-control features added to quic-go in v0.39.0. Certain older kernels tend to not agree with the changes in quic-go.

maybe this happened because of double nat.
The issue doesn't seem like something that would be caused from being in a double nat. Especially if it worked for you before the last update/fix.
 
Last edited:
Release v1.6.7

What's Changed
  • Fix memory limits
  • Use nohup to help break free of terminal break aways.
  • Fix stack size for a GO process like AdGuardHome
  • Add bug fix consideration for users running syslog-ng (scribe) # Thanks goes to @madao for helping investigate the issue.
  • Fix line endings
  • Re-prioritize nice values for AdGuardHome.
  • Adjust memory confinements for heap, set maximum for stack.
  • Fix quic option. # Thanks goes to @exoxon for pointing out the issue and providing the solution.
**Full Changelog**: https://github.com/jumpsmm7/Asuswrt-Merlin-AdGuardHome-Installer/compare/v1.6.6...v1.6.7
 
I figured it was something the AdGuardHome developers changed. Strange I haven't discovered this option yet, but it doesn't surprise me that the AGH development team changed something again. Do you mind sharing where you read about this option at ? I would like to read more about it to access if it is needed the "average" users use case.

I just read about it here https://github.com/AdguardTeam/AdGuardHome/issues/6422 , it turns out it relates to the kernel version on whether the option is needed or not. The option disables the additional congestion-control features added to quic-go in v0.39.0. Certain older kernels tend to not agree with the changes in quic-go.


The issue doesn't seem like something that would be caused from being in a double nat. Especially if it worked for you before the last update/fix.
I get the fix from the same bug report that you linked. Thanks for the help and quick fix. Cheers.
 
Just did a new install of AG v1.6.7 and noticed following during installation:

Code:
 Info:  Writing AdGuardHome configuration...
 Info:  Checking AdGuardHome configuration...
 Info:  Starting AdGuardHome...
/opt/etc/init.d/S99AdGuardHome: line 9: nproc: not found
 Checking AdGuardHome...              dead.
/opt/etc/init.d/S99AdGuardHome: line 9: nproc: not found
 Checking AdGuardHome...              alive.
 Info:  Please wait while we perform one last check.
/opt/etc/init.d/S99AdGuardHome: line 9: nproc: not found
 Checking AdGuardHome...              alive.
 Info:  AdGuardHome setup is complete.
 Info:  Operation completed, returning to Main Menu. You can quit or continue.

Looking into the file S99AdGuardHome :
Code:
#!/bin/sh
renice -10 $$
ENABLED="yes"
WORK_DIR="/opt/etc/AdGuardHome"
LOG_FILE="syslog"
PID_FILE="/opt/var/run/AdGuardHome.pid"
PROCS="AdGuardHome"
GOGC="40"
GOMAXPROCS="$(nproc)"
GOMAXPROCS="$((GOMAXPROCS == 4 ? 2 : (GOMAXPROCS == 2 ? 1 : 1)))"
GOMEMLIMIT="$(free | awk -v VAR=$GOMAXPROCS '/Mem/{print int(($4*0.9537/1024)/VAR)}')MiB"
ARGS="-s run -c ${WORK_DIR}/AdGuardHome.yaml -w $WORK_DIR --pidfile $PID_FILE --no-check-update -l $LOG_FILE"
PREARGS="env TZ=/etc/localtime GOGC=${GOGC} GOMAXPROCS=${GOMAXPROCS} GOMEMLIMIT=${GOMEMLIMIT} QUIC_GO_DISABLE_ECN=true"
PRECMD="{ ulimit -v 1750000; ulimit -m 450000; ulimit -s 8192; } && { if pidof syslog-ng logrotate | wc -w | grep -qE '^[^0]$'; then scribe restart; fi; until pidof $PROCS | grep -qE '.*'; do { killall -9 $(netstat -nlp 2>/dev/null | awk -F/ -v VAR=$PROCS '$0 ~ /.*:53[[:space:]].*/ && $0 !~ VAR {if(!x[$2]++) printf "%s ", $2}') || kill -s 9 $(netstat -nlp 2>/dev/null | awk -v VAR=$PROCS '$0 ~ /.*:53[[:space:]].*/ && $0 !~ VAR {match($7, /[0-9]+/); if (RSTART && !x[$7]++) printf "%s ", substr($7, RSTART, RLENGTH)}'); }; service stop_dnsmasq; done; } &"
POSTCMD="service restart_dnsmasq"
DESC="$PROCS"
PATH="/opt/sbin:/opt/bin:/opt/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
export TZ="$(cat /etc/TZ)"
[ -z "$SCRIPT_LOC" ] && . /jffs/addons/AdGuardHome.d/AdGuardHome.sh

@SomeWhereOverTheRainBow I also noticed it when doing a upgrade of AG, so tried a fresh install but the messages "line 9: nproc: not found" still showing up . Can you check why these messages do appear?
 
Just did a new install of AG v1.6.7 and noticed following during installation:

Code:
 Info:  Writing AdGuardHome configuration...
 Info:  Checking AdGuardHome configuration...
 Info:  Starting AdGuardHome...
/opt/etc/init.d/S99AdGuardHome: line 9: nproc: not found
 Checking AdGuardHome...              dead.
/opt/etc/init.d/S99AdGuardHome: line 9: nproc: not found
 Checking AdGuardHome...              alive.
 Info:  Please wait while we perform one last check.
/opt/etc/init.d/S99AdGuardHome: line 9: nproc: not found
 Checking AdGuardHome...              alive.
 Info:  AdGuardHome setup is complete.
 Info:  Operation completed, returning to Main Menu. You can quit or continue.

Looking into the file S99AdGuardHome :
Code:
#!/bin/sh
renice -10 $$
ENABLED="yes"
WORK_DIR="/opt/etc/AdGuardHome"
LOG_FILE="syslog"
PID_FILE="/opt/var/run/AdGuardHome.pid"
PROCS="AdGuardHome"
GOGC="40"
GOMAXPROCS="$(nproc)"
GOMAXPROCS="$((GOMAXPROCS == 4 ? 2 : (GOMAXPROCS == 2 ? 1 : 1)))"
GOMEMLIMIT="$(free | awk -v VAR=$GOMAXPROCS '/Mem/{print int(($4*0.9537/1024)/VAR)}')MiB"
ARGS="-s run -c ${WORK_DIR}/AdGuardHome.yaml -w $WORK_DIR --pidfile $PID_FILE --no-check-update -l $LOG_FILE"
PREARGS="env TZ=/etc/localtime GOGC=${GOGC} GOMAXPROCS=${GOMAXPROCS} GOMEMLIMIT=${GOMEMLIMIT} QUIC_GO_DISABLE_ECN=true"
PRECMD="{ ulimit -v 1750000; ulimit -m 450000; ulimit -s 8192; } && { if pidof syslog-ng logrotate | wc -w | grep -qE '^[^0]$'; then scribe restart; fi; until pidof $PROCS | grep -qE '.*'; do { killall -9 $(netstat -nlp 2>/dev/null | awk -F/ -v VAR=$PROCS '$0 ~ /.*:53[[:space:]].*/ && $0 !~ VAR {if(!x[$2]++) printf "%s ", $2}') || kill -s 9 $(netstat -nlp 2>/dev/null | awk -v VAR=$PROCS '$0 ~ /.*:53[[:space:]].*/ && $0 !~ VAR {match($7, /[0-9]+/); if (RSTART && !x[$7]++) printf "%s ", substr($7, RSTART, RLENGTH)}'); }; service stop_dnsmasq; done; } &"
POSTCMD="service restart_dnsmasq"
DESC="$PROCS"
PATH="/opt/sbin:/opt/bin:/opt/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
export TZ="$(cat /etc/TZ)"
[ -z "$SCRIPT_LOC" ] && . /jffs/addons/AdGuardHome.d/AdGuardHome.sh

@SomeWhereOverTheRainBow I also noticed it when doing a upgrade of AG, so tried a fresh install but the messages "line 9: nproc: not found" still showing up . Can you check why these messages do appear?
What router model are you running? At first I thought "That option is not available for older legacy model routers (soon to be discontinued models)", so I just changed the command to support the thought of this limitation. The nproc command is actually derived from /opt/bin/nproc which tells me the older kernel entware builds must not have this tool. Either that, or you don't have the coreutils packages installed on entware. I dont recall which was the case, but I do however remember that it is a coreutils package tool and our routers run busy box which typically has only stripped down tools.

change line GOMAXPROCS="$(nproc)" to GOMAXPROCS="$(grep -c "processor" /proc/cpuinfo)".

or rerun update from

curl -L -s -k -O https://raw.githubusercontent.com/jumpsmm7/Asuswrt-Merlin-AdGuardHome-Installer/master/installer && sh installer master update
 
Last edited:
What router model are you running? That option is not available for older legacy model routers (soon to be discontinued models), but I just changed the command to support this limitation. The nproc command is actually derived from /opt/bin/nproc which tells me the older kernel entware builds must not have this tool. Either that, or you don't have the coreutils packages installed on entware. I dont recall which was the case.

change line GOMAXPROCS="$(nproc)" to GOMAXPROCS="$(grep -c "processor" /proc/cpuinfo)".

or rerun update from

curl -L -s -k -O https://raw.githubusercontent.com/jumpsmm7/Asuswrt-Merlin-AdGuardHome-Installer/master/installer && sh installer master update
As mentioned in my signature i am running a AX88u on 388.4.
When checking the directory /opt/bin/ ,i don't see a file called nproc .
For entware i just installed it directly from amtm
Screenshot 2023-11-16 123705.png


Will try your feedback and let you know the outcome.

@SomeWhereOverTheRainBow
Update ; checked both suggested options and they look fine , Thanks:
Code:
 Info:  Writing AdGuardHome configuration...
 Info:  Checking AdGuardHome configuration...
 Info:  Starting AdGuardHome...
 Checking AdGuardHome...              dead.
 Checking AdGuardHome...              alive.
 Info:  Please wait while we perform one last check.
 Checking AdGuardHome...              alive.
 Info:  AdGuardHome setup is complete.
 Info:  Operation completed, returning to Main Menu. You can quit or continue.
 
Last edited:
As mentioned in my signature i am running a AX88u on 388.4.
When checking the directory /opt/bin/ ,i don't see a file called nproc .
For entware i just installed it directly from amtm
View attachment 54241


Will try your feedback and let you know the outcome.

@SomeWhereOverTheRainBow
Update ; checked both suggested options and they look fine , Thanks:
Code:
 Info:  Writing AdGuardHome configuration...
 Info:  Checking AdGuardHome configuration...
 Info:  Starting AdGuardHome...
 Checking AdGuardHome...              dead.
 Checking AdGuardHome...              alive.
 Info:  Please wait while we perform one last check.
 Checking AdGuardHome...              alive.
 Info:  AdGuardHome setup is complete.
 Info:  Operation completed, returning to Main Menu. You can quit or continue.
Yea man, for me it was like 5am and I just woke up when I read your message. I wasn't thinking "let's look at that signature". Instead, I was thinking "coffee, headache medicine, and oh no what else did I break". Hahaha. I am glad it worked for you. On my test environment routers, the one common denominator is they all run entware and the latest firmware, so it took me a second to narrow down the "cause". In this case it was more important to draft a quick and simple solution.
 
@SomeWhereOverTheRainBow Just moved from RT-AC68U to AX86U, having issues with AgH! Looks like everything works fine until I install scribe, it breaks AgH. Just removed scribe & now AgH works fine. Couldn't even see any activity in logs when trying to start AgH manually. AgH works & starts fine after uninstalling scribe. Currently running fine after uninstalling scribe. Didn't have this issue with 68U. Would like to have scribe.
 
Last edited:
@SomeWhereOverTheRainBow Just moved from RT-AC68U to AX86U, having issues with AgH! Looks like everything works fine until I install scribe, it breaks AgH. Just removed scribe & now AgH works fine. Couldn't even see any activity in logs when trying to start AgH manually. AgH works & starts fine after uninstalling scribe. Currently running fine after uninstalling scribe. Didn't have this issue with 68U. Would like to have scribe.
Known incompatibility with scribe. Sorry nothing I can do that is why I no longer use scribe. It is because syslog-ng takes over as log facility and breaks adguardhomes ability to detect the current log facility. Adguardhome will not start in this scenario unless you use your own manual log file (a.k.a not syslog) with agh, or you remove scribe.
 
Just tried, installing scribe first then AgH, still same issue but restarting syslog-ng from scribe menu fixes AgH & I can see in log AgH starting up. Rebooting router breaks AgH again.
 
Known incompatibility with scribe. Sorry nothing I can do that is why I no longer use scribe. It is because syslog-ng takes over as log facility and breaks adguardhomes ability to detect the current log facility. Adguardhome will not start in this scenario unless you use your own manual log file (a.k.a not syslog) with agh, or you remove scribe.
ok thanks will remove scribe, it was good to see logs separately :( Wonder how it has been working fine with scribe until today on my 68U?
 
ok thanks will remove scribe, it was good to see logs separately :( Wonder how it has been working fine with scribe until today on my 68U?
It is probably limited to AX models. Some update down the road may fix the issue, only time will tell. All I can tell you was the issue was the same for the RTAX88U-PRO as well. I tried adding a moderate solution to prearguments where scribe would be restart so AGH would not bug out, but it appears that fix nolonger works.
 
Last edited:
Status
Not open for further replies.

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!
Top