search

hassio-addons / addon-pi-hole

Pi-hole - Home Assistant Community Add-ons
https://addons.community
MIT License
123 stars 40 forks source link

FATAL: Opening of FTL log (/var/log/pihole-FTL.log) failed! #31

Closed Cooper-Dale closed 6 years ago

Cooper-Dale commented 6 years ago

Problem/Motivation

my log is full of (Rpi3; HassIO; Hass.io supervisor version 115; Pi-hole 1.2.0)

 FATAL: Opening of FTL log (/var/log/pihole-FTL.log) failed!
       Make sure it exists and is writeable by user pihole

Expected behavior

writeble file, I am not sure if the path is correct - ssh to hassio and browse to /var/log/ - empty folder, when I create a log file there and set 666 the result is the same

Actual behavior

full log

Steps to reproduce

after every restart

addons-assistant[bot] commented 6 years ago

:wave: Thanks for opening your first issue here! If you're reporting a :bug: bug, please make sure you include steps to reproduce it. Also, logs, error messages and information about your hardware might be usefull.

frenck commented 6 years ago

@Cooper-Dale Are you running the HassOS beta?

Cooper-Dale commented 6 years ago

@frenck No

frenck commented 6 years ago

@Cooper-Dale Could you share some more specifics? Like your platform, the add-on configuration, version numbers of hass.io and the add-ons (and maybe other things like OS as well)?

Cooper-Dale commented 6 years ago

No problem, but it is in my first post:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] 01-resolver-resolv: applying... 
[fix-attrs.d] 01-resolver-resolv: exited 0.
[fix-attrs.d] 01-sudo: applying... 
[fix-attrs.d] 01-sudo: exited 0.
[fix-attrs.d] 02-nginx: applying... 
[fix-attrs.d] 02-nginx: exited 0.
[fix-attrs.d] 03-pihole: applying... 
[fix-attrs.d] 03-pihole: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Hass.io Add-on: Pi-hole v1.2.0
 Network-wide ad blocking using your Hass.io instance
 From: Community Hass.io Add-ons
 By: Franck Nijhof
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing... 
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-requirements.sh: executing... 
[cont-init.d] 10-requirements.sh: exited 0.
[cont-init.d] 11-patches.sh: executing... 
[cont-init.d] 11-patches.sh: exited 0.
[cont-init.d] 11-pihole.sh: executing... 
[cont-init.d] 11-pihole.sh: exited 0.
[cont-init.d] 12-dnsmasq.sh: executing... 
[cont-init.d] 12-dnsmasq.sh: exited 0.
[cont-init.d] 13-nginx.sh: executing... 
[cont-init.d] 13-nginx.sh: exited 0.
[cont-init.d] 14-password.sh: executing... 
WARNING: No password set! This is not recommended!
  [✓] Password Removed
[cont-init.d] 14-password.sh: exited 0.
[cont-init.d] 15-hostname.sh: executing... 
[cont-init.d] 15-hostname.sh: exited 0.
[cont-init.d] 16-logfiles.sh: executing... 
[cont-init.d] 16-logfiles.sh: exited 0.
[cont-init.d] 17-hosts.sh: executing... 
[cont-init.d] 17-hosts.sh: exited 0.
[cont-init.d] 50-gravity.sh: executing... 
  [i] Neutrino emissions detected...
  [i] Pulling blocklist source list into range...

  [✓] Pulling blocklist source list into range
  [i] Target: raw.githubusercontent.com (hosts)
  [i] Status: Pending...

  [✓] Status: Retrieval successful
  [i] Target: mirror1.malwaredomains.com (justdomains)
  [i] Status: Pending...

  [✓] Status: No changes detected
  [i] Target: sysctl.org (hosts)
  [i] Status: Pending...

  [✓] Status: No changes detected
  [i] Target: zeustracker.abuse.ch (blocklist.php?download=domainblocklist)
  [i] Status: Pending...

  [✓] Status: No changes detected
  [i] Target: s3.amazonaws.com (simple_tracking.txt)
  [i] Status: Pending...

  [✓] Status: No changes detected
  [i] Target: s3.amazonaws.com (simple_ad.txt)
  [i] Status: Pending...

  [✓] Status: No changes detected
  [i] Target: hosts-file.net (ad_servers.txt)
  [i] Status: Pending...

  [✓] Status: No changes detected
  [i] Consolidating blocklists...

  [✓] Consolidating blocklists
  [i] Extracting domains from blocklists...

  [✓] Extracting domains from blocklists
  [i] Number of domains being pulled in by gravity: 155818
  [i] Removing duplicate domains...

  [✓] Removing duplicate domains
  [i] Number of unique domains trapped in the Event Horizon: 132559
  [i] Number of whitelisted domains: 8...

  [i] Number of whitelisted domains: 8
  [i] Parsing domains into hosts format...

  [✓] Parsing domains into hosts format
  [i] Cleaning up stray matter...

  [✓] Cleaning up stray matter
  [✗] dnsmasq: no process found
pihole-FTL: no process found
  [✓] DNS service is running
  [✓] Pi-hole blocking is Enabled
[cont-init.d] 50-gravity.sh: exited 0.
[cont-init.d] 99-tests.sh: executing... 
dnsmasq: syntax check OK.
[09-Jul-2018 14:35:58] NOTICE: configuration file /etc/php7/php-fpm.conf test is successful
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
[cont-init.d] 99-tests.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
FATAL: Opening of FTL log (/var/log/pihole-FTL.log) failed!
       Make sure it exists and is writeable by user pihole
FATAL: Opening of FTL log (/var/log/pihole-FTL.log) failed!
       Make sure it exists and is writeable by user pihole
FATAL: Opening of FTL log (/var/log/pihole-FTL.log) failed! 
.....
PRabahy commented 6 years ago

I had the same thing happening on my install of Home Assistant. I uninstalled then reinstalled this addon and it fixed it.

The only other addon I had running was the Configurator, but I have Check Home Assistant configuration, Let's Encrypt, NGINX Home Assistant SSL proxy, and SSH server installed.

einschmidt commented 6 years ago

@PRabahy I can second your findings. After I unstalled and reinstalled the addon the error did not happen again. By the way this error happened to me after the migration to HassOS 1.5 only.

PRabahy commented 6 years ago

I have not migrated to HassOS. I am still on Hass.io.

frenck commented 6 years ago

I've been able to reproduce this now. Looking into a solution.

frenck commented 6 years ago

Found it! Still needs some testing, but is fixed in the master branch, will be in the next release.

addons-assistant[bot] commented 6 years ago

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.