Unable to access Querylog

Please follow the below template, it will help us to help you!

Expected Behaviour:

Expecting to see recent query logs

Actual Behaviour:

Page gets locked with the text "processing"

Debug Token:

kzhscgyylp

What is the output of sudo cat /var/log/lighttpd/error.log

It doesnt seems to be giving specific errors.
Last logs were:
2018-05-08 20:46:07: (mod_fastcgi.c.2543) FastCGI-stderr: PHP Warning: unlink(../custom_disable_timer): No such file or directory in /var/www/html/admin/api.php on line 47
2018-05-08 20:49:56: (server.c.1828) server stopped by UID = 0 PID = 1
2018-05-08 20:49:58: (log.c.217) server started
2018-05-08 21:02:40: (server.c.1828) server stopped by UID = 0 PID = 1
2018-05-08 21:05:30: (log.c.217) server started
2018-05-08 21:09:31: (server.c.1828) server stopped by UID = 0 PID = 1
2018-05-08 21:09:33: (log.c.217) server started
2018-05-08 21:16:35: ## is not a valid domain
2018-05-08 21:33:41: *.google.com is not a valid domain
2018-05-08 21:52:09: (server.c.1828) server stopped by UID = 0 PID = 1
2018-05-08 21:52:33: (log.c.217) server started
2018-05-08 21:55:56: (server.c.1828) server stopped by UID = 0 PID = 1
2018-05-08 21:55:58: (log.c.217) server started

do you see any errors in the page's console ?

That's my main page. Weird that it says 0 queries. This happened after upgrading from 3.3 to beta. Before, it was working fine.

No, i don't see any errors in console

image

You actually have queries processed and blocked.

Check out your query log.

Graphs will take a little time to update. They are not rendered in real time but hourly.

Check in a few hours :slight_smile:


That's the problem that i'm seeing. Is it normal ? Its locked here

Edit:


This doesnt work too even if i have 30 queries blocked

Thank you so much man. Apparently it was my browser cache that was causing problems.
Thanks, just wanna add a note.

My DB precendetly corrupted because i've added too much load on the PI.
The solutions was to flush logs, delete pihole DB (or rename it to .old) and then run pihole -r with repair, just if someone has my same problem

1 Like

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.