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

in /var/log/daemon.log: lighttpd[553]: grep: blacklist.txt: No such file or directory #1888

Closed
3 tasks done
LudovicRousseau opened this issue Jan 3, 2018 · 1 comment
Closed
3 tasks done

Comments

@LudovicRousseau
Copy link
Contributor

LudovicRousseau commented Jan 3, 2018

In raising this issue, I confirm the following:

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

1


Expected behaviour:

No such logs from lighttpd in /var/log/daemon.log.

Actual behaviour:

$ grep lighttpd /var/log/daemon.log
Jan  1 16:47:08 PiHole lighttpd[553]: grep: blacklist.txt: No such file or directory
Jan  1 16:47:08 PiHole lighttpd[553]: grep: blacklist.txt: No such file or directory
Jan  1 16:47:10 PiHole lighttpd[553]: grep: blacklist.txt: No such file or directory
Jan  1 16:47:12 PiHole lighttpd[553]: grep: blacklist.txt: No such file or directory
Jan  1 18:03:32 PiHole lighttpd[553]: grep: blacklist.txt: No such file or directory
Jan  1 18:03:43 PiHole lighttpd[553]: grep: blacklist.txt: No such file or directory
Jan  1 18:03:57 PiHole lighttpd[553]: grep: blacklist.txt: No such file or directory
Jan  2 23:51:16 PiHole lighttpd[553]: grep: blacklist.txt: No such file or directory
Jan  3 11:42:35 PiHole lighttpd[553]: grep: blacklist.txt: No such file or directory
Jan  3 11:42:35 PiHole lighttpd[553]: grep: blacklist.txt: No such file or directory

Since I use logcheck https://packages.debian.org/sid/logcheck to watch my logs I get emails for each such log.

Steps to reproduce:

Install PiHole and watch /var/log/daemon.log file. I am using PiHole on Debian stable.

Debug token provided by uploading pihole -d log:

3g5xf70kj6

Troubleshooting undertaken, and/or other relevant information:

I have not yet fixed it. I propose 2 options:

  • check the file blacklist.txt exists before using grep(1) on it
    or
  • provide an empty blacklist.txt file by default.

I will create an empty /etc/pihole/blacklist.txt file for now.

@jacobsalmela
Copy link
Contributor

We're always open to pull requests if you have a suggestion on fixing the issue.

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

2 participants