jacklul
Senior Member
Did you follow the installation guide, specifically for Merlin firmware?I did and it wouldnt let me change it back to 53. Said it was in use, could that have been because I have unbound installed before pihole?
Did you follow the installation guide, specifically for Merlin firmware?I did and it wouldnt let me change it back to 53. Said it was in use, could that have been because I have unbound installed before pihole?
I will try it again.Did you follow the installation guide, specifically for Merlin firmware?
admin@RT-AC86U-9988:/# ps wT | grep pihole
3209 pihole 109m S < pihole-FTL
13000 pihole 109m S < {database} pihole-FTL
13001 pihole 109m S < {housekeeper} pihole-FTL
13002 pihole 109m S < {dns-client} pihole-FTL
13003 pihole 109m S < {timer} pihole-FTL
13004 pihole 109m S < {webserver} pihole-FTL
13016 pihole 109m S N {civetweb-timer} pihole-FTL
13017 pihole 109m S N {civetweb-master} pihole-FTL
898995 pihole 109m S N {civetweb-worker} pihole-FTL
898996 pihole 109m S N {civetweb-worker} pihole-FTL
898998 pihole 109m S N {civetweb-worker} pihole-FTL
898999 pihole 109m S N {civetweb-worker} pihole-FTL
1112602 admin 5980 S grep pihole
admin@RT-AC86U-9988:/#
How long have you been running it? Maybe there is memory leak somewhere again.@jacklul
It seems the latest version wants quite a bit more memory, compared to the earlier one:
Code:admin@RT-AC86U-9988:/# ps wT | grep pihole 3209 pihole 109m S < pihole-FTL 13000 pihole 109m S < {database} pihole-FTL 13001 pihole 109m S < {housekeeper} pihole-FTL 13002 pihole 109m S < {dns-client} pihole-FTL 13003 pihole 109m S < {timer} pihole-FTL 13004 pihole 109m S < {webserver} pihole-FTL 13016 pihole 109m S N {civetweb-timer} pihole-FTL 13017 pihole 109m S N {civetweb-master} pihole-FTL 898995 pihole 109m S N {civetweb-worker} pihole-FTL 898996 pihole 109m S N {civetweb-worker} pihole-FTL 898998 pihole 109m S N {civetweb-worker} pihole-FTL 898999 pihole 109m S N {civetweb-worker} pihole-FTL 1112602 admin 5980 S grep pihole admin@RT-AC86U-9988:/#
#!/bin/sh
pid_file="$(pihole-FTL --config files.pid 2> /dev/null)"
sigrtmin="$(pihole-FTL sigrtmin 2> /dev/null)"
kill -$((sigrtmin + 5)) "$(cat "$pid_file")"
kill -$((sigrtmin + 4)) "$(cat "$pid_file")"
It does not take much for memory to skyrocket:How long have you been running it? Maybe there is memory leak somewhere again.
In FTL v6.3 dev version there was a memory leak that I reported and it got fixed.
admin@RT-AC86U-9988:/tmp/mnt/ac86u/entware/var/log# /opt/etc/init.d/S65pihole-FTL restart
Shutting down pihole-FTL... done.
Starting pihole-FTL... done.
admin@RT-AC86U-9988:/tmp/mnt/ac86u/entware/var/log# ps wT | grep pihole
1112433 pihole 36132 S < pihole-FTL
1112521 pihole 36132 S < {database} pihole-FTL
1112522 pihole 36132 S < {housekeeper} pihole-FTL
1112523 pihole 36132 S < {dns-client} pihole-FTL
1112524 pihole 36132 S < {timer} pihole-FTL
1112525 pihole 36132 S < {webserver} pihole-FTL
1112526 pihole 36132 S N {civetweb-timer} pihole-FTL
1112527 pihole 36132 S N {civetweb-master} pihole-FTL
1112589 admin 1184 D grep pihole
admin@RT-AC86U-9988:/tmp/mnt/ac86u/entware/var/log# ps wT | grep pihole
1112433 pihole 104m S < pihole-FTL
1112521 pihole 104m S < {database} pihole-FTL
1112522 pihole 104m S < {housekeeper} pihole-FTL
1112523 pihole 104m S < {dns-client} pihole-FTL
1112524 pihole 104m S < {timer} pihole-FTL
1112525 pihole 104m S < {webserver} pihole-FTL
1112526 pihole 104m S N {civetweb-timer} pihole-FTL
1112527 pihole 104m S N {civetweb-master} pihole-FTL
admin@RT-AC86U-9988:/tmp/mnt/ac86u/entware/var/log# ps wT | grep pihole
1112433 pihole 104m S < pihole-FTL
1112521 pihole 104m S < {database} pihole-FTL
1112522 pihole 104m S < {housekeeper} pihole-FTL
1112523 pihole 104m S < {dns-client} pihole-FTL
1112524 pihole 104m S < {timer} pihole-FTL
1112525 pihole 104m S < {webserver} pihole-FTL
1112526 pihole 104m S N {civetweb-timer} pihole-FTL
1112527 pihole 104m S N {civetweb-master} pihole-FTL
1218617 admin 5980 D grep pihole
admin@RT-AC86U-9988:/tmp/mnt/ac86u/entware/var/log# cat /jffs/scripts/pihole39
#!/bin/sh
pid_file="$(pihole-FTL --config files.pid 2> /dev/null)"
sigrtmin="$(pihole-FTL sigrtmin 2> /dev/null)"
kill -$((sigrtmin + 5)) "$(cat "$pid_file")"
kill -$((sigrtmin + 4)) "$(cat "$pid_file")"
admin@RT-AC86U-9988:/tmp/mnt/ac86u/entware/var/log# /jffs/scripts/pihole39
admin@RT-AC86U-9988:/tmp/mnt/ac86u/entware/var/log# ps wT | grep pihole
1112433 pihole 104m S < pihole-FTL
1112521 pihole 104m S < {database} pihole-FTL
1112522 pihole 104m S < {housekeeper} pihole-FTL
1112523 pihole 104m S < {dns-client} pihole-FTL
1112524 pihole 104m S < {timer} pihole-FTL
1112525 pihole 104m S < {webserver} pihole-FTL
1112526 pihole 104m S N {civetweb-timer} pihole-FTL
1112527 pihole 104m S N {civetweb-master} pihole-FTL
1219434 admin 5980 S grep pihole
admin@RT-AC86U-9988:/tmp/mnt/ac86u/entware/var/log# ps wT |grep pihole
1112433 pihole 104m S < pihole-FTL
1112521 pihole 104m S < {database} pihole-FTL
1112522 pihole 104m S < {housekeeper} pihole-FTL
1112523 pihole 104m S < {dns-client} pihole-FTL
1112524 pihole 104m S < {timer} pihole-FTL
1112525 pihole 104m S < {webserver} pihole-FTL
1112526 pihole 104m S N {civetweb-timer} pihole-FTL
1112527 pihole 104m S N {civetweb-master} pihole-FTL
1230019 admin 1184 D grep pihole
admin@RT-AC86U-9988:/tmp/mnt/ac86u/entware/var/log# killall -SIGHUP pihole-FTL
admin@RT-AC86U-9988:/tmp/mnt/ac86u/entware/var/log# ps wT |grep pihole
1112433 pihole 104m S < pihole-FTL
1112521 pihole 104m S < {database} pihole-FTL
1112522 pihole 104m S < {housekeeper} pihole-FTL
1112523 pihole 104m S < {dns-client} pihole-FTL
1112524 pihole 104m S < {timer} pihole-FTL
1112525 pihole 104m S < {webserver} pihole-FTL
1112526 pihole 104m S N {civetweb-timer} pihole-FTL
1112527 pihole 104m S N {civetweb-master} pihole-FTL
1231843 admin 5980 S grep pihole
2025-11-24 10:37:11.395 CST [3472/T11431] WARNING: Long-term load (15min avg) larger than number of processors: 2.7 > 2
2025-11-24 10:38:11.741 CST [3472M] INFO: Asked to terminate by "killall pihole-FTL" (PID 1112292, user admin UID 0)
2025-11-24 10:38:11.815 CST [3472/T11430] INFO: Terminating database thread
2025-11-24 10:38:11.855 CST [3472/T11433] INFO: Terminating timer thread
2025-11-24 10:38:12.219 CST [3472M] INFO: Finished final database update
2025-11-24 10:38:12.220 CST [3472M] INFO: Waiting for threads to join
2025-11-24 10:38:12.221 CST [3472M] INFO: Thread housekeeper (1) is idle, terminating it.
2025-11-24 10:38:12.221 CST [3472M] INFO: Thread dns-client (2) is idle, terminating it.
2025-11-24 10:38:12.221 CST [3472M] INFO: Thread webserver (7) is idle, terminating it.
2025-11-24 10:38:12.223 CST [3472M] INFO: All threads joined
2025-11-24 10:38:12.255 CST [3472M] INFO: PID file emptied
2025-11-24 10:38:12.270 CST [3472M] INFO: Stored 0 API sessions in the database
2025-11-24 10:38:13.474 CST [3472M] INFO: ########## FTL terminated after 6h 31m 21s (code 0)! ##########
2025-11-24 10:38:14.072 CST [1112402M] INFO: ########## FTL started on RT-AC86U-9988! ##########
2025-11-24 10:38:14.073 CST [1112402M] INFO: FTL branch: master
2025-11-24 10:38:14.073 CST [1112402M] INFO: FTL version: v6.3.3
2025-11-24 10:38:14.073 CST [1112402M] INFO: FTL commit: a0186fd4
2025-11-24 10:38:14.073 CST [1112402M] INFO: FTL date: 2025-11-04 20:18:48 +0100
2025-11-24 10:38:14.073 CST [1112402M] INFO: FTL user: pihole
2025-11-24 10:38:14.073 CST [1112402M] INFO: Compiled for linux/arm64/v8 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-11-24 10:38:14.086 CST [1112402M] INFO: Wrote config file:
2025-11-24 10:38:14.086 CST [1112402M] INFO: - 161 total entries
2025-11-24 10:38:14.087 CST [1112402M] INFO: - 147 entries are default
2025-11-24 10:38:14.087 CST [1112402M] INFO: - 14 entries are modified
2025-11-24 10:38:14.087 CST [1112402M] INFO: - 0 entries are forced through environment
2025-11-24 10:38:14.116 CST [1112402M] INFO: Parsed config file /opt/etc/pihole/pihole.toml successfully
2025-11-24 10:38:14.116 CST [1112402M] INFO: PID file does not exist or not readable
2025-11-24 10:38:14.116 CST [1112402M] INFO: No other running FTL process found.
2025-11-24 10:38:14.119 CST [1112402M] INFO: PID of FTL process: 1112402
2025-11-24 10:38:14.142 CST [1112402M] INFO: listening on 192.168.1.20 port 53
2025-11-24 10:38:14.143 CST [1112402M] INFO: listening on br0(#19): 192.168.1.20 port 53
2025-11-24 10:38:14.146 CST [1112433M] INFO: PID of FTL process: 1112433
2025-11-24 10:38:14.154 CST [1112433M] INFO: Database version is 21
2025-11-24 10:38:14.185 CST [1112433M] INFO: Database successfully initialized
2025-11-24 10:38:16.558 CST [1112433M] INFO: Imported 48386 queries from the on-disk database (it has 3516806 rows)
2025-11-24 10:38:16.565 CST [1112433M] INFO: Parsing queries in database
2025-11-24 10:38:16.691 CST [1112433M] INFO: 10000 queries parsed...
2025-11-24 10:38:16.807 CST [1112433M] INFO: 20000 queries parsed...
2025-11-24 10:38:16.925 CST [1112433M] INFO: 30000 queries parsed...
2025-11-24 10:38:17.085 CST [1112433M] INFO: 40000 queries parsed...
2025-11-24 10:38:17.187 CST [1112433M] INFO: Imported 48386 queries from the long-term database
2025-11-24 10:38:17.187 CST [1112433M] INFO: -> Total DNS queries: 48386
2025-11-24 10:38:17.187 CST [1112433M] INFO: -> Cached DNS queries: 14423
2025-11-24 10:38:17.187 CST [1112433M] INFO: -> Forwarded DNS queries: 9216
2025-11-24 10:38:17.187 CST [1112433M] INFO: -> Blocked DNS queries: 24447
2025-11-24 10:38:17.187 CST [1112433M] INFO: -> Unknown DNS queries: 0
2025-11-24 10:38:17.187 CST [1112433M] INFO: -> Unique domains: 2982
2025-11-24 10:38:17.187 CST [1112433M] INFO: -> Unique clients: 16
2025-11-24 10:38:17.187 CST [1112433M] INFO: -> DNS cache records: 1044
2025-11-24 10:38:17.187 CST [1112433M] INFO: -> Known forward destinations: 1
2025-11-24 10:38:17.734 CST [1112433M] INFO: NTP sync is disabled
2025-11-24 10:38:17.734 CST [1112433M] INFO: FTL is running as user pihole (UID 502)
2025-11-24 10:38:17.734 CST [1112433/T1112522] WARNING: Long-term load (15min avg) larger than number of processors: 2.8 > 2
2025-11-24 10:38:17.742 CST [1112433M] INFO: Reading certificate from /opt/etc/pihole/tls.pem ...
2025-11-24 10:38:17.760 CST [1112433M] INFO: Using SSL/TLS certificate file /opt/etc/pihole/tls.pem
2025-11-24 10:38:17.782 CST [1112433M] INFO: Web server ports:
2025-11-24 10:38:17.782 CST [1112433M] INFO: - 127.0.0.1:5080 (HTTP, IPv4, OK)
2025-11-24 10:38:17.782 CST [1112433M] INFO: - 192.168.1.20:80 (HTTP, IPv4, OK)
2025-11-24 10:38:17.782 CST [1112433M] INFO: - 192.168.1.20:5443 (HTTPS, IPv4, OK)
2025-11-24 10:38:17.811 CST [1112433M] INFO: Restored 0 API sessions from the database
2025-11-24 10:38:17.815 CST [1112433M] INFO: Blocking status is enabled
2025-11-24 10:38:17.891 CST [1112433/T1112521] INFO: Compiled 0 allow and 25 deny regex for 16 clients in 34.5 msec
2025-11-24 10:43:17.295 CST [1112433/T1112522] WARNING: Long-term load (15min avg) larger than number of processors: 2.7 > 2
2025-11-24 10:48:17.475 CST [1112433/T1112522] WARNING: Long-term load (15min avg) larger than number of processors: 2.7 > 2
2025-11-24 10:53:17.475 CST [1112433/T1112522] WARNING: Long-term load (15min avg) larger than number of processors: 2.7 > 2
2025-11-24 11:20:26.372 CST [1112433M] INFO: Flushing cache and re-reading config
2025-11-24 11:20:26.388 CST [1112433M] INFO: Blocking status is enabled
2025-11-24 11:20:26.504 CST [1112433/T1112521] INFO: Compiled 0 allow and 25 deny regex for 16 clients in 49.0 msec
What are the sizes of gravity.db and pihole-FTL.db?
admin@RT-AC86U-9988:/tmp/mnt/ac86u/entware/etc/pihole# ls -lta *.db
-rw-r----- 1 pihole pihole 227610624 Nov 24 12:29 pihole-FTL.db
-rw-r----- 1 pihole pihole 6344704 Nov 23 09:43 gravity.db
-rw-r----- 1 pihole pihole 13426688 Nov 13 10:15 gravity_old.db
-rw-r----- 1 pihole pihole 3387392 Nov 6 11:32 macvendor.db
That's a good point. How do I shrink it?That memory usage could be caused by the size of pihole-FTL.db, for comparison mine is around 65M and I keep only last 30 days of queries in it.

Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!