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

cron job "pihole flush once quiet" produces missing conf file error #2139

Closed
3 tasks done
fsantiago07044 opened this issue Apr 21, 2018 · 7 comments
Closed
3 tasks done
Assignees
Labels
Fixed in next release triage: Issue User Filled out Issue Template

Comments

@fsantiago07044
Copy link

In raising this issue, I confirm the following: {please fill the checkboxes, e.g: [X]}

How familiar are you with the the source code relevant to this issue?:

1


Expected behaviour:

for cron job to complete successfully and silently, or at least without error

Actual behaviour:

each run of this cron job:

00 00 * * * root PATH="$PATH:/usr/local/bin/" pihole flush once quiet

produces error message:

sed: can't read /etc/pihole/pihole-FTL.conf: No such file or directory

Steps to reproduce:

run said cron job without conf file present

Debug token provided by uploading pihole -d log:

nqd3o5l882

Troubleshooting undertaken, and/or other relevant information:

I could simply create the missing file but am unsure of its content or syntax. why is this file missing? I'm running on fedora 27, and recently uninstalled and reinstalled. i have never noticed this error before. Is it a problem? Thanks.

@dschaper dschaper added triage: Issue User Filled out Issue Template Investigating Open issue or bug, under investigation labels Apr 21, 2018
@dschaper
Copy link
Member

@bcambl You recently did a fresh install on Fed 27, did you have to adjust anything when you installed?

@fsantiago07044
Copy link
Author

fsantiago07044 commented Apr 21, 2018 via email

@bcambl
Copy link
Member

bcambl commented Apr 21, 2018

No adjustments made. That said, the file in question is missing on both my devices:

OPZ w/ Armbian:

root@orangepizero:~# stat /etc/pihole/pihole-FTL.conf
stat: cannot stat '/etc/pihole/pihole-FTL.conf': No such file or directory
root@orangepizero:~# pihole -v
  Pi-hole version is v3.2.1-148-g82d5afe (Latest: v3.3.1)
  AdminLTE version is v3.2.1-123-g89090261 (Latest: v3.3)
  FTL version is vDev-d1c163e (Latest: v3.0)
root@orangepizero:~# 

RPI3 w/ Fedora 27 Server:

[root@localhost ~]# stat /etc/pihole/pihole-FTL.conf
stat: cannot stat '/etc/pihole/pihole-FTL.conf': No such file or directory
[root@localhost ~]# pihole -v
  Pi-hole version is v3.3.1-74-g557372b (Latest: v3.3.1)
  AdminLTE version is v3.3 (Latest: v3.3)
  FTL version is vDev-02b987c (Latest: v3.0)
[root@localhost ~]# 

@technicalpyro
Copy link
Contributor

technicalpyro commented Apr 21, 2018

iirc FTL.conf is not created unless the user creates an populates it @DL6ER ? can probably confimr better than i can

@bcambl
Copy link
Member

bcambl commented Apr 21, 2018

This has already been fixed in the development branch with the following commit: d8f85a8

@AzureMarker AzureMarker added Fixed in next release and removed Investigating Open issue or bug, under investigation labels Apr 21, 2018
@subfission
Copy link

subfission commented Apr 27, 2018

Simple workaround until next release:

touch /etc/pihole/pihole-FTL.conf

@fsantiago07044
Copy link
Author

fsantiago07044 commented Apr 27, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Fixed in next release triage: Issue User Filled out Issue Template
Projects
None yet
Development

No branches or pull requests

6 participants