Adblock service keeps stop?

Can't figure out why the adblock service stopped but there is no error to bring up the adblock services.
my dns running is dnsmasq on port 53, i have dnsmasq/stubby tls running on 5453,
Not sure if this error happened after I installed stubby tls.
Any advice?

root@r6220:/etc/config# service adblock start
root@r6220:/etc/config#
root@r6220:/etc/config# service
Usage: service <service> [command]
/etc/init.d/adblock                enabled         stopped
root@r6220:/etc/config# service adblock status
::: adblock runtime information
  + adblock_status  : enabled
  + adblock_version : 4.1.5
  + blocked_domains : 221899
  + active_sources  : adaway, adguard, adguard_tracking, android_tracking, anti_ad, disconnect, easylist, easyprivacy, o
                      penphish, phishing_army, reg_cn, spam404, winspy, yoyo
  + dns_backend     : dnsmasq (-), /tmp/dnsmasq.d
  + run_utils       : download: /bin/uclient-fetch, sort: /usr/libexec/sort-coreutils, awk: /bin/busybox
  + run_ifaces      : trigger: -, report: br-lan
  + run_directories : base: /tmp, backup: /etc/adblock, report: /tmp/adblock-Report, jail: /tmp
  + run_flags       : backup: ✔, flush: ✔, force: ✘, search: ✘, report: ✔, mail: ✘, jail: ✘
  + last_run        : reload, 3m 23s, 120/48/34, 2022-10-23T02:19:24+08:00
  + system          : Netgear R6220, OpenWrt 22.03.2 r19803-9a599fee93
root@r6220:/etc/config#
Sun Oct 23 00:53:15 2022 user.info adblock-4.1.5[1689]: report directory '/tmp/adblock-Report' created
Sun Oct 23 00:53:15 2022 user.info adblock-4.1.5[1689]: adblock instance started ::: action: start, priority: 0, pid: 1689
Sun Oct 23 01:08:31 2022 user.info adblock-4.1.5[8710]: adblock instance started ::: action: start, priority: 0, pid: 8710
Sun Oct 23 01:09:24 2022 user.info adblock-4.1.5[8710]: blocklist with overall 158709 blocked domains loaded successfully (Netgear R6220, OpenWrt 22.03.2 r19803-9a599fee93)
Sun Oct 23 01:10:31 2022 user.info adblock-4.1.5[11257]: adblock instance started ::: action: reload, priority: 0, pid: 11257
Sun Oct 23 01:13:59 2022 user.info adblock-4.1.5[11257]: blocklist with overall 212717 blocked domains loaded successfully (Netgear R6220, OpenWrt 22.03.2 r19803-9a599fee93)
Sun Oct 23 01:36:57 2022 user.info adblock-4.1.5[15982]: adblock instance started ::: action: reload, priority: 0, pid: 15982
Sun Oct 23 01:40:06 2022 user.info adblock-4.1.5[15982]: blocklist with overall 212717 blocked domains loaded successfully (Netgear R6220, OpenWrt 22.03.2 r19803-9a599fee93)
Sun Oct 23 01:41:48 2022 user.info adblock-4.1.5[18259]: adblock instance started ::: action: start, priority: 0, pid: 18259
Sun Oct 23 01:42:57 2022 user.info adblock-4.1.5[18259]: blocklist with overall 212717 blocked domains loaded successfully (Netgear R6220, OpenWrt 22.03.2 r19803-9a599fee93)
Sun Oct 23 01:46:15 2022 user.info adblock-4.1.5[20098]: adblock instance started ::: action: reload, priority: 0, pid: 20098
Sun Oct 23 01:49:37 2022 user.info adblock-4.1.5[20098]: blocklist with overall 219465 blocked domains loaded successfully (Netgear R6220, OpenWrt 22.03.2 r19803-9a599fee93)
Sun Oct 23 02:01:21 2022 user.info adblock-4.1.5[23239]: adblock instance started ::: action: start, priority: 0, pid: 23239
Sun Oct 23 02:02:35 2022 user.info adblock-4.1.5[23239]: blocklist with overall 219465 blocked domains loaded successfully (Netgear R6220, OpenWrt 22.03.2 r19803-9a599fee93)
Sun Oct 23 02:16:01 2022 user.info adblock-4.1.5[27427]: adblock instance started ::: action: reload, priority: 0, pid: 27427
Sun Oct 23 02:19:25 2022 user.info adblock-4.1.5[27427]: blocklist with overall 221899 blocked domains loaded successfully (Netgear R6220, OpenWrt 22.03.2 r19803-9a599fee93)

The actual blocking is done by dnamasq/unbound, adblock just downloads and prepares the block-list for the dnsmasq/unbound, so once it's been done, there are no instances of adblock active and the service command reports adblock stopped.

@dibdot can correct me if I'm wrong.

If you do not see anything in the log, does it mean the AdBlock stopped working?

No, it just means that there are no adblock related log messages in the log buffer (by default 64k). Hit the reload button and you should see logs from current adblock run....

Also, if you're already logged into the router, do ls -laF /var/dnsmasq.d and look at the age of the generated list. This is what I do to confirm my cron job timing, if I don't see anything in the log because something flooded it out.

Correct me if I am wrong, that said, the adblocker is to download or populate the block list to the local DNS for the block task, as long as the filter lists are available, therefore the AdBlock service could be stopped after AdBlock download process completed.

1 Like