Closed Bogdan107 closed 2 years ago
Question: Why /etc/pihole/setupVars.conf file moved into /var/lib/pihole/setupVars.conf inside the ebuild script?
Changes occur to it in other places such as the Pi-hole web interface (there is no package for this yet, but I have it running over here). It needs correct access for that to work. It seems more appropriate that files that can change at runtime not be placed /etc
.
Solution, variant 1: create draft file from ebuild script;
I will implement this.
Will add.
Will need to add init of pihole-FTL.db
.
I am getting this issue at times.
As a workaround:
I deleted /var/lib/pihole/gravity.db*
, used the old way to add ad lists (by creating a list of URLs at /var/lib/pihole/adlists.list
) and then ran pihole -g
. The adlists.list
file will be moved to migration_backup
after this, and without the web interface the only to add a new ad list is to use SQL with sqlite3 gravity.db
:
insert into adlist (address) values ('https://someonewhocares.org/hosts/hosts');
Then run pihole -g
.
Also for later: https://github.com/Tatsh/tatsh-overlay/issues/119#issuecomment-995401530 and #121
Back up your setupVars.conf
before merging the ebuilds again.
Do you have /etc/dnsmasq.conf
? If you do, what is the content? Mine is
conf-dir=/etc/pihole/dnsmasq.d
Currently the ebuild does not ship this file.
Do you have
/etc/dnsmasq.conf
? If you do, what is the content?
This file contain standart draft content of system installed dnsmasq
package.
At now all lines are commented there.
Pi-Holed dnsmasq daemon is included into pihole-FTL binary.
Why pihol-ed dnsmasq deamon still requires configs/paths of system daemons (about /etc/dnsmasq.conf
file)?
We can change that path in FTL's code if that is a concern. The default configuration from Pi-hole's end is that a system cannot have DNSMasq and FTL installed at the same time. FTL is based on DNSMasq so it will use the same paths. I moved the general configs to be under /etc/pihole/dnsmasq.d
to make it more clear what kind of configs these are.
Please try with a clean install and see if you find if any of these bugs remain:
If you find something, file a new issue.
I have errors:
Message 1: /usr/bin/pihole: line 142: Cannot restart Pi-hole: command not found
What is wrong:
pihole
script does not know how to restart system service.Solution in patch:
Message 2: sed: can't read /var/lib/pihole/setupVars.conf: No such file or directory
File
/var/lib/pihole/setupVars.conf
strictly reuired inpihole
script, but this file is not prepared by installer.Solution, variant 1: create draft file from ebuild script; Solution, variant 2: create null file from init script (like
checkpath -o "$command_user" -f /var/lib/pihole/setupVars.conf
).Question: Why
/etc/pihole/setupVars.conf
file moved into/var/lib/pihole/setupVars.conf
inside the ebuild script? I think, that storing setupVars.conf file under/var
directory is reasonable for embedded devices, where root filesystem is RO and/var
directory is RW. But why ebuild use/var
for storing the file, which place is inside the/etc
directory?Message 3: error: error creating stub state file /var/lib/logrotate/pihole: No such file or directory
This file path defined in STATEFILE variable of
/usr/lib64/pihole/piholeLogFlush.sh
script. Directory/var/lib/logrotate
does not exists by default.Solution in patch:
Message 4: Error: in prepare, no such table: queries (1)
This is bug of
pihole
orpihole-ftl
installer, which must preparepihole-FTL.db
structure.Message 5: _Error: in prepare, no such table: networkaddresses (1)
This is bug of
pihole
orpihole-ftl
installer, which must preparepihole-FTL.db
structure.Message 6: Error: in prepare, no such table: main.gravity (1)
As
gravity
table present ingravity.db
file, then this is bug ofgravity.sh
script, which can't findgravity
table inside the gravityTEMPfile or gravityOLDfile file.