Client Activity missing from dashboard

Help Community Help
1

On one of my Pi-hole's, the Client Activity panel is missing from the dashboard. If I refresh the page it comes back. Using Edge. My other one never exhibits this. They are clones of each other, with the only difference being the problematic one uses the dark mode theme.

Anyone ever have this?

2

Please follow our help template. Expected behavior, actual behavior, debug token, etc.

3

Expected Behaviour:

Pi-hole web interface should always show the client activity panel. Since a few updates ago, I often see one of my Pi-hole instances not showing this panel. Both instances are clones of each other, except the problematic one is using the dark mode interface. I leave the Pi-hole dashboard up all the time in my browser.
Edge on Win10, both Pi-holes are on a Raspberry Pi 4b 8GB

Actual Behaviour:

Pi-hole dashboard occasionally missing the Client Activity panel. Refreshing the page brings it back.

Debug Token:

https://tricorder.pi-hole.net/hJ8uaofW/

4

It appears you are running other software that may be interferering with the functions of Pi-hole:

-rw-r--r-- 1 www-data www-data 453K Mar 17 11:59 /var/log/lighttpd/error-pihole.log
   -----head of error-pihole.log------
   2023-03-12 00:00:28: server.c.1787) logfiles cycled UID = 0 PID = 32302
   2023-03-12 00:33:25: connections.c.750) invalid request-line -> sending Status 400
   2023-03-12 01:15:41: mod_fastcgi.c.487) FastCGI-stderr:PHP Warning:  SQLite3::query(): Unable to prepare statement: 5, database is locked in /home/pi/pialert/front/php/server/parameters.php on line 46
   2023-03-12 01:15:41: mod_fastcgi.c.487) FastCGI-stderr:PHP Fatal error:  Uncaught Error: Call to a member function fetchArray() on bool in /home/pi/pialert/front/php/server/parameters.php:47
   2023-03-12 01:15:41: mod_fastcgi.c.487) FastCGI-stderr:Stack trace:
   2023-03-12 01:15:41: mod_fastcgi.c.487) FastCGI-stderr:#0 /home/pi/pialert/front/php/server/parameters.php(28): getParameter()
   2023-03-12 01:15:41: mod_fastcgi.c.487) FastCGI-stderr:#1 {main}
   2023-03-12 01:15:41: mod_fastcgi.c.487) FastCGI-stderr:  thrown in /home/pi/pialert/front/php/server/parameters.php on line 47
   2023-03-12 01:15:41: mod_fastcgi.c.487) FastCGI-stderr:PHP Warning:  SQLite3::query(): Unable to prepare statement: 5, database is locked in /home/pi/pialert/front/php/server/devices.php on line 183
   2023-03-12 01:15:41: mod_fastcgi.c.487) FastCGI-stderr:PHP Fatal error:  Uncaught Error: Call to a member function fetchArray() on bool in /home/pi/pialert/front/php/server/devices.php:184
...
5

I do run my own fork of PiAlert but it does not touch the PiHole db anymore, I've retrofitted it to get its data from my Unifi network API.

Are these errors specific to the access of the PiHole DB or is the PHP server reporting all errors even for other PHP apps and their SQLite db's?

6

This indicates otherwise:

   2023-03-12 01:15:41: mod_fastcgi.c.487) FastCGI-stderr:PHP Warning:  SQLite3::query(): Unable to prepare statement: 5, database is locked in /home/pi/pialert/front/php/server/parameters.php on line 46

I would start troubleshooting by completely disabling Pi-Alert and restarting FTL. If the problem clears, you know where the problem lies. If not, we continue troubleshooting.

7

I disabled the other app but am still seeing the missing client activity panel sporadically. I'm pretty sure that error message is caused by my app and the DB it refers to is my pialert.db. Those FastCGI errors are from any PHP app running under the pi 's webserver, as I understand it.

8

Actually both Pi-hole and Pialert app use the same webserver (lighttpd). Pi-hole creates the /var/log/lighttpd/error-pihole.log and Pialert uses whatever error log is configured.

So, in this specific case, both applications will show error messages on the same file, but it's possible for other applications to use different files to store error logs.

I'm not sure how you customized your Pialert fork, but you can try to set a different error log.

I guess you can try (this is UNTESTED and I never used Pialert) to change pialert_front.conf and add a new error log file:

$HTTP["host"] == "pi.alert" {
  server.document-root = "/var/www/html/pialert/"
  server.errorlog := "/var/log/lighttpd/error-pialert.log"
}
9

Thanks! I just modified my pi with this and we'll see if the errors show up in the pihole log anymore.

10

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