Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Query Log Ajax Error #561

Closed
iLlama opened this issue Jul 6, 2016 · 8 comments
Closed

Query Log Ajax Error #561

iLlama opened this issue Jul 6, 2016 · 8 comments

Comments

@iLlama
Copy link

iLlama commented Jul 6, 2016

Expected Behavior: Show Query Log info on Admin Page

Actual Behavior: Receive error DataTables warning: table id=all-queries - Ajax error

Steps to reproduce this issue: Clicking Query Log

All of the main page graphs seems to be working fine, though loading is quiet slow.

Seen the /var/log/lighttpd/error.log asked for in other threads I looked at so here is that as well - http://pastebin.com/yNkxRaGA

@AzureMarker
Copy link
Contributor

Run pihole -d and pastebin the log it creates as well. It looks like you might have a big log file. One of the reasons we're working on a rewrite is so that a big log file doesn't slow down the web interface.

@iLlama
Copy link
Author

iLlama commented Jul 6, 2016

Here is the log - http://pastebin.com/N1hLfG70

Not sure if its worth mentioning that I have only been using pi-hole for a few days. #

@AzureMarker
Copy link
Contributor

If you run pihole -f, wait a min or so, and then check the web interface, what are the stats? Does everything load correctly?

@iLlama
Copy link
Author

iLlama commented Jul 7, 2016

Well, I wanted to wait a day before I said anything, but it seems the issue went away on its own.

@AzureMarker
Copy link
Contributor

The issue most likely was that there were so many queries logged at that point that the pi was unable to handle so many. It fixed itself because every night the log is flushed.

@iLlama
Copy link
Author

iLlama commented Jul 7, 2016

I guess that makes sense then. I noticed this issue on days that my family would be home and surfing all day. The last two days we have been at work and school etc.

Is this something I should keep an eye on this weekend I guess? What should I do if it happens again? Can I increase the log size or flush the log manually?

Thanks

@AzureMarker
Copy link
Contributor

Having a large log will only affect the web interface, so unless that's critical for you it is not too important. Running pihole -f will flush the log, letting you view the web interface stats (although there won't be many queries shown since it was just flushed).

@PromoFaux
Copy link
Member

Reopened on the AdminLTE repo on the above link.

@DL6ER DL6ER mentioned this issue Apr 6, 2017
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants