ERROR - Pi-Hole stopped working properly on 5/22/2025

Help
1

Expected Behaviour:

It should show me the filtering, and all the data in each of the sections within "Group Management", within the sidebar.

  • Operating System: Debian 12
  • Hardware: Raspberry Pi 3B

Actual Behaviour:

Starting today, May 22, 2025, Pi-Hole started showing me this problem, which I attach in the photos. All the values ​​in the "Group Management" sidebar are returning negative numbers. The "pihole -d" diagnostic shows all the values ​​I had configured, but the web service presents this problem.

Debug Token:

Token: nMjgQSpn

Log fragments where diagnostic errors are generated:

e[95m*** [ DIAGNOSING ]:e[0m contents of e[96m/var/log/piholee[0m

e[32m-rw-r----- 1 pihole pihole 2.9M May 22 12:19 /var/log/pihole/FTL.loge[0m
   e[96m-----head of FTL.log------e[0m
   2025-05-22 00:00:19.006 CEST [705/T1218] ERROR: SQLite3: no such table: info in "SELECT value FROM info WHERE property = 'updated';" (1)
   2025-05-22 00:00:19.045 CEST [705/T1218] WARNING: gravity_updated(): SELECT value FROM info WHERE property = 'updated'; - SQL error prepare: SQL logic error
   2025-05-22 00:00:20.049 CEST [705/T1218] ERROR: SQLite3: no such table: info in "SELECT value FROM info WHERE property = 'updated';" (1)
   2025-05-22 00:00:20.050 CEST [705/T1218] WARNING: gravity_updated(): SELECT value FROM info WHERE property = 'updated'; - SQL error prepare: SQL logic error
   2025-05-22 00:00:21.055 CEST [705/T1218] ERROR: SQLite3: no such table: info in "SELECT value FROM info WHERE property = 'updated';" (1)
   2025-05-22 00:00:21.056 CEST [705/T1218] WARNING: gravity_updated(): SELECT value FROM info WHERE property = 'updated'; - SQL error prepare: SQL logic error
   2025-05-22 00:00:22.060 CEST [705/T1218] ERROR: SQLite3: no such table: info in "SELECT value FROM info WHERE property = 'updated';" (1)
   2025-05-22 00:00:22.061 CEST [705/T1218] WARNING: gravity_updated(): SELECT value FROM info WHERE property = 'updated'; - SQL error prepare: SQL logic error
   2025-05-22 00:00:23.066 CEST [705/T1218] ERROR: SQLite3: no such table: info in "SELECT value FROM info WHERE property = 'updated';" (1)
   2025-05-22 00:00:23.067 CEST [705/T1218] WARNING: gravity_updated(): SELECT value FROM info WHERE property = 'updated'; - SQL error prepare: SQL logic error
   2025-05-22 00:00:24.071 CEST [705/T1218] ERROR: SQLite3: no such table: info in "SELECT value FROM info WHERE property = 'updated';" (1)
   2025-05-22 00:00:24.072 CEST [705/T1218] WARNING: gravity_updated(): SELECT value FROM info WHERE property = 'updated'; - SQL error prepare: SQL logic error
   2025-05-22 00:00:25.079 CEST [705/T1218] ERROR: SQLite3: no such table: info in "SELECT value FROM info WHERE property = 'updated';" (1)
   2025-05-22 00:00:25.080 CEST [705/T1218] WARNING: gravity_updated(): SELECT value FROM info WHERE property = 'updated'; - SQL error prepare: SQL logic error
   2025-05-22 00:00:26.087 CEST [705/T1218] ERROR: SQLite3: no such table: info in "SELECT value FROM info WHERE property = 'updated';" (1)
   2025-05-22 00:00:26.088 CEST [705/T1218] WARNING: gravity_updated(): SELECT value FROM info WHERE property = 'updated'; - SQL error prepare: SQL logic error
   2025-05-22 00:00:27.094 CEST [705/T1218] ERROR: SQLite3: no such table: info in "SELECT value FROM info WHERE property = 'updated';" (1)
   2025-05-22 00:00:27.095 CEST [705/T1218] WARNING: gravity_updated(): SELECT value FROM info WHERE property = 'updated'; - SQL error prepare: SQL logic error
   2025-05-22 00:00:28.003 CEST [705/T1218] ERROR: SQLite3: no such table: info in "SELECT value FROM info WHERE property = 'updated';" (1)
   2025-05-22 00:00:28.003 CEST [705/T1218] WARNING: gravity_updated(): SELECT value FROM info WHERE property = 'updated'; - SQL error prepare: SQL logic error
   2025-05-22 00:00:29.010 CEST [705/T1218] ERROR: SQLite3: no such table: info in "SELECT value FROM info WHERE property = 'updated';" (1)
   2025-05-22 00:00:29.011 CEST [705/T1218] WARNING: gravity_updated(): SELECT value FROM info WHERE property = 'updated'; - SQL error prepare: SQL logic error
   2025-05-22 00:00:30.018 CEST [705/T1218] ERROR: SQLite3: no such table: info in "SELECT value FROM info WHERE property = 'updated';" (1)
   2025-05-22 00:00:30.019 CEST [705/T1218] WARNING: gravity_updated(): SELECT value FROM info WHERE property = 'updated'; - SQL error prepare: SQL logic error
   2025-05-22 00:00:31.025 CEST [705/T1218] ERROR: SQLite3: no such table: info in "SELECT value FROM info WHERE property = 'updated';" (1)
   2025-05-22 00:00:31.026 CEST [705/T1218] WARNING: gravity_updated(): SELECT value FROM info WHERE property = 'updated'; - SQL error prepare: SQL logic error
   2025-05-22 00:00:32.030 CEST [705/T1218] ERROR: SQLite3: no such table: info in "SELECT value FROM info WHERE property = 'updated';" (1)
   2025-05-22 00:00:32.031 CEST [705/T1218] WARNING: gravity_updated(): SELECT value FROM info WHERE property = 'updated'; - SQL error prepare: SQL logic error
   2025-05-22 00:00:33.038 CEST [705/T1218] ERROR: SQLite3: no such table: info in "SELECT value FROM info WHERE property = 'updated';" (1)
   2025-05-22 00:00:33.039 CEST [705/T1218] WARNING: gravity_updated(): SELECT value FROM info WHERE property = 'updated'; - SQL error prepare: SQL logic error
   2025-05-22 00:00:34.046 CEST [705/T1218] ERROR: SQLite3: no such table: info in "SELECT value FROM info WHERE property = 'updated';" (1)
   2025-05-22 00:00:34.047 CEST [705/T1218] WARNING: gravity_updated(): SELECT value FROM info WHERE property = 'updated'; - SQL error prepare: SQL logic error
   2025-05-22 00:00:35.051 CEST [705/T1218] ERROR: SQLite3: no such table: info in "SELECT value FROM info WHERE property = 'updated';" (1)
   2025-05-22 00:00:35.052 CEST [705/T1218] WARNING: gravity_updated(): SELECT value FROM info WHERE property = 'updated'; - SQL error prepare: SQL logic error
   2025-05-22 00:00:36.067 CEST [705/T1218] ERROR: SQLite3: no such table: info in "SELECT value FROM info WHERE property = 'updated';" (1)

   e[96m-----tail of FTL.log------e[0m
   2025-05-22 02:57:32.128 CEST [709/T1341] ERROR: gravity_updated(): SELECT value FROM info WHERE property = 'updated'; - SQL error step: no more rows available
   2025-05-22 02:57:41.037 CEST [709/T1419] WARNING: API: Could not read domains from database table (key: database_error, hint: Database not available)
   2025-05-22 02:57:42.158 CEST [709/T1408] WARNING: API: Could not read domains from database table (key: database_error, hint: Database not available)
   2025-05-22 02:57:42.746 CEST [709/T1408] WARNING: API: Could not read domains from database table (key: database_error, hint: Database not available)
   2025-05-22 02:57:43.814 CEST [709/T1366] WARNING: API: Could not read domains from database table (key: database_error, hint: Database not available)
   2025-05-22 02:57:44.527 CEST [709/T1407] WARNING: API: Could not read domains from database table (key: database_error, hint: Database not available)
   2025-05-22 02:57:45.890 CEST [709/T1407] WARNING: API: Could not read domains from database table (key: database_error, hint: Database not available)
   2025-05-22 02:57:46.697 CEST [709/T1407] WARNING: API: Could not read domains from database table (key: database_error, hint: Database not available)
   2025-05-22 02:57:47.936 CEST [709/T1419] WARNING: API: Could not read domains from database table (key: database_error, hint: Database not available)
   2025-05-22 02:57:48.726 CEST [709/T1366] WARNING: API: Could not read domains from database table (key: database_error, hint: Database not available)
   2025-05-22 03:46:06.645 CEST [709/T1340] INFO: Received 8/8 valid NTP replies from pool.ntp.org
   2025-05-22 03:46:06.646 CEST [709/T1340] INFO: Time offset: -3.233731e+00 ms (excluded 0 outliers)
   2025-05-22 03:46:06.647 CEST [709/T1340] INFO: Round-trip delay: 3.926146e+01 ms (excluded 0 outliers)
   2025-05-22 04:46:06.926 CEST [709/T1340] INFO: Received 8/8 valid NTP replies from pool.ntp.org
   2025-05-22 04:46:06.926 CEST [709/T1340] INFO: Time offset: 3.134459e+00 ms (excluded 0 outliers)
   2025-05-22 04:46:06.927 CEST [709/T1340] INFO: Round-trip delay: 2.184004e+01 ms (excluded 0 outliers)
   2025-05-22 05:46:07.138 CEST [709/T1340] INFO: Received 8/8 valid NTP replies from pool.ntp.org
   2025-05-22 05:46:07.139 CEST [709/T1340] INFO: Time offset: -1.457078e-01 ms (excluded 1 outliers)
   2025-05-22 05:46:07.139 CEST [709/T1340] INFO: Round-trip delay: 1.234518e+01 ms (excluded 1 outliers)
   2025-05-22 06:46:07.356 CEST [709/T1340] INFO: Received 8/8 valid NTP replies from pool.ntp.org
   2025-05-22 06:46:07.356 CEST [709/T1340] INFO: Time offset: 5.205472e-01 ms (excluded 2 outliers)
   2025-05-22 06:46:07.357 CEST [709/T1340] INFO: Round-trip delay: 1.169904e+01 ms (excluded 2 outliers)
   2025-05-22 07:46:07.554 CEST [709/T1340] INFO: Received 8/8 valid NTP replies from pool.ntp.org
   2025-05-22 07:46:07.555 CEST [709/T1340] INFO: Time offset: 5.886853e-01 ms (excluded 0 outliers)
   2025-05-22 07:46:07.555 CEST [709/T1340] INFO: Round-trip delay: 1.185793e+01 ms (excluded 0 outliers)
   2025-05-22 08:46:07.756 CEST [709/T1340] INFO: Received 8/8 valid NTP replies from pool.ntp.org
   2025-05-22 08:46:07.757 CEST [709/T1340] INFO: Time offset: -7.615685e-01 ms (excluded 0 outliers)
   2025-05-22 08:46:07.757 CEST [709/T1340] INFO: Round-trip delay: 1.214564e+01 ms (excluded 0 outliers)
   2025-05-22 11:19:11.076 CEST [709/T1340] INFO: Received 8/8 valid NTP replies from pool.ntp.org
   2025-05-22 11:19:11.076 CEST [709/T1340] INFO: Time offset: -2.875805e+00 ms (excluded 1 outliers)
   2025-05-22 11:19:11.077 CEST [709/T1340] INFO: Round-trip delay: 1.496724e+01 ms (excluded 1 outliers)
   2025-05-22 11:30:56.544 CEST [709/T1366] WARNING: API: Could not read domains from database table (key: database_error, hint: Database not available)
   2025-05-22 12:19:11.366 CEST [709/T1340] INFO: Received 8/8 valid NTP replies from pool.ntp.org
   2025-05-22 12:19:11.367 CEST [709/T1340] INFO: Time offset: 2.508968e+00 ms (excluded 0 outliers)
   2025-05-22 12:19:11.367 CEST [709/T1340] INFO: Round-trip delay: 2.105433e+01 ms (excluded 0 outliers)

Captura de pantalla 2025-05-22 123417
Captura de pantalla 2025-05-22 1234171552×798 112 KB

2

Try to run sudo pihole -g and wait it to finish, then check the web interface again.

If this still doesn't fix the issue, generate a new debug log.

1 Like
3

Thanks a lot. I tried -g yesterday and it didn't work. Today I got the idea that maybe Gravity was damaged, so I tried to find a solution to fix it, and I found one:

sudo pihole -r

Thank you for your help :+1: