logopk

I have the same issue on a 3b+. Had to disable the database. Even with an empty DB as a start it happens again after a couple of days/even hours......

> > Even with an empty DB as a start it happens again after a couple of days/even hours... > > Oh, interesting. I was thinking that disabling the DB...

The issue gets really bad once I reload the dns after updating data in my dnsmasq files (or any config in the UI that requires reload) I have two use...

Around midnight it does an internal reload ``` tail: /var/log/pihole/FTL.log: file truncated 2025-06-17 00:33:37.701 CEST [50/T12350] INFO: Restarting FTL: API action request 2025-06-17 00:33:37.701 CEST [50M] INFO: Asked to terminate...

OK, I'll have an eye on it. Currently at 640000 records. The downtime is at roughly 1:20 min.

No automatic restart happened since yesterday. Currently with 723492 log entries the reload takes 1:40 min.

After 3 days the number has increased to 777652, reload takes 2:30 and the query log takes almost 8 sec. beware if you click twice or activate "live update", cpu...

After a week I did get frequent dig lookup failures. I enabled database debug. And I've found that every minute the storage of the query log takes between 15 and...

You still don't get the point. It should do this in a separate task and non-blocking. That would speed up startup. Each restart of DNS, reload or many changes of...

I can add a me too on debian bookworm in a docker-compose build. I have tried all the above suggestions with ENV MODSECURITY_INC /usr/local/modsecurity/include/ ENV MODSECURITY_LIB /usr/local/modsecurity/lib/ ENV CFLAGS -I/usr/local/modsecurity/headers...