Error opening database on "network" page

General Beta 5.0
1

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

Please ensure that you are running the latest version of the beta code.
Run pihole -up to update to the latest, then verify that the problem still exists before reporting it.

Problem with Beta 5.0:
On the Network page (Network overiview), I receive "No data available in table", error connecting to database /etc/pihole/pihole-FTL.db unable to open database: unable to open database file

Debug Token:
[✗] There was an error uploading your debug log.

  • Please try again or contact the Pi-hole team for assistance.
  • A local copy of the debug log can be found at: /var/log/pihole_debug.log
3

Please PM me the log.

5

This is not a supported OS. You likely have gotten it working, but we can only offer limited support for this OS version.

*** [ DIAGNOSING ]: Operating system
[✓] Fedora 31 (Server Edition)

https://docs.pi-hole.net/main/prerequesites/

Can you post a screen capture of what you see on that page? You can paste it directly into a reply.

Out of curiousity, was this choice of subnet mask intentional? /26 is not something widely used.

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the enp3s0 interface:
172.28.100.2/26 matches the IP found in /etc/pihole/setupVars.conf
6

image

7

the /26 is intentional, no real rhyme or reason

8

What is the output of ls -lha /etc/pihole/pihole-FTL.db

9

-rw------- 1 pihole pihole 1.2M Apr 21 09:36 /etc/pihole/pihole-FTL.db

10

The permissions should be:

-rw-r--r-- 1 pihole pihole 46M Apr 21 10:00 /etc/pihole/pihole-FTL.db

11

OK, am I screwed because of Fedora 31? or can i fix it? (PiHole works great btw, dns is fine, and browsing is faster than ever...)

12

You should be able to fix it with the chmod command. The required permissions are 644. To be safe, we stop FTL first and then restart.

sudo service pihole-FTL stop

sudo chmod 644 /etc/pihole/pihole-FTL.db

sudo service pihole-FTL start

13

Bingo! solved, thanks

1 Like
14

@bigq4mayor Out of curiosity (and likely what was causing the issue for you):

What is the output of

umask

on your Pi-hole?

15

umask output is
0022

16

Hmm, does

sudo umask

say something different?

17

same output