The issue I am facing:
This is my debug log: https://tricorder.pi-hole.net/Finuj6E9/
Details about my system:
What I have changed since installing Pi-hole:
Thank you in advance!
DL6ER
March 19, 2023, 6:59am
2
Your debug log contains no FTL log at all. There is a warning about an almost full disk (30.9 of 31.1 GB) but this is already back from Tuesday. Seems like you have resolved this by now.
At first glance, this looks like gravity-sync is stopping FTL and never restarting it, but evidence is actually not very solid on this. On the contrary, I can did not see any evidence for any crash.
Please send us your pihole-FTL.log after such an incident happened using
tail -n 1000 /var/log/pihole-FTL.log | pihole tricorder
and provide the displayed token for us here.
Hi, the disk being full should be resolved indeed! Here's the log: https://tricorder.pi-hole.net/hrsQt1mf/
DL6ER
March 20, 2023, 6:52pm
4
This log is incompletely empty. Did you run this immediately after the issue or with some delay? If there was a log rotation in between, you'd have needed to upload to FTL.log.1 rotated file. Could you please try again?
It seems like the pi or pihole rebooted and was 'working' again. It has since stopped again, here's the new log: https://tricorder.pi-hole.net/fvuJFSaA/
You new log (fvuJFSaA ) is also empty.
What is the output of ls -la /var/log/pihole/FTL.log?
-rw-r--r-- 1 pihole pihole 0 Mar 20 12:17 /var/log/pihole/FTL.log
What is the output of ls -la /var/log/pihole
That will show the pihole log folder contents and the permissions for the folder itself
dietpi@PiHole2:~$ ls -la /var/log/pihole
total 8
drwxr-xr-x 2 pihole pihole 140 Mar 16 16:40 .
drwxr-xr-t 6 root root 280 Mar 18 09:33 ..
-rw-r--r-- 1 pihole pihole 0 Mar 20 12:17 FTL.log
-rw-r----- 1 pihole pihole 2 Mar 22 00:00 pihole.log
-rw-r----- 1 pihole pihole 2 Mar 21 00:00 pihole.log.1
-rw-r----- 1 root pihole 0 Mar 18 10:17 pihole_debug.log
-rw-r--r-- 1 root root 0 Mar 19 04:17 pihole_updateGravity.log
Edit 2: Can someone else comment on the below (@deHakkelaar ?) – I'm no longer sure if what I've written is correct. The sticky bit is not set on any of my systems' /var/log, but since Pi-hole is logging into a subdirectory owned by the pihole user it's not clear to me if this matters and would be preventing log files from being written. On the one hand it's log files owned by pihole in a subdirectory owned by pihole, on the other hand all that is in a subdirectory of a sticky bit directory owned by root.
@Pintjes best hold off on the below until someone else can advise further.
For some reason your /var/log directory. which is correctly owned by user and group root, has its sticky bit set. This will prevent the pihole user from writing logs. You can unset this with the command
sudo chmod -t /var/log
Then run the command
ls -la /var/log/pihole
again and confirm that the permissions on the line
drwxr-xr-t 6 root root 280 Mar 18 09:33 ..
have changed to
drwxr-xr-x
ie, that final t should now be an x. Then reboot the Pi with
sudo reboot
and once it's back up, go back and run that ls command again and check the permissions on that line still show
drwxr-xr-x
Logging should now be working and you should see FTL.log and pihole.log growing past their current sizes of 0 and 2. Have a look at them and see if they are now starting to contain content.
Finally, create and upload another debug log and post the new URL token
pihole -d -a
Edit: I'm wondering if this is the way that DietPi configures logging, but others have used DietPi and have not reported this. It's easy to put the sticky bit back again if the above breaks something else.
I wasnt sure either so I recreated circumstances without the sticky bit:
pi@ph5b:~ $ sudo mkdir /tmp/log/{,pihole}
pi@ph5b:~ $
pi@ph5b:~ $ sudo chown pihole: /tmp/log/pihole
pi@ph5b:~ $
pi@ph5b:~ $ umask 0122
pi@ph5b:~ $
pi@ph5b:~ $ sudo -u pihole touch /tmp/log/pihole/FTL.log
pi@ph5b:~ $
pi@ph5b:~ $ ll /tmp/log/pihole
total 8
drwxr-xr-x 2 pihole pihole 4096 Mar 23 11:49 .
drwxr-xr-x 3 root root 4096 Mar 23 11:37 ..
-rw-r--r-- 1 pihole pihole 0 Mar 23 11:49 FTL.log
And after adding the sticky bit, I was still able to create a log file:
pi@ph5b:~ $ sudo chmod +t /tmp/log/
pi@ph5b:~ $
pi@ph5b:~ $ sudo -u pihole touch /tmp/log/pihole/FTL.log.2
pi@ph5b:~ $
pi@ph5b:~ $ ll /tmp/log/pihole
total 8
drwxr-xr-x 2 pihole pihole 4096 Mar 23 11:59 .
drwxr-xr-t 3 root root 4096 Mar 23 11:58 ..
-rw-r--r-- 1 pihole pihole 0 Mar 23 11:59 FTL.log
-rw-r--r-- 1 pihole pihole 0 Mar 23 11:59 FTL.log.2
@MichaIng , is that sticky bit intended and do you have any idea whats happening?
@Pintjes , does below show any errors/warnings concerning the logs?
journalctl --full --no-pager -b -u pihole-FTL
No errors as far as I can see...
This is the output:
dietpi@PiHole2:~$ sudo journalctl --full --no-pager -b -u pihole-FTL
-- Logs begin at Wed 2023-03-15 15:08:30 GMT, end at Thu 2023-03-23 13:00:27 GMT. --
Mar 15 15:08:32 PiHole2 systemd[1]: Starting Pi-hole FTL...
Mar 15 15:08:32 PiHole2 systemd[1]: Started Pi-hole FTL.
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.065 319M] Using log file /var/log/pihole/FTL.log
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.065 319M] ########## FTL started on PiHole2! ##########
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.065 319M] FTL branch: master
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.065 319M] FTL version: v5.21
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.065 319M] FTL commit: f380afdaMar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.065 319M] FTL date: 2023-02-10 18:55:28 +0000
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.065 319M] FTL user: pihole
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.065 319M] Compiled for armv7hf (compiled on CI) using arm-linux-gnueabihf-gcc (Debian 8.3.0-2) 8.3.0
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.065 319M] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.065 319M] SOCKET_LISTENING: only local
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.065 319M] AAAA_QUERY_ANALYSIS: Show AAAA queries
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.065 319M] MAXDBDAYS: max age for stored queries is 365 days
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.065 319M] RESOLVE_IPV6: Resolve IPv6 addresses
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.065 319M] RESOLVE_IPV4: Resolve IPv4 addresses
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.065 319M] DBINTERVAL: saving to DB file every minute
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.066 319M] DBFILE: Using /etc/pihole/pihole-FTL.db
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.066 319M] MAXLOGAGE: Importing up to 24.0 hours of log data
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.066 319M] PRIVACYLEVEL: Set to 0
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.066 319M] IGNORE_LOCALHOST: Show queries from localhost
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.066 319M] BLOCKINGMODE: Pi-hole's IP + NODATA-IPv6 for blocked domains
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.066 319M] ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.066 319M] DBIMPORT: Importing history from database
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.066 319M] PIDFILE: Using /run/pihole-FTL.pid
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.066 319M] SOCKETFILE: Using /run/pihole/FTL.sock
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.066 319M] SETUPVARSFILE: Using /etc/pihole/setupVars.conf
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.066 319M] MACVENDORDB: Using /etc/pihole/macvendor.db
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.066 319M] GRAVITYDB: Using /etc/pihole/gravity.db
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.066 319M] PARSE_ARP_CACHE: Active
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.066 319M] CNAME_DEEP_INSPECT: Active
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.066 319M] DELAY_STARTUP: No delay requested.
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.066 319M] BLOCK_ESNI: Enabled, blocking _esni.{blocked domain}
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.066 319M] NICE: Set process niceness to -10 (default)
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.067 319M] MAXNETAGE: Removing IP addresses and host names from network table after 365 days
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.067 319M] NAMES_FROM_NETDB: Enabled, trying to get names from network database
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.067 319M] EDNS0_ECS: Overwrite client from ECS information
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.067 319M] REFRESH_HOSTNAMES: Periodically refreshing IPv4 names
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.067 319M] RATE_LIMIT: Rate-limiting client making more than 10000 queries in 60 seconds
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.067 319M] LOCAL_IPV4: Automatic interface-dependent detection of address
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.067 319M] LOCAL_IPV6: Automatic interface-dependent detection of address
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.067 319M] BLOCK_IPV4: Automatic interface-dependent detection of address
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.067 319M] BLOCK_IPV6: Automatic interface-dependent detection of address
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.067 319M] SHOW_DNSSEC: Enabled, showing automatically generated DNSSEC queries
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.067 319M] MOZILLA_CANARY: Enabled
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.067 319M] PIHOLE_PTR: internal PTR generation enabled (pi.hole)
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.067 319M] ADDR2LINE: Enabled
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.067 319M] REPLY_WHEN_BUSY: Drop queries when the database is busy
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.067 319M] BLOCK_TTL: 2 seconds
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.067 319M] BLOCK_ICLOUD_PR: Enabled
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.067 319M] CHECK_LOAD: Enabled
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.067 319M] CHECK_SHMEM: Warning if shared-memory usage exceeds 90%
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.067 319M] CHECK_DISK: Warning if certain disk usage exceeds 90%
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.068 319M] Finished config file parsing
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15 15:08:33.068 319M] Creating mutex
Mar 15 15:08:33 PiHole2 pihole-FTL[319]: [2023-03-15
Mar 16 13:12:10 PiHole2 systemd[1]: pihole-FTL.service: Succeeded.
Mar 19 03:47:49 PiHole2 systemd[1]: Starting Pi-hole FTL...
Mar 19 03:47:49 PiHole2 systemd[1]: Started Pi-hole FTL.
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.852 11257M] Using log file /var/log/pihole/FTL.log
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.852 11257M] ########## FTL started on PiHole2! ##########
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.852 11257M] FTL branch: master
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.852 11257M] FTL version: v5.21
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.852 11257M] FTL commit: f380afda
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.852 11257M] FTL date: 2023-02-10 18:55:28 +0000
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.853 11257M] FTL user: piholeMar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.853 11257M] Compiled for armv7hf (compiled on CI) using arm-linux-gnueabihf-gcc (Debian 8.3.0-2) 8.3.0
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.853 11257M] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.853 11257M] SOCKET_LISTENING: only local
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.853 11257M] AAAA_QUERY_ANALYSIS: Show AAAA queries
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.853 11257M] MAXDBDAYS: max age for stored queries is 365 days
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.853 11257M] RESOLVE_IPV6: Resolve IPv6 addresses
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.853 11257M] RESOLVE_IPV4: Resolve IPv4 addresses
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.853 11257M] DBINTERVAL: saving to DB file every minute
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.853 11257M] DBFILE: Using /etc/pihole/pihole-FTL.db
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.853 11257M] MAXLOGAGE: Importing up to 24.0 hours of log data
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.853 11257M] PRIVACYLEVEL: Set to 0
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.853 11257M] IGNORE_LOCALHOST: Show queries from localhost
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.853 11257M] BLOCKINGMODE: Pi-hole's IP + NODATA-IPv6 for blocked domains
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.853 11257M] ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.853 11257M] DBIMPORT: Importing history from database
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.853 11257M] PIDFILE: Using /run/pihole-FTL.pid
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.853 11257M] SOCKETFILE: Using /run/pihole/FTL.sock
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.853 11257M] SETUPVARSFILE: Using /etc/pihole/setupVars.conf
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.853 11257M] MACVENDORDB: Using /etc/pihole/macvendor.db
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.853 11257M] GRAVITYDB: Using /etc/pihole/gravity.db
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.854 11257M] PARSE_ARP_CACHE: Active
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.854 11257M] CNAME_DEEP_INSPECT: Active
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.854 11257M] DELAY_STARTUP: No delay requested.
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.854 11257M] BLOCK_ESNI: Enabled, blocking _esni.{blocked domain}
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.854 11257M] NICE: Set process niceness to -10 (default)
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.854 11257M] MAXNETAGE: Removing IP addresses and host names from network table after 365 days
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.854 11257M] NAMES_FROM_NETDB: Enabled, trying to get names from network database
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.854 11257M] EDNS0_ECS: Overwrite client from ECS information
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.854 11257M] REFRESH_HOSTNAMES: Periodically refreshing IPv4 names
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.854 11257M] RATE_LIMIT: Rate-limiting client making more than 10000 queries in 60 seconds
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.854 11257M] LOCAL_IPV4: Automatic interface-dependent detection of address
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.854 11257M] LOCAL_IPV6: Automatic interface-dependent detection of address
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.854 11257M] BLOCK_IPV4: Automatic interface-dependent detection of address
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.854 11257M] BLOCK_IPV6: Automatic interface-dependent detection of address
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.854 11257M] SHOW_DNSSEC: Enabled, showing automatically generated DNSSEC queries
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.854 11257M] MOZILLA_CANARY: Enabled
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.854 11257M] PIHOLE_PTR: internal PTR generation enabled (pi.hole)
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.854 11257M] ADDR2LINE: Enabled
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.854 11257M] REPLY_WHEN_BUSY: Drop queries when the database is busy
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.854 11257M] BLOCK_TTL: 2 seconds
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.854 11257M] BLOCK_ICLOUD_PR: Enabled
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.855 11257M] CHECK_LOAD: Enabled
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.855 11257M] CHECK_SHMEM: Warning if shared-memory usage exceeds 90%
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:47:49.855 11257M] CHECK_DISK: Warning if certain disk usage exceeds 90%
Mar 19 03:47:49 PiHole2 pihole-FTL[11257]: [2023-03-19 03:
Mar 20 12:11:25 PiHole2 systemd[1]: pihole-FTL.service: Succeeded.
Indeed we set the sticky bit when RAM logging is enabled, actually not sure why. However, it does not break logging (otherwise all non-root applications in DietPi would be broken since it exists
However, is RAM logging even enabled? We use 1777 mode for the mount and above I see that /var/log has 1755 mode.
findmnt /var/log
I'll remove the mode change for the RAM logging mount, it does not make sense and does not match the default. Was there since before I joined DietPi.
Thanks for testing it and to @MichaIng for the extra info. I also tested with the sticky bit set and was also able to continue logging into pihole-owned logs, but hadn't restarted the logging so wasn't sure if that mattered. Looks like it doesn't matter at all here.
@Pintjes where is your problem at now, no change? Is there anything log-related on the DietPi forum which might offer any clues?
Sadly no change, kinda hard to debug when you have 0 logs... I can only imagine it has something to do with gravity sync as that's the only difference it has with my other pihole (that works as intended)... I've tried searching on gravity sync's github to see if there were any similar issues but also no luck.
Have you tried to manually update the gravity database? Not so uncommon that faulty entries lead to issues.
You can also disable RAM logging if you need permanent/older logs, and may re-enable it after the issue has been solved. In dietpi-software select logging system and None. The wording is a bit misleading: "None" does not disable logging completely but just removes the tmpfs (RAM disk) from /var/log so that logs are done to disk, without installing rsyslog for plain text system logs (which are anyway done to journal / journalctl in any case).
I think I actually found the problem whilst trying to manual update gravity. It threw an out of storage error, seems like gravity sync isn't respecting the backup retention I setup and spams backups.
system
April 15, 2023, 4:49pm
19
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.
). It means that only the owner of a file/directory can remove it, but does not limit permissions to create files or directories. It is a common measure for world-writable directories.