pi-hole/ftl

The Pi-hole FTL engine

Network-wide ad blocking via your own Linux hardware

The Pi-hole® is a DNS sinkhole that protects your devices from unwanted content without installing any client-side software.

• Easy-to-install: our dialogs walk you through the simple installation process in less than ten minutes
• Resolute: content is blocked in non-browser locations, such as ad-laden mobile apps and smart TVs
• Responsive: seamlessly speeds up the feel of everyday browsing by caching DNS queries
• Lightweight: runs smoothly with minimal hardware and software requirements
• Robust: a command-line interface that is quality assured for interoperability
• Insightful: a beautiful responsive Web Interface dashboard to view and control your Pi-hole
• Versatile: can optionally function as a DHCP server, ensuring all your devices are protected automatically
• Scalable: capable of handling hundreds of millions of queries when installed on server-grade hardware
• Modern: blocks ads over both IPv4 and IPv6
• Free: open source software that helps ensure you are the sole person in control of your privacy

---

One-Step Automated Install

Those who want to get started quickly and conveniently may install Pi-hole using the following command:

curl -sSL https://install.pi-hole.net | bash

Alternative Install Methods

Piping to bash is controversial, as it prevents you from reading code that is about to run on your system. Therefore, we provide these alternative installation methods which allow code review before installation:

Method 1: Clone our repository and run

git clone --depth 1 https://github.com/pi-hole/pi-hole.git Pi-hole
cd "Pi-hole/automated install/"
sudo bash basic-install.sh

Method 2: Manually download the installer and run

wget -O basic-install.sh https://install.pi-hole.net
sudo bash basic-install.sh

Method 3: Using Docker to deploy Pi-hole

Please refer to the Pi-hole docker repo to use the Official Docker Images.

Post-install: Make your network take advantage of Pi-hole

Once the installer has been run, you will need to configure your router to have DHCP clients use Pi-hole as their DNS server. This router configuration will ensure that all devices connecting to your network will have content blocked without any further intervention.

If your router does not support setting the DNS server, you can use Pi-hole's built-in DHCP server; be sure to disable DHCP on your router first (if it has that feature available).

As a last resort, you can manually set each device to use Pi-hole as their DNS server.

---

Pi-hole is free but powered by your support

There are many reoccurring costs involved with maintaining free, open-source, and privacy-respecting software; expenses which our volunteer developers pitch in to cover out-of-pocket. This is just one example of how strongly we feel about our software and the importance of keeping it maintained.

Make no mistake: your support is absolutely vital to help keep us innovating!

Donations

Donating using our Sponsor Button is extremely helpful in offsetting a portion of our monthly expenses:

Alternative support

If you'd rather not donate (which is okay!), there are other ways you can help support us:

• GitHub Sponsors
• Patreon
• Hetzner Cloud affiliate link
• Digital Ocean affiliate link
• Stickermule earn a $10 credit after your first purchase
• Amazon US affiliate link
• Spreading the word about our software and how you have benefited from it

Contributing via GitHub

We welcome everyone to contribute to issue reports, suggest new features, and create pull requests.

If you have something to add - anything from a typo through to a whole new feature, we're happy to check it out! Just make sure to fill out our template when submitting your request; the questions it asks will help the volunteers quickly understand what you're aiming to achieve.

You'll find that the install script and the debug script have an abundance of comments, which will help you better understand how Pi-hole works. They're also a valuable resource to those who want to learn how to write scripts or code a program! We encourage anyone who likes to tinker to read through it and submit a pull request for us to review.

---

Getting in touch with us

While we are primarily reachable on our Discourse User Forum, we can also be found on various social media outlets.

Please be sure to check the FAQs before starting a new discussion, as we do not have the spare time to reply to every request for assistance.

• Frequently Asked Questions
• Feature Requests
• Reddit
• Twitter

---

Breakdown of Features

Faster-than-light Engine

FTLDNS is a lightweight, purpose-built daemon used to provide statistics needed for the Web Interface, and its API can be easily integrated into your own projects. As the name implies, FTLDNS does this all very quickly!

Some of the statistics you can integrate include:

• Total number of domains being blocked
• Total number of DNS queries today
• Total number of ads blocked today
• Percentage of ads blocked
• Unique domains
• Queries forwarded (to your chosen upstream DNS server)
• Queries cached
• Unique clients

Access the API via telnet, the Web (admin/api.php) and Command Line (pihole -c -j). You can find out more details over here.

The Command-Line Interface

The pihole command has all the functionality necessary to fully administer the Pi-hole, without the need for the Web Interface. It's fast, user-friendly, and auditable by anyone with an understanding of bash.

Some notable features include:

• Whitelisting, Blacklisting, and Regex
• Debugging utility
• Viewing the live log file
• Updating Ad Lists
• Querying Ad Lists for blocked domains
• Enabling and Disabling Pi-hole
• ... and many more!

You can read our Core Feature Breakdown for more information.

The Web Interface Dashboard

This optional dashboard allows you to view stats, change settings, and configure your Pi-hole. It's the power of the Command Line Interface, with none of the learning curve!

Some notable features include:

• Mobile-friendly interface
• Password protection
• Detailed graphs and doughnut charts
• Top lists of domains and clients
• A filterable and sortable query log
• Long Term Statistics to view data over user-defined time ranges
• The ability to easily manage and configure Pi-hole features
• ... and all the main features of the Command Line Interface!

There are several ways to access the dashboard:

1. http://pi.hole/admin/ (when using Pi-hole as your DNS server)
2. http://<IP_ADDRESS_OF_YOUR_PI_HOLE>/admin/

ftl's Issues

List all clients from UI

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

1

---

[ISSUE] Expected Behaviour:
It would be useful to be able to list all clients that are requesting DNS lookup through Pi-hole not just Top 10. It would show if a particular client was configured to use Pi-hole correctly as well as looking for rouge clients.

My C is not great but looking at the code I believe https://github.com/pi-hole/FTL/blob/master/request.c#L457 is where this lookup is handled.

If the function was made more general to include the 'count' as a parameter, it looks as if the function could be made more general (even offer a UI to display more items) or simply use 0 to display all clients in the logs.

This template was created based on the work of udemy-dl.

FTL out of date message after updating to 2.9

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

1

---

[BUG | ISSUE] Expected Behaviour:
no message after a succesful update to FTL 2.9

[BUG | ISSUE] Actual Behaviour:
FTL out of date message appears after succesful FTL update to 2.9

[BUG | ISSUE] Steps to reproduce:
pihole -up

Log file output [if available]

output

Device specifics

Hardware Type: rPi, VPS, etc
OS:

This template was created based on the work of udemy-dl.

forward destinations over time

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

1

---

[BUG | ISSUE] Expected Behaviour:
forward destination graphic should display all logs

http://fs5.directupload.net/images/170418/4853ocop.png

[BUG | ISSUE] Actual Behaviour:
sometimes gaps are appearing in the graphic, but pi-hole and query logging are working normal

[BUG | ISSUE] Steps to reproduce:
it appears sometimes when not so many querys have to be logged

Log file output [if available]

output

Device specifics

Hardware Type: rPi, VPS, etc
OS:

This template was created based on the work of udemy-dl.

pi-hole ftl is dying

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

1

[BUG | ISSUE] Expected Behaviour:
ftl runs forever

[BUG | ISSUE] Actual Behaviour:
ftl is dying

[BUG | ISSUE] Steps to reproduce:
run pi-hole for a long time.
web interface shows ftl not running.

output from debug:

a lot of:
[New Thread 0x7ffff57e8700 (LWP 25440)]
[Thread 0x7ffff57e8700 (LWP 25440) exited]

and then:

Thread 48123 "client-4" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff4fe7700 (LWP 11257)]
strlen () at ../sysdeps/x86_64/strlen.S:106
106 ../sysdeps/x86_64/strlen.S: Datei oder Verzeichnis nicht gefunden.

Device specifics

Hardware Type: rPi, VPS, etc
OS:
linux debian stretch

This template was created based on the work of udemy-dl.

Potential NULL parameter to strlen

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

2

---

[BUG] Expected Behaviour:
If a pointer is NULL, it should not be passed as a parameter or used

[BUG] Actual Behaviour:
In parser.c, starting at line 711, the variable part is allocated. The return is checked for NULL, but only logged. part is then provided as an argument to strlen, which would result in undefined behaviour. But probably a segfault in most cases.

I'd consider it very unlikely to be run into/fail, but since the check for NULL is already there, might as well not use the NULL? Perhaps the call to logg will halt or set an error, but I didn't notice anything

[BUG] Steps to reproduce:

Device specifics

Hardware Type: rPi, VPS, etc
OS: N/A

This template was created based on the work of udemy-dl.

Pihole Crashing

[2017-04-11 00:00:04.436] Reading from /var/log/pihole.log.1
[2017-04-11 00:00:04.436] Notice: Increasing queries struct size from 0 to 10000 (281.06 KB)
[2017-04-11 00:00:04.436] Notice: Increasing overTime struct size from 0 to 100 (284.26 KB)
[2017-04-11 00:00:04.436] Notice: Increasing domains struct size from 0 to 1000 (308.27 KB)
[2017-04-11 00:00:04.550] Notice: Increasing overTime struct size from 100 to 200 (333.15 KB)
[2017-04-11 00:00:04.551] Notice: Increasing domains struct size from 1000 to 2000 (357.36 KB)
[2017-04-11 00:00:04.611] Notice: Increasing queries struct size from 10000 to 20000 (645.58 KB)
[2017-04-11 00:00:04.620] Reading from /var/log/pihole.log
[2017-04-11 01:35:13.186] Notice: Increasing clients struct size from 0 to 20 (648.85 KB)
[2017-04-11 01:35:14.794] Added new client: 87.150.154.150 (p57969A96.dip0.t-ipconnect.de)
[2017-04-11 01:35:21.154] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-04-11 01:35:21.155] ----------------------------> FTL crashed! <----------------------------
[2017-04-11 01:35:21.155] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-04-11 01:35:21.155] > Please report a bug at https://github.com/pi-hole/FTL/issues
[2017-04-11 01:35:21.155] > and include in your report already the following details:
[2017-04-11 01:35:21.155] >
[2017-04-11 01:35:21.155] > Received signal: Segmentation fault
[2017-04-11 01:35:21.155] at address: 123969
[2017-04-11 01:35:21.155] with code: SEGV_MAPERR (Address not mapped to object)
[2017-04-11 01:35:21.155] > Memory usage (structs): 614964
[2017-04-11 01:35:21.155] > Memory usage (dynamic): 33933
[2017-04-11 01:35:21.155] >
[2017-04-11 01:35:21.155] > Thank you for helping us to improve our FTL engine!
[2017-04-11 01:35:21.155] FTL terminated!

Tell me which logs or information you need...

Domains with mixed lower and upper case characters cannot be properly analyzed

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

10

---

[BUG | ISSUE] Expected Behaviour:

Domains with mixed small and capital letters should be correctly detected as OK or Pi-holed

[BUG | ISSUE] Actual Behaviour:

Domains with mixed small and capital letters are detected as Unknown

[BUG | ISSUE] Steps to reproduce:

• $ dig GooGle.com
• Result:
  

This template was created based on the work of udemy-dl.

-bash: pihole-FTL: command not found after binary install

Just tried to install FTL on my RPi-0, and I'm unable to get it to run any commands.

I did the following

wget https://github.com/pi-hole/FTL/releases/download/v1.0/pihole-FTL-arm-linux-gnueabi
chmod u+x pihole-FTL*

So far so good...

./pihole-FTL*
FATAL: Opening of FTL log (/var/log/pihole-FTL.log) failed!
       Make sure it exists

Clearly a problem with not having write permissions in /var/log/pihole-FTL.log

sudo /usr/downloads/pihole-FTL-arm-linux-gnueabi
FTL started!

Woohoo!

pihole-FTL
-bash: pihole-FTL: command not found

:(

Any suggestions?

FTL is M.I.A

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

{1}

[BUG | ISSUE] Expected Behaviour:
Rebooted my raspberry pi 3, saw that FTL was offline. Logged in via ssh

pi@raspberrypi:~ $ sudo service pihole-FLT status
pihole-FLT.service
Loaded: not-found (Reason: No such file or directory) Active: inactive (dead)

pi@raspberrypi:~ $ sudo service pihole-FLT start
Failed to start pihole-FLT.service: Unit pihole-FLT.service failed to load: No such file or directory.

pi@raspberrypi:~ $ pihole -up
::: Checking for updates...
::: Pi-hole Core: up to date
::: FTL: up to date
::: Web Interface: up to date
:::
::: Everything is up to date!

[2017-05-23 21:23:05.671] FATAL: FTL received SIGTERM from PID/UID 1/0, scheduled to exit gracefully

rydagvb2sr

[BUG | ISSUE] Actual Behaviour:

[BUG | ISSUE] Steps to reproduce:

Log file output [if available]

output

Device specifics

OS:


_This template was created based on the work of [`udemy-dl`](https://github.com/nishad/udemy-dl/blob/master/LICENSE)._

Allow foreground execution for s6 style service

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

6

---

Simple request: since backgrounding/daemonizing is the default of pihole-FTL, please provide a -f argument to run it in the foreground to provide some more versatility with other supervisor style service managers like s6.

I just converted the pi-hole docker image to use s6-overlay, all my other services for the docker-pi-hole container have a option to run them int he foreground so that s6-supervisor can properly watch the long running process (also intake logs) and restart it if something goes wrong.

More details on s6 services: http://www.skarnet.org/software/s6/servicedir.html see the bullet points, the 5th in particular:

execute into the long-lived process that is to be supervised by s6-supervise, i.e. the real foo daemon. That process must not "background itself": being run by a supervision tree already makes it a "background" task.

s6 will just restart a service over and over when the process goes into background mode (learned this with php-fpm) since it is a supervisor style service manager, the exit of the run script means the service stopped in s6's mind and it triggers another run unless it was just told to stop the service.

I can work around this for now with something silly like while pgrep pihole-FTL ; do sleep 5 ; done at the end of my s6 service run script, so no rush.

Stack Buffer Overflow on unknown command

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?: 7

---

In https://github.com/pi-hole/FTL/blob/master/request.c#L151 the received client message is copied in "server_message" variable using "sprintf". "server_message" is a local variable with a maximum length given by "SOCKETBUFFERLEN" (1024 bytes ->

FTL/FTL.h

Line 55 in 07b1275

#define SOCKETBUFFERLEN 1024

).

If the client message is greater than 1024 bytes, it will overflow the buffer. The result is a stack buffer overflow.
It is not exploitable because the binary is compiled with the latest security measures (ASLR, Stack Canary, PIE..). But it still is a way to cause a DDoS to the FTL server.

[BUG | ISSUE] Steps to reproduce:

Connect to FTL and send a command with length greater than 1024.

Device specifics

Hardware Type: All devices are affected.
OS: All devices are affected.

This template was created based on the work of udemy-dl.

RPI2 testing [closed]

was going to attempt my first PR but i either dont have it setup right or my account is not able either way here is the info i was attempting to add

| Raspberry Pi 2 | Raspbian Jessie | armv7l | arm-linux-gnueabihf | @Technicalpyro |

Please provide a PPC32 Build

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

1

---

[BUG | ISSUE] Expected Behaviour:
FTL runs

[BUG | ISSUE] Actual Behaviour:
No binary available for CPU arch ppc as per lscpu output
Architecture: ppc
CPU op-mode(s): 32-bit
Byte Order: Big Endian
CPU(s): 1
On-line CPU(s) list: 0
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 1
Model: amcc,apollo3g
BogoMIPS: 1600.00
L1d cache: 32K
L1i cache: 32K
L2d cache: unknown size
L2i cache: unknown size

[BUG | ISSUE] Steps to reproduce:
Install pi-hole on a PPC based device.

Device specifics

Hardware Type: MyBook Live
OS: Linux

FTL crashed with SQL 21 error, previously worked fine

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

7

[BUG | ISSUE] Expected Behaviour:

[BUG | ISSUE] Actual Behaviour:

[BUG | ISSUE] Steps to reproduce:

Log file output [if available]

output

Finished initial log file parsing
[2017-07-16 08:47:23.472] -> Total DNS queries: 9090
[2017-07-16 08:47:23.472] -> Cached DNS queries: 2380
[2017-07-16 08:47:23.472] -> Blocked DNS queries: 388
[2017-07-16 08:47:23.472] -> Unknown DNS queries: 0
[2017-07-16 08:47:23.472] -> Unique domains: 999
[2017-07-16 08:47:23.472] -> Unique clients: 13
[2017-07-16 08:47:23.472] Successfully accessed setupVars.conf
[2017-07-16 08:47:23.473] Listening on port 4711 for incoming connections
[2017-07-16 08:48:00.023] SQL error (21): (null)
[2017-07-16 08:48:00.024] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-07-16 08:48:00.024] ----------------------------> FTL crashed! <----------------------------
[2017-07-16 08:48:00.024] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-07-16 08:48:00.024] > Please report a bug at https://github.com/pi-hole/FTL/issues
[2017-07-16 08:48:00.024] > and include in your report already the following details:
[2017-07-16 08:48:00.025] >
[2017-07-16 08:48:00.025] > Received signal: Segmentation fault
[2017-07-16 08:48:00.025] at address: 0
[2017-07-16 08:48:00.025] with code: SEGV_MAPERR (Address not mapped to object)
[2017-07-16 08:48:00.025] > Memory usage (structs): 346944
[2017-07-16 08:48:00.025] > Memory usage (dynamic): 23455
[2017-07-16 08:48:00.026] >
[2017-07-16 08:48:00.026] > Thank you for helping us to improve our FTL engine!
[2017-07-16 08:48:00.026] FTL terminated!

Device specifics

Hardware Type: rPi, VPS, etc: banana pi R1
OS: 3.4.113-bananian

This template was created based on the work of udemy-dl.

FTL terminates unexpectedly

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

1

---

[BUG | ISSUE] Expected Behaviour:
Do not crash

[BUG | ISSUE] Actual Behaviour:
Crash.

[BUG | ISSUE] Steps to reproduce:
Just start FTL en wait some time. Time between two crashes was two hours.

After the crash 'service pihole-FTL start' doesn't work. For some reason, running '/bin/sh -c "/usr/bin/pihole-FTL" "pihole"' as root does start FTL,

We have 273000 wildcards in the blocklist (based on squid blacklists).

Log file output [if available]
[2017-06-22 12:59:01.009] SQL error (5): database is locked
[2017-06-22 12:59:01.009] DB-GC error: Deleting queries due to age of entries failed!
[2017-06-22 12:59:01.009] SQL error (21): (null)
[2017-06-22 12:59:01.010] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-06-22 12:59:01.010] ----------------------------> FTL crashed! <----------------------------
[2017-06-22 12:59:01.010] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-06-22 12:59:01.010] > Please report a bug at https://github.com/pi-hole/FTL/issues
[2017-06-22 12:59:01.010] > and include in your report already the following details:
[2017-06-22 12:59:01.010] >
[2017-06-22 12:59:01.010] > Received signal: Segmentation fault
[2017-06-22 12:59:01.010] at address: 32
[2017-06-22 12:59:01.010] with code: SEGV_MAPERR (Address not mapped to object)
[2017-06-22 12:59:01.010] > Memory usage (structs): 2540116
[2017-06-22 12:59:01.010] > Memory usage (dynamic): 5535318
[2017-06-22 12:59:01.010] >
[2017-06-22 12:59:01.010] > Thank you for helping us to improve our FTL engine!
[2017-06-22 12:59:01.010] FTL terminated!

[2017-06-22 14:59:01.093] SQL error (21): (null)
[2017-06-22 14:59:01.094] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-06-22 14:59:01.094] ----------------------------> FTL crashed! <----------------------------
[2017-06-22 14:59:01.095] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-06-22 14:59:01.095] > Please report a bug at https://github.com/pi-hole/FTL/issues
[2017-06-22 14:59:01.095] > and include in your report already the following details:
[2017-06-22 14:59:01.096] >
[2017-06-22 14:59:01.096] > Received signal: Segmentation fault
[2017-06-22 14:59:01.096] at address: 32
[2017-06-22 14:59:01.097] with code: SEGV_MAPERR (Address not mapped to object)
[2017-06-22 14:59:01.097] > Memory usage (structs): 2540364
[2017-06-22 14:59:01.097] > Memory usage (dynamic): 5538235
[2017-06-22 14:59:01.097] >
[2017-06-22 14:59:01.098] > Thank you for helping us to improve our FTL engine!
[2017-06-22 14:59:01.098] FTL terminated!

Device specifics

Hardware Type: Hyper-V VM, 1 CPU, 768MB RAM, 8GB HD
OS: Ubuntu Server 16.04.2 LTS

installation error

to preface this i did not attempt this on a complete fresh install but you will see from the steps i think i did the correct sequence of commands

killed any existing pihole and pihole-FTL processes

rm -rf /etc/.pihole
git clone https://github.com/pi-hole/pi-hole.git /etc/.pihole/
cd /etc/.pihole/
git checkout new/FTL
rm -rf /var/html/admin/
gi clone https://github.com/pi-hole/AdminLTE.git
cd /var/html/admin/
git checkout new/FTL-nitegration
cd
pihole -r

got an error when it went to install (sorry should have taken a debug) that stated error of file not found and referred back to line 972 of the automated script

slept on it
did the same as the above the next morning but changed to using the new/FT:L-binary branch
once the script completed(successfully with no errors) i checked the web interface and saw FTL offline
i checked /etc/.pihole/ for a pihole-FTL executable ad saw none moved one from my testing directory started it and everything was working

OSMC issues

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

{6}

---

[BUG | ISSUE] Expected Behaviour:
FTL Operate correctly on OSMC and XBian

[BUG | ISSUE] Actual Behaviour:
https://discourse.pi-hole.net/t/pihole-ftl-refuses-to-start-after-upgrade-osmc/2895/12
seems to be failing to start

[BUG | ISSUE] Steps to reproduce:

-unsure what has changed in their installs

Log file output [if available]

running debug now

Device specifics

Hardware Type: rPi2B
OS: OSMC

This template was created based on the work of udemy-dl.

I have spun up OSMC on my Pi2B and as f yet have not had any issues. i will stand by for some troubleshooting on it if required and am willing to allow remote control through my firewall if that is easier

FTL segfaults in v2.11

I upgraded my Pihole to version 2.11 and now, on every boot, FTL crashes. Here is the relevant part of the log file:

[2017-10-03 09:37:03.774] FATAL ERROR: Trying to access overTime[-1], but maximum is 100
[2017-10-03 09:37:03.775] found in process_pihole_log() (line 363) in parser.c
[2017-10-03 09:37:03.775] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-10-03 09:37:03.775] ----------------------------> FTL crashed! <----------------------------
[2017-10-03 09:37:03.776] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-10-03 09:37:03.776] Please report a bug at https://github.com/pi-hole/FTL/issues
[2017-10-03 09:37:03.776] and include in your report already the following details:

[2017-10-03 09:37:03.776] FTL has been running for 52 seconds
[2017-10-03 09:37:03.777] FTL branch: (no branch)
[2017-10-03 09:37:03.777] FTL hash: v2.11
[2017-10-03 09:37:03.777] FTL date: 2017-09-28 11:01:31 -0700
[2017-10-03 09:37:03.777] FTL user: pihole
[2017-10-03 09:37:03.778]
Received signal: Segmentation fault
[2017-10-03 09:37:03.788] at address: 3209
[2017-10-03 09:37:03.789] with code: SEGV_MAPERR (Address not mapped to object)
[2017-10-03 09:37:03.789] Memory usage (structs): 343832
[2017-10-03 09:37:03.789] Memory usage (dynamic): 7301

[2017-10-03 09:37:03.789] Thank you for helping us to improve our FTL engine!
[2017-10-03 09:37:03.790] FTL terminated!

update issue

this may be more of a server(VPS) side issue but wanted to report it either way
potentially the hive mind can help me sort it out

Updated this morning on my pi ran flawlessly.
went to do the same on my VPS as i like to use it to test with as well and encountered the following

::: Checking for updates...
fatal: unable to access 'https://github.com/pi-hole/pi-hole.git/': Failed to connect to github.com port 443: Connection refused
::: Pi-hole Core:   up to date
::: FTL:            update available
:::
::: FTL out of date
:::
::: Downloading latest version of FTL...
:::  Detected x86_64 architecture
:::  Installing FTL... failed (error in getting latest release location from GitHub)

i dont have anything in the iptables on the VPS as the only thing connecting it me on VPN or on a randomized ssh port
i am pretty sure its something on the datacenter side as my home update ran without a hitchj or wondering if there is a more verbose pihole -up i can run to see more of whats going on

new feature - configurable number of top_domains

Hi, This is just to let you know that I have fiddled with your code to alter the number of domains reported from FTL when asking for "top-domains". This was so I could see a different number of the admin dashboard. At first I simply altered the "count" variable in request.c but then I changed it so I could set the number from setupVars.conf (it defaults to 10 if not set in setupVars.conf).

I have read your contributors guide and see that you would prefer bug fixes rather than additional features, so I don't want to go through a long journey learning how to create a pull request etc. Basically I have no idea how to contribute to a github project and don't want to waste your (or my) time learning how to do it with your project if you would prefer I didn't. I wouldn't want to make more of a mess than help! You should probably also know that I am definitely an amateur programmer, but I've dabbled enough over the years to know how to use StackOverflow!

Database file location option

Please allow us to confiure the database file location which is /etc/pihole by default. This could be a problem for tmpfs deployments...

FTL for mips64 bigendian needed.

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• [] The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

2

---

[BUG | ISSUE] Expected Behaviour:

[BUG | ISSUE] Actual Behaviour:

[BUG | ISSUE] Steps to reproduce:

Log file output [if available]

lscpu
Architecture:          mips64
Byte Order:            Big Endian
CPU(s):                2
On-line CPU(s) list:   0,1
Thread(s) per core:    1
Core(s) per socket:    1
Socket(s):             2
L1d cache:             16K
L1i cache:             32K
L2 cache:              128K

Device specifics

Hardware Type: rPi, VPS, etc
OS:
debian wheezy for mips64 big endian

This template was created based on the work of udemy-dl.

[Documentation] Describe FTL project focus

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

{2}

---

[ISSUE] Expected Behaviour:
Documentation enhancement required:
Both the pi-hole and AdminLTE have a description in README.md of what these projects focus on. This is lacking for FTL and should be added for visitors to clearly understand what does the FTL part in the pihole solution.
We should simply be able to find information to answer these questions at least:

• What does FTL acronym means?
• What does this project focus on?
• Is it mandatory or optional in the pihole solution?
  Today, a simple visitor does not know the goal of this project.

[BUG | ISSUE] Actual Behaviour:

[BUG | ISSUE] Steps to reproduce:

Log file output [if available]

output

Device specifics

Hardware Type: rPi, VPS, etc
OS:

This template was created based on the work of udemy-dl.

First discussion

based on the pihole script installing under the user "pihole" would it fit into the code that at the end of what im guessing will be the eventual bash/whiptail install script to have it run the following commands

sudo touch /etc/pihole/FTL.log
sudo touch /etc/pihole/FTL.pid
sudo touch /etc/pihole/FTL.lport
sudo chown pihole:pihole /etc/pihole/FTL.*

i would guess that is the eventual plan but dont want to assume

so far despite not running with a web interface as it is not agreeing at the moment every operation i have run has been successful and damn fast

query log unresponsive

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

{3}

---

[BUG | ISSUE] Expected Behaviour:
ability to view all queries in the query log when selected

[BUG | ISSUE] Actual Behaviour:
when clicking the all queries (instead of queries for the last 10 minutes) the web interface freezes

[BUG | ISSUE] Steps to reproduce:

-go to query log
-filter if you wish
-select the link at the top to view all rather than just the last 10 minutes

Log file output [if available]

kqwkw2i045

Device specifics

Hardware Type: rPi2B
OS: Raspbian stretch

i believe this to be an FTL error as it would seem to me to be the page hangs while trying to load the data my other thought is it is an admin interface issue but unsure f which

This template was created based on the work of udemy-dl.

FTL crashed!

Hello,

I just upgraded yesterday PiHole to latest version 3.1 with FTL version 2.9.2.

Everytime I start PiHole, reboot the VM, or just the FTL service, it takes a few minutes and crash.

This is the log file:
[2017-06-21 08:42:46.469] Finished initial log file parsing
[2017-06-21 08:42:46.469] -> Total DNS queries: 18709
[2017-06-21 08:42:46.469] -> Cached DNS queries: 10397
[2017-06-21 08:42:46.469] -> Blocked DNS queries: 169
[2017-06-21 08:42:46.469] -> Unknown DNS queries: 0
[2017-06-21 08:42:46.469] -> Unique domains: 1007
[2017-06-21 08:42:46.470] -> Unique clients: 28
[2017-06-21 08:42:46.470] Successfully accessed setupVars.conf
[2017-06-21 08:42:46.472] Listening on port 4711 for incoming connections
[2017-06-21 08:59:01.094] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-06-21 08:59:01.094] ----------------------------> FTL crashed! <----------------------------
[2017-06-21 08:59:01.094] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-06-21 08:59:01.094] > Please report a bug at https://github.com/pi-hole/FTL/issues
[2017-06-21 08:59:01.094] > and include in your report already the following details:
[2017-06-21 08:59:01.094] >
[2017-06-21 08:59:01.094] > Received signal: Segmentation fault
[2017-06-21 08:59:01.094] at address: 297783804246
[2017-06-21 08:59:01.094] with code: SEGV_MAPERR (Address not mapped to object)
[2017-06-21 08:59:01.094] > Memory usage (structs): 712908
[2017-06-21 08:59:01.095] > Memory usage (dynamic): 25993
[2017-06-21 08:59:01.095] >
[2017-06-21 08:59:01.095] > Thank you for helping us to improve our FTL engine!
[2017-06-21 08:59:01.095] FTL terminated!

Already tried a pihole repair, without any change.

This is running on an Ubuntu 17.04:
NAME="Ubuntu"
VERSION="17.04 (Zesty Zapus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 17.04"
VERSION_ID="17.04"

On a VM running with such characteristics:
=> 2 vCPUs
=> 768 Mb RAM

------------------------------------------------------------------<

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

1

[BUG | ISSUE] Expected Behaviour:

FTL deamon continues it's work

[BUG | ISSUE] Actual Behaviour:

FTL crashing with "Segmentation Fault"

[BUG | ISSUE] Steps to reproduce:

• Launch FTL (service pihole-FTL restart)
• wait...

Log file output [if available]

See at the beginning.

FTL is offline after restarting pihole.

[x] In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:**

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

1

I am a newbie to pihole and have just installed pihole on ubuntu 16.04

Fault: Dashboard showing zero stats.

Checked the FTL log and this shows FTL crashed

Log file output [if available]
Here is the requested part of the log file

2017-10-08 15:27:55.271] ########## FTL started! ##########
[2017-10-08 15:27:55.271] FTL branch: (no branch)
[2017-10-08 15:27:55.271] FTL hash: v2.11
[2017-10-08 15:27:55.271] FTL date: 2017-09-28 11:01:31 -0700
[2017-10-08 15:27:55.271] FTL user: pihole
[2017-10-08 15:27:55.271] Notice: Found no readable FTL config file
[2017-10-08 15:27:55.271] Using default settings
[2017-10-08 15:27:55.271] Starting config file parsing
[2017-10-08 15:27:55.271] SOCKET_LISTENING: only local
[2017-10-08 15:27:55.271] TIMEFRAME: Rolling 24h
[2017-10-08 15:27:55.271] QUERY_DISPLAY: Show queries
[2017-10-08 15:27:55.271] AAAA_QUERY_ANALYSIS: Show AAAA queries
[2017-10-08 15:27:55.271] MAXDBDAYS: max age for stored queries is 365 days
[2017-10-08 15:27:55.271] Finished config file parsing
[2017-10-08 15:27:55.273] Found no other running pihole-FTL process
[2017-10-08 15:27:55.274] PID of FTL process: 16210
[2017-10-08 15:27:55.299] Gravity list entries: 111579
[2017-10-08 15:27:55.299] No blacklist present
[2017-10-08 15:27:55.299] No wildcard blocking list present
[2017-10-08 15:27:55.299] Database initialized
[2017-10-08 15:27:55.299] Starting initial log file parsing
[2017-10-08 15:27:55.299] Reading from /var/log/pihole.log.1 (rw-r--r--)
[2017-10-08 15:27:55.299] Notice: Increasing forwarded struct size from 0 to 4 (188.00 B)
[2017-10-08 15:27:55.300] New forward server: 8.8.4.4 google-public-dns-b.google.com (0/4)
[2017-10-08 15:27:55.300] Notice: Increasing overTime struct size from 0 to 100 (4.23 KB)
[2017-10-08 15:27:55.301] New forward server: 8.8.8.8 google-public-dns-a.google.com (1/4)
[2017-10-08 15:27:55.301] Notice: Increasing queries struct size from 0 to 10000 (324.28 KB)
[2017-10-08 15:27:55.301] Notice: Increasing domains struct size from 0 to 1000 (356.28 KB)
[2017-10-08 15:27:55.301] Notice: Increasing clients struct size from 0 to 10 (356.53 KB)
[2017-10-08 15:27:55.301] New client: 127.0.0.1 localhost (0/10)
[2017-10-08 15:27:55.301] FATAL ERROR: Trying to access overTime[-1], but maximum is 100
[2017-10-08 15:27:55.301] found in process_pihole_log() (line 363) in parser.c
[2017-10-08 15:27:55.301] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-10-08 15:27:55.301] ----------------------------> FTL crashed! <----------------------------
[2017-10-08 15:27:55.301] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-10-08 15:27:55.301] Please report a bug at https://github.com/pi-hole/FTL/issues
[2017-10-08 15:27:55.301] and include in your report already the following details:

[2017-10-08 15:27:55.301] FTL has been running for 0 seconds
[2017-10-08 15:27:55.301] FTL branch: (no branch)
[2017-10-08 15:27:55.301] FTL hash: v2.11
[2017-10-08 15:27:55.301] FTL date: 2017-09-28 11:01:31 -0700
[2017-10-08 15:27:55.301] FTL user: pihole
[2017-10-08 15:27:55.301]
Received signal: Segmentation fault
[2017-10-08 15:27:55.301] at address: 4017
[2017-10-08 15:27:55.301] with code: SEGV_MAPERR (Address not mapped to object)
[2017-10-08 15:27:55.301] Memory usage (structs): 356428
[2017-10-08 15:27:55.301] Memory usage (dynamic): 310

[2017-10-08 15:27:55.301] Thank you for helping us to improve our FTL engine!
[2017-10-08 15:27:55.301] FTL terminated!

Device specifics

Hardware Type: PC running ubuntu 16.04 (dual boot with Windows 8.1)
OS:

I am running pihole locally (not VPN) and changed the router DNS settings to point to 192.168.1.2 (my fixed IP addr. As an aside, is this feasible?

This template was created based on the work of udemy-dl.

discussion

::: Downloading latest version of FTL...
:::  Detected ARM-hf architecture (armv7+)
:::  Installing FTL... transferred... done.
::: Restarting services...

Above appeared today when i ran an update despite being on the most up to date version we may want to look at making that a little more clear before FTL is live

Query Log "Unknown" entry

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

10

---

[BUG | ISSUE] Expected Behaviour:

git-lfs.github.com query log entry listed as OK

[BUG | ISSUE] Actual Behaviour:

git-lfs.github.com query log entry listed as Unknown but this does not seem to be reproducible

Interestingly, the Unknown status is gone after restarting FTL, so I assume FTL wasn't able to find it in pihole.log due to a yet unknown reason.

pihole.log excerpt

Jun 23 17:04:42 dnsmasq[20193]: query[A] git-lfs.github.com from 127.0.0.1
Jun 23 17:04:42 dnsmasq[20193]: forwarded git-lfs.github.com to 2001:1608:10:25::1c04:b12f
Jun 23 17:04:42 dnsmasq[20193]: reply git-lfs.github.com is <CNAME>
Jun 23 17:04:42 dnsmasq[20193]: reply github.map.fastly.net is 151.101.112.133

FTL Crashed! (First ever...)

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

{1}

---

[BUG | ISSUE] Expected Behaviour:

PiHole to continue running

[BUG | ISSUE] Actual Behaviour:

Out of the blue, FTL crashed. PiHole Admin page reported Lost Connection To API.

Unclear as to what had caused this. Memory usage is normal at around 42% (HomeBridge and ntopng running constantly). Temperature is normal (despite it being quite warm here...). No activity was happening on the Pi at the time...

up 30 days, 6:53, 3 users, load average: 0.33, 0.57, 0.65

Noticed some stuff in HomeBridge wasn't updating properly, Wifi calling failed but cached responses were still working...

Raising because the log states to... not sure if its any use and whether there is an explanation for this?

[BUG | ISSUE] Steps to reproduce:

Unknown cause...

Log file output [if available]

[2017-07-06 09:15:00.765] Notice: Increasing overTime struct size from 200 to 300 (729.40 KB)
[2017-07-06 17:52:58.687] Notice: Increasing queries struct size from 20000 to 30000 (1.05 MB)
[2017-07-06 23:55:24.947] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-07-06 23:55:24.947] ---------------------------->  FTL crashed!  <----------------------------
[2017-07-06 23:55:24.947] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-07-06 23:55:24.947] > Please report a bug at https://github.com/pi-hole/FTL/issues
[2017-07-06 23:55:24.947] > and include in your report already the following details:
[2017-07-06 23:55:24.947] >
[2017-07-06 23:55:24.947] > Received signal: Segmentation fault
[2017-07-06 23:55:24.947]        at address: 0
[2017-07-06 23:55:24.947]         with code: SEGV_MAPERR (Address not mapped to object)
[2017-07-06 23:55:24.947] > Memory usage (structs): 1009984
[2017-07-06 23:55:24.947] > Memory usage (dynamic): 44240
[2017-07-06 23:55:24.947] >
[2017-07-06 23:55:24.947] > Thank you for helping us to improve our FTL engine!
[2017-07-06 23:55:24.948] FTL terminated!

Device specifics

Hardware Type: rPi, VPS, etc
OS: rPi

This template was created based on the work of udemy-dl.

Queries forwarded may be computed incorrectly

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

10

---

[BUG | ISSUE] Expected Behaviour:
Neither of the counters in the result of >forward-dests should be larger than queries_forwarded from >stats.

[BUG | ISSUE] Actual Behaviour:
Not what is described above.

[BUG | ISSUE] Steps to reproduce:

• echo ">stats" | nc pi.hole 4711

domains_being_blocked 118558
dns_queries_today 14302
ads_blocked_today 286
ads_percentage_today 1.999720
unique_domains 514
queries_forwarded 4814
queries_cached 9202

• echo ">forward-dests" | nc pi.hole 4711

0 11640 2001:1608:10:25::9249:d69b 
1 9456 ::1 local
2 6341 2620:0:ccd::2 resolver2.ipv6-sandbox.opendns.com
3 5464 2620:0:ccc::2 resolver1.ipv6-sandbox.opendns.com
4 5269 2001:1608:10:25::1c04:b12f

top clients list has duplicates

@technicalpyro commented on Tue Jan 23 2018

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

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated.
• The issue I am reporting isn't a duplicate (see FAQs, closed issues, and open issues).

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

{3}

---

Expected behaviour:

web interface top clients lis not have duplicates with different query numbers

Actual behaviour:

Steps to reproduce:

{run the dev branches past that im unsure of what i did to cause this }

Debug token provided by uploading pihole -d log:

8jgnv8mc07

Troubleshooting undertaken, and/or other relevant information:

checked hosts file potentially that is causing the issues ?

• This template was created based on the work of udemy-dl.

Strange issue

@strrrn wrote:

---

mine is crashing with the following:

[2017-04-10 00:00:09.177] Notice: Increasing queries struct size from 0 to 10000 (281020.00 B)
[2017-04-10 00:00:09.178] Notice: Increasing overTime struct size from 0 to 100 (283420.00 B)
[2017-04-10 00:00:09.178] Notice: Increasing domains struct size from 0 to 1000 (299428.00 B)
[2017-04-10 00:00:11.968] Notice: Increasing domains struct size from 1000 to 2000 (338743.00 B)
[2017-04-10 00:00:11.994] Notice: Increasing queries struct size from 10000 to 20000 (619161.00 B)
[2017-04-10 00:00:15.548] Notice: Increasing overTime struct size from 100 to 200 (637702.00 B)
[2017-04-10 00:00:15.658] Notice: Increasing queries struct size from 20000 to 30000 (917877.00 B)
[2017-04-10 00:00:17.633] Notice: Increasing domains struct size from 2000 to 3000 (939924.00 B)
[2017-04-10 00:00:19.814] Notice: Increasing queries struct size from 30000 to 40000 (1225976.00 B)
[2017-04-10 00:00:21.281] Reading from /var/log/pihole.log
[2017-04-10 00:36:26.555] Notice: Increasing clients struct size from 0 to 20 (1239221.00 B)
[2017-04-10 00:36:26.759] Added new client: 2001:470:HIDDEN
[2017-04-10 00:36:26.760] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-04-10 00:36:26.760] ----------------------------> FTL crashed! <----------------------------
[2017-04-10 00:36:26.761] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-04-10 00:36:26.761] > Please report a bug at https://github.com/pi-hole/FTL/issues
[2017-04-10 00:36:26.761] > and include in your report already the following details:
[2017-04-10 00:36:26.761] >
[2017-04-10 00:36:26.762] > Received signal: Segmentation fault
[2017-04-10 00:36:26.762] at address: 513
[2017-04-10 00:36:26.762] with code: SEGV_MAPERR (Address not mapped to object)
[2017-04-10 00:36:26.763] > Memory usage (structs): 1173176
[2017-04-10 00:36:26.763] > Memory usage (dynamic): 66084
[2017-04-10 00:36:26.763] >
[2017-04-10 00:36:26.764] > Thank you for helping us to improve our FTL engine!
[2017-04-10 00:36:26.764] FTL terminated!

any updates on this?

FTL crashes instantly after start

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

1

---

[BUG | ISSUE] Expected Behaviour:
pihole-FTL should start and not crash

[BUG | ISSUE] Actual Behaviour:
pihole-FTL either crashes instantly after start or after a few hours

[BUG | ISSUE] Steps to reproduce:

• Start pihole-FTL, crashes almost instantly at the moment

Log file output [if available]

[2017-05-14 08:51:51.958] ########## FTL started! ##########
[2017-05-14 08:51:51.959] FTL branch: (no branch)
[2017-05-14 08:51:51.959] FTL hash: v2.7
[2017-05-14 08:51:51.959] FTL date: 2017-05-12 17:49:20 +0200
[2017-05-14 08:51:51.959] FTL user: pihole
[2017-05-14 08:51:51.959] Notice: Found no readable FTL config file
[2017-05-14 08:51:51.959]         Using default settings
[2017-05-14 08:51:51.959] Starting config file parsing
[2017-05-14 08:51:51.959]    SOCKET_LISTENING: only local
[2017-05-14 08:51:51.959]    TIMEFRAME: Rolling 24h
[2017-05-14 08:51:51.959]    QUERY_DISPLAY: Show queries
[2017-05-14 08:51:51.959] Finished config file parsing
[2017-05-14 08:51:51.963] Found no other running pihole-FTL process
[2017-05-14 08:51:51.964] PID of FTL process: 32302
[2017-05-14 08:51:52.130] Gravity list entries: 106239
[2017-05-14 08:51:52.130] No blacklist present
[2017-05-14 08:51:52.130] Notice: Increasing wildcards struct size from 0 to 1 (92.00 B)
[2017-05-14 08:51:52.130] Wildcard blocking list entries: 1
[2017-05-14 08:51:52.130] Starting initial log file parsing
[2017-05-14 08:51:52.131] Reading from /var/log/pihole.log.1 (rw-r--r--)
[2017-05-14 08:51:52.131] Notice: Increasing forwarded struct size from 0 to 4 (209.00 B)
[2017-05-14 08:51:52.137] New forward server: 139.59.208.246 ns1.he.de.dns.opennic.glue (0/4)
[2017-05-14 08:51:52.137] Notice: Increasing overTime struct size from 0 to 100 (4.25 KB)
[2017-05-14 08:51:52.141] New forward server: 62.113.203.55 secondary.server.edv-froehlich.de (1/4)
[2017-05-14 08:51:52.197] Notice: Increasing queries struct size from 0 to 10000 (324.41 KB)
[2017-05-14 08:51:52.198] Notice: Increasing domains struct size from 0 to 1000 (356.41 KB)
[2017-05-14 08:51:52.198] Notice: Increasing clients struct size from 0 to 10 (356.66 KB)
[2017-05-14 08:51:52.202] New client: 192.168.11.140 (0/10)
[2017-05-14 08:51:52.210] New client: 192.168.11.124 (1/10)
[2017-05-14 08:51:52.216] New client: 192.168.11.129 (2/10)
[2017-05-14 08:51:52.221] New client: 192.168.11.134 (3/10)
[2017-05-14 08:51:52.227] New client: 192.168.11.131 (4/10)
[2017-05-14 08:51:52.237] New client: 192.168.11.127 (5/10)
[2017-05-14 08:51:52.256] New client: 192.168.11.1 (6/10)
[2017-05-14 08:51:52.378] New client: 127.0.0.1 localhost (7/10)
[2017-05-14 08:51:52.705] New client: 192.168.11.100 (8/10)
[2017-05-14 08:51:53.099] New client: 192.168.11.113 (9/10)
[2017-05-14 08:51:53.099] Notice: Increasing clients struct size from 10 to 20 (360.95 KB)
[2017-05-14 08:51:53.110] New client: 192.168.11.149 (10/20)
[2017-05-14 08:51:53.122] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-05-14 08:51:53.122] ---------------------------->  FTL crashed!  <----------------------------
[2017-05-14 08:51:53.122] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-05-14 08:51:53.122] > Please report a bug at https://github.com/pi-hole/FTL/issues
[2017-05-14 08:51:53.122] > and include in your report already the following details:
[2017-05-14 08:51:53.122] >
[2017-05-14 08:51:53.122] > Received signal: Segmentation fault
[2017-05-14 08:51:53.122]        at address: 367155572728
[2017-05-14 08:51:53.122]         with code: SEGV_MAPERR (Address not mapped to object)
[2017-05-14 08:51:53.122] > Memory usage (structs): 356676
[2017-05-14 08:51:53.123] > Memory usage (dynamic): 5386
[2017-05-14 08:51:53.123] >
[2017-05-14 08:51:53.123] > Thank you for helping us to improve our FTL engine!
[2017-05-14 08:51:53.123] FTL terminated!

gdb backtrace

[2017-05-14 08:53:24.769] New client:  (11/20)

Program received signal SIGSEGV, Segmentation fault.
process_pihole_log (file=1) at parser.c:440
440	parser.c: No such file or directory.
(gdb) bt
#0  process_pihole_log (file=1) at parser.c:440
#1  0x0000000000000002 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Device specifics

Hardware Type: Pine64
Arch: aarch64
OS: Ubuntu 16.04.2
Kernel: 3.10.104-2-pine64-longsleep
Pi-hole Version: v3.0.1
FTL Version: v2.7

This template was created based on the work of udemy-dl.

FTL Crashed!

Upgraded yesterday and now FTL keeps going offline.

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• [] I have read and understood the contributors guide.
• [] The issue I am reporting can be replicated
• [] The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

0

[BUG | ISSUE] Expected Behaviour:

FTL to be online

[BUG | ISSUE] Actual Behaviour:

FTL crashing with Segmentation fault

[BUG | ISSUE] Steps to reproduce:

Upgrade to latest pihole v3.1 & FTL v2.9.2

Log file output [if available]

Log output;

[2017-06-21 18:59:01.115] > Please report a bug at https://github.com/pi-hole/FTL/issues
[2017-06-21 18:59:01.115] > and include in your report already the following details:
[2017-06-21 18:59:01.115] >
[2017-06-21 18:59:01.115] > Received signal: Segmentation fault
[2017-06-21 18:59:01.115] at address: 104
[2017-06-21 18:59:01.115] with code: SEGV_MAPERR (Address not mapped to object)
[2017-06-21 18:59:01.115] > Memory usage (structs): 356428
[2017-06-21 18:59:01.115] > Memory usage (dynamic): 7851
[2017-06-21 18:59:01.115] >
[2017-06-21 18:59:01.115] > Thank you for helping us to improve our FTL engine!
[2017-06-21 18:59:01.115] FTL terminated!

But before that output is does moan about the database being locked;

[2017-06-21 16:59:01.044] SQL error (5): database is locked
[2017-06-21 16:59:01.044] DB-GC error: Deleting queries due to age of entries failed!
[2017-06-21 17:59:01.100] SQL error (5): database is locked
[2017-06-21 17:59:01.109] DB-GC error: Deleting queries due to age of entries failed!

Device specifics

Hardware Type: VPS
OS: Debian

FTL crashed

Last night FTL suddenly stopped working

[2017-04-12 02:56:58.376] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-04-12 02:56:58.376] ---------------------------->  FTL crashed!  <----------------------------
[2017-04-12 02:56:58.376] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-04-12 02:56:58.377] > Please report a bug at https://github.com/pi-hole/FTL/issues
[2017-04-12 02:56:58.377] > and include in your report already the following details:
[2017-04-12 02:56:58.377] >
[2017-04-12 02:56:58.377] > Received signal: Segmentation fault
[2017-04-12 02:56:58.377]        at address: 409
[2017-04-12 02:56:58.377]         with code: SEGV_MAPERR (Address not mapped to object)
[2017-04-12 02:56:58.377] > Memory usage (structs): 877144
[2017-04-12 02:56:58.377] > Memory usage (dynamic): 39598
[2017-04-12 02:56:58.377] >
[2017-04-12 02:56:58.378] > Thank you for helping us to improve our FTL engine!
[2017-04-12 02:56:58.378] FTL terminated!

Trying to build for alpine docker (musl libc)

We talked about this is chat but I thought I should probably put everything in an issue for full documentation of things attempted/results, and to let others voice opinions. I have been trying to get my docker upgraded and part of that includes getting FTL in my primary docker tag, which is alpine traditionally. Now I could drop alpine support but the size differences is pretty big between alpine and debian and I'm sure I wouldn't be the only one disappointed.

The first approach I decided on trying was just use the musl-gcc wrapper application, which fills in the necessary paths and such for GCC compiling for musl. I didn't get very far in fixing the first compilation error, where it cannot seem to find the qsort's 4th arg type of __compar_fn_t

musl-gcc -c -o obj/main.o main.c -I. -Wall -Wextra -Wno-unused-parameter -D_FILE_OFFSET_BITS=64 -fstack-protector -D_FORTIFY_SOURCE=2 -O3 -Wl,-z,relro,-z,now -pie -fPIE -g3 -rdynamic -fno-omit-frame-pointer
musl-gcc -c -o obj/structs.o structs.c -I. -Wall -Wextra -Wno-unused-parameter -D_FILE_OFFSET_BITS=64 -fstack-protector -D_FORTIFY_SOURCE=2 -O3 -Wl,-z,relro,-z,now -pie -fPIE -g3 -rdynamic -fno-omit-frame-pointer
musl-gcc -c -o obj/log.o log.c -I. -Wall -Wextra -Wno-unused-parameter -D_FILE_OFFSET_BITS=64 -fstack-protector -D_FORTIFY_SOURCE=2 -O3 -Wl,-z,relro,-z,now -pie -fPIE -g3 -rdynamic -fno-omit-frame-pointer
musl-gcc -c -o obj/daemon.o daemon.c -I. -Wall -Wextra -Wno-unused-parameter -D_FILE_OFFSET_BITS=64 -fstack-protector -D_FORTIFY_SOURCE=2 -O3 -Wl,-z,relro,-z,now -pie -fPIE -g3 -rdynamic -fno-omit-frame-pointer
musl-gcc -c -o obj/parser.o parser.c -I. -Wall -Wextra -Wno-unused-parameter -D_FILE_OFFSET_BITS=64 -fstack-protector -D_FORTIFY_SOURCE=2 -O3 -Wl,-z,relro,-z,now -pie -fPIE -g3 -rdynamic -fno-omit-frame-pointer
musl-gcc -c -o obj/signals.o signals.c -I. -Wall -Wextra -Wno-unused-parameter -D_FILE_OFFSET_BITS=64 -fstack-protector -D_FORTIFY_SOURCE=2 -O3 -Wl,-z,relro,-z,now -pie -fPIE -g3 -rdynamic -fno-omit-frame-pointer
musl-gcc -c -o obj/socket.o socket.c -I. -Wall -Wextra -Wno-unused-parameter -D_FILE_OFFSET_BITS=64 -fstack-protector -D_FORTIFY_SOURCE=2 -O3 -Wl,-z,relro,-z,now -pie -fPIE -g3 -rdynamic -fno-omit-frame-pointer
musl-gcc -c -o obj/request.o request.c -I. -Wall -Wextra -Wno-unused-parameter -D_FILE_OFFSET_BITS=64 -fstack-protector -D_FORTIFY_SOURCE=2 -O3 -Wl,-z,relro,-z,now -pie -fPIE -g3 -rdynamic -fno-omit-frame-pointer
request.c: In function ‘getTopDomains’:
request.c:293:55: error: ‘__compar_fn_t’ undeclared (first use in this function)
   qsort(temparray, counters.domains, sizeof(int[2]), (__compar_fn_t)cmpdesc);
                                                       ^
request.c:293:55: note: each undeclared identifier is reported only once for each function it appears in
request.c:293:69: error: expected ‘)’ before ‘cmpdesc’
   qsort(temparray, counters.domains, sizeof(int[2]), (__compar_fn_t)cmpdesc);
                                                                     ^
request.c:295:69: error: expected ‘)’ before ‘cmpasc’
   qsort(temparray, counters.domains, sizeof(int[2]), (__compar_fn_t)cmpasc);
                                                                     ^
request.c: In function ‘getTopClients’:
request.c:400:54: error: ‘__compar_fn_t’ undeclared (first use in this function)
  qsort(temparray, counters.clients, sizeof(int[2]), (__compar_fn_t)cmpasc);
                                                      ^
request.c:400:68: error: expected ‘)’ before ‘cmpasc’
  qsort(temparray, counters.clients, sizeof(int[2]), (__compar_fn_t)cmpasc);
                                                                    ^
request.c: In function ‘getForwardDestinations’:
request.c:458:58: error: ‘__compar_fn_t’ undeclared (first use in this function)
  qsort(temparray, counters.forwarded+1, sizeof(int[2]), (__compar_fn_t)cmpdesc);
                                                          ^
request.c:458:72: error: expected ‘)’ before ‘cmpdesc’
  qsort(temparray, counters.forwarded+1, sizeof(int[2]), (__compar_fn_t)cmpdesc);
                                                                        ^
Makefile:44: recipe for target 'obj/request.o' failed
make: *** [obj/request.o] Error 1

I messed with that for a while but C is not my forte and I couldn't seem to google my way past that type error so I next tried a glibc static binary...it seems to actually start up inside of my alpine docker but it does have these 2 warnings, which I'm not sure if that'll cause problems down the road or not...this is more an FYI.

Note: -pie -fPIE are replaced by -static -fPIC to get this build.

root@d5f38ecee56c:/usr/src/myapp# make clean ; make
rm -f obj/*.o pihole-FTL
gcc -c -o obj/main.o main.c -I. -Wall -Wextra -Wno-unused-parameter -D_FILE_OFFSET_BITS=64 -fstack-protector -D_FORTIFY_SOURCE=2 -O3 -Wl,-z,relro,-z,now -static -fPIC -g3 -rdynamic -fno-omit-frame-pointer
gcc -c -o obj/structs.o structs.c -I. -Wall -Wextra -Wno-unused-parameter -D_FILE_OFFSET_BITS=64 -fstack-protector -D_FORTIFY_SOURCE=2 -O3 -Wl,-z,relro,-z,now -static -fPIC -g3 -rdynamic -fno-omit-frame-pointer
gcc -c -o obj/log.o log.c -I. -Wall -Wextra -Wno-unused-parameter -D_FILE_OFFSET_BITS=64 -fstack-protector -D_FORTIFY_SOURCE=2 -O3 -Wl,-z,relro,-z,now -static -fPIC -g3 -rdynamic -fno-omit-frame-pointer
gcc -c -o obj/daemon.o daemon.c -I. -Wall -Wextra -Wno-unused-parameter -D_FILE_OFFSET_BITS=64 -fstack-protector -D_FORTIFY_SOURCE=2 -O3 -Wl,-z,relro,-z,now -static -fPIC -g3 -rdynamic -fno-omit-frame-pointer
gcc -c -o obj/parser.o parser.c -I. -Wall -Wextra -Wno-unused-parameter -D_FILE_OFFSET_BITS=64 -fstack-protector -D_FORTIFY_SOURCE=2 -O3 -Wl,-z,relro,-z,now -static -fPIC -g3 -rdynamic -fno-omit-frame-pointer
gcc -c -o obj/signals.o signals.c -I. -Wall -Wextra -Wno-unused-parameter -D_FILE_OFFSET_BITS=64 -fstack-protector -D_FORTIFY_SOURCE=2 -O3 -Wl,-z,relro,-z,now -static -fPIC -g3 -rdynamic -fno-omit-frame-pointer
gcc -c -o obj/socket.o socket.c -I. -Wall -Wextra -Wno-unused-parameter -D_FILE_OFFSET_BITS=64 -fstack-protector -D_FORTIFY_SOURCE=2 -O3 -Wl,-z,relro,-z,now -static -fPIC -g3 -rdynamic -fno-omit-frame-pointer
gcc -c -o obj/request.o request.c -I. -Wall -Wextra -Wno-unused-parameter -D_FILE_OFFSET_BITS=64 -fstack-protector -D_FORTIFY_SOURCE=2 -O3 -Wl,-z,relro,-z,now -static -fPIC -g3 -rdynamic -fno-omit-frame-pointer
gcc -c -o obj/grep.o grep.c -I. -Wall -Wextra -Wno-unused-parameter -D_FILE_OFFSET_BITS=64 -fstack-protector -D_FORTIFY_SOURCE=2 -O3 -Wl,-z,relro,-z,now -static -fPIC -g3 -rdynamic -fno-omit-frame-pointer
gcc -c -o obj/setupVars.o setupVars.c -I. -Wall -Wextra -Wno-unused-parameter -D_FILE_OFFSET_BITS=64 -fstack-protector -D_FORTIFY_SOURCE=2 -O3 -Wl,-z,relro,-z,now -static -fPIC -g3 -rdynamic -fno-omit-frame-pointer
gcc -c -o obj/args.o args.c -I. -Wall -Wextra -Wno-unused-parameter -D_FILE_OFFSET_BITS=64 -fstack-protector -D_FORTIFY_SOURCE=2 -O3 -Wl,-z,relro,-z,now -static -fPIC -g3 -rdynamic -fno-omit-frame-pointer
gcc -c -o obj/flush.o flush.c -I. -Wall -Wextra -Wno-unused-parameter -D_FILE_OFFSET_BITS=64 -fstack-protector -D_FORTIFY_SOURCE=2 -O3 -Wl,-z,relro,-z,now -static -fPIC -g3 -rdynamic -fno-omit-frame-pointer
gcc -c -o obj/threads.o threads.c -I. -Wall -Wextra -Wno-unused-parameter -D_FILE_OFFSET_BITS=64 -fstack-protector -D_FORTIFY_SOURCE=2 -O3 -Wl,-z,relro,-z,now -static -fPIC -g3 -rdynamic -fno-omit-frame-pointer
gcc -c -o obj/gc.o gc.c -I. -Wall -Wextra -Wno-unused-parameter -D_FILE_OFFSET_BITS=64 -fstack-protector -D_FORTIFY_SOURCE=2 -O3 -Wl,-z,relro,-z,now -static -fPIC -g3 -rdynamic -fno-omit-frame-pointer
gcc -c -o obj/config.o config.c -I. -Wall -Wextra -Wno-unused-parameter -D_FILE_OFFSET_BITS=64 -fstack-protector -D_FORTIFY_SOURCE=2 -O3 -Wl,-z,relro,-z,now -static -fPIC -g3 -rdynamic -fno-omit-frame-pointer
gcc -v -I. -Wall -Wextra -Wno-unused-parameter -D_FILE_OFFSET_BITS=64 -fstack-protector -D_FORTIFY_SOURCE=2 -O3 -Wl,-z,relro,-z,now -static -fPIC -g3 -rdynamic -fno-omit-frame-pointer   -o pihole-FTL obj/main.o obj/structs.o obj/log.o obj/daemon.o obj/parser.o obj/signals.o obj/socket.o obj/request.o obj/grep.o obj/setupVars.o obj/args.o obj/flush.o obj/threads.o obj/gc.o obj/config.o -pthread
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-unknown-linux-gnu/4.9.4/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: /usr/src/gcc/configure --disable-multilib --enable-languages=c,c++,fortran,go
Thread model: posix
gcc version 4.9.4 (GCC)
COMPILER_PATH=/usr/local/libexec/gcc/x86_64-unknown-linux-gnu/4.9.4/:/usr/local/libexec/gcc/x86_64-unknown-linux-gnu/4.9.4/:/usr/local/libexec/gcc/x86_64-unknown-linux-gnu/:/usr/local/lib/gcc/x86_64-unknown-linux-gnu/4.9.4/:/usr/local/lib/gcc/x86_64-unknown-linux-gnu/
LIBRARY_PATH=/usr/local/lib/gcc/x86_64-unknown-linux-gnu/4.9.4/:/usr/local/lib/gcc/x86_64-unknown-linux-gnu/4.9.4/../../../../lib64/:/lib/x86_64-linux-gnu/:/lib/../lib64/:/usr/lib/x86_64-linux-gnu/:/usr/local/lib/gcc/x86_64-unknown-linux-gnu/4.9.4/../../../:/lib/:/usr/lib/
COLLECT_GCC_OPTIONS='-v' '-I' '.' '-Wall' '-Wextra' '-Wno-unused-parameter' '-D' '_FILE_OFFSET_BITS=64' '-fstack-protector' '-D' '_FORTIFY_SOURCE=2' '-O3' '-static' '-fPIC' '-g3' '-rdynamic' '-fno-omit-frame-pointer' '-o' 'pihole-FTL' '-pthread' '-mtune=generic' '-march=x86-64'
 /usr/local/libexec/gcc/x86_64-unknown-linux-gnu/4.9.4/collect2 -plugin /usr/local/libexec/gcc/x86_64-unknown-linux-gnu/4.9.4/liblto_plugin.so -plugin-opt=/usr/local/libexec/gcc/x86_64-unknown-linux-gnu/4.9.4/lto-wrapper -plugin-opt=-fresolution=/tmp/ccqMEy2b.res -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_eh -plugin-opt=-pass-through=-lpthread -plugin-opt=-pass-through=-lc -m elf_x86_64 -static -o pihole-FTL /usr/lib/x86_64-linux-gnu/crt1.o /usr/lib/x86_64-linux-gnu/crti.o /usr/local/lib/gcc/x86_64-unknown-linux-gnu/4.9.4/crtbeginT.o -L/usr/local/lib/gcc/x86_64-unknown-linux-gnu/4.9.4 -L/usr/local/lib/gcc/x86_64-unknown-linux-gnu/4.9.4/../../../../lib64 -L/lib/x86_64-linux-gnu -L/lib/../lib64 -L/usr/lib/x86_64-linux-gnu -L/usr/local/lib/gcc/x86_64-unknown-linux-gnu/4.9.4/../../.. -z relro -z now obj/main.o obj/structs.o obj/log.o obj/daemon.o obj/parser.o obj/signals.o obj/socket.o obj/request.o obj/grep.o obj/setupVars.o obj/args.o obj/flush.o obj/threads.o obj/gc.o obj/config.o --start-group -lgcc -lgcc_eh -lpthread -lc --end-group /usr/local/lib/gcc/x86_64-unknown-linux-gnu/4.9.4/crtend.o /usr/lib/x86_64-linux-gnu/crtn.o
obj/daemon.o: In function `getUserName':
/usr/src/myapp/daemon.c:225: warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
obj/parser.o: In function `resolveHostname':
/usr/src/myapp/parser.c:618: warning: Using 'gethostbyaddr' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking

working I guess?

bash-4.3# cat /etc/issue
Welcome to Alpine Linux 3.5
Kernel \r on an \m (\l)
bash-4.3# telnet 127.0.0.1 4711
>top-clients
0 2 172.17.0.5
1 2 ::1
---EOM---

>forward-dest
0 10 8.8.4.4
1 2 8.8.8.8
---EOM---

I'll keep you posted as I go down the static glibc road more since I'm in over my head with musl libc compilation which sounds like it may require some rewriting.

api string format?

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

5

---

i just have a few questions on the new format:

i am trying to expand the bitbar plugin to use the new api calls, i have integrated the enable and disable.

1: i would like the status to be displayed in the bitbar but can't figure out the call

2: is there a way to combine the enable and disable commands to 1 line based on a true/false
IE: if status disabled true enable or disabled fasle disable

below is my current code, status: is the place holder. hashed password removed for security:

import urllib2
import json

If you have UTF-8 problems then uncomment next 3 lines

#import sys
#reload(sys)
#sys.setdefaultencoding("utf-8")

Change to Your Pi-Hole Admin Console Url

pihole = "http://pi-hole.local/admin/"

Change to Your Pi-Hole Admin Console Hashed Password (see WEBPASSWORD in /etc/pihole/setupVars.conf)

passwd = "hashed password here"

try:
url = pihole + "api.php?summary"
result = urllib2.urlopen(url, timeout = 15).read()
json = json.loads(result)
print "| image=iVBORw0KGgoAAAANSUhEUgAAACgAAAAoCAYAAACM/rhtAAAACXBIWXMAABYlAAAWJQFJUiTwAAAKT2lDQ1BQaG90b3Nob3AgSUNDIHByb2ZpbGUAAHjanVNnVFPpFj333vRCS4iAlEtvUhUIIFJCi4AUkSYqIQkQSoghodkVUcERRUUEG8igiAOOjoCMFVEsDIoK2AfkIaKOg6OIisr74Xuja9a89+bN/rXXPues852zzwfACAyWSDNRNYAMqUIeEeCDx8TG4eQuQIEKJHAAEAizZCFz/SMBAPh+PDwrIsAHvgABeNMLCADATZvAMByH/w/qQplcAYCEAcB0kThLCIAUAEB6jkKmAEBGAYCdmCZTAKAEAGDLY2LjAFAtAGAnf+bTAICd+Jl7AQBblCEVAaCRACATZYhEAGg7AKzPVopFAFgwABRmS8Q5ANgtADBJV2ZIALC3AMDOEAuyAAgMADBRiIUpAAR7AGDIIyN4AISZABRG8lc88SuuEOcqAAB4mbI8uSQ5RYFbCC1xB1dXLh4ozkkXKxQ2YQJhmkAuwnmZGTKBNA/g88wAAKCRFRHgg/P9eM4Ors7ONo62Dl8t6r8G/yJiYuP+5c+rcEAAAOF0ftH+LC+zGoA7BoBt/qIl7gRoXgugdfeLZrIPQLUAoOnaV/Nw+H48PEWhkLnZ2eXk5NhKxEJbYcpXff5nwl/AV/1s+X48/Pf14L7iJIEyXYFHBPjgwsz0TKUcz5IJhGLc5o9H/LcL//wd0yLESWK5WCoU41EScY5EmozzMqUiiUKSKcUl0v9k4t8s+wM+3zUAsGo+AXuRLahdYwP2SycQWHTA4vcAAPK7b8HUKAgDgGiD4c93/+8//UegJQCAZkmScQAAXkQkLlTKsz/HCAAARKCBKrBBG/TBGCzABhzBBdzBC/xgNoRCJMTCQhBCCmSAHHJgKayCQiiGzbAdKmAv1EAdNMBRaIaTcA4uwlW4Dj1wD/phCJ7BKLyBCQRByAgTYSHaiAFiilgjjggXmYX4IcFIBBKLJCDJiBRRIkuRNUgxUopUIFVIHfI9cgI5h1xGupE7yAAygvyGvEcxlIGyUT3UDLVDuag3GoRGogvQZHQxmo8WoJvQcrQaPYw2oefQq2gP2o8+Q8cwwOgYBzPEbDAuxsNCsTgsCZNjy7EirAyrxhqwVqwDu4n1Y8+xdwQSgUXACTYEd0IgYR5BSFhMWE7YSKggHCQ0EdoJNwkDhFHCJyKTqEu0JroR+cQYYjIxh1hILCPWEo8TLxB7iEPENyQSiUMyJ7mQAkmxpFTSEtJG0m5SI+ksqZs0SBojk8naZGuyBzmULCAryIXkneTD5DPkG+Qh8lsKnWJAcaT4U+IoUspqShnlEOU05QZlmDJBVaOaUt2ooVQRNY9aQq2htlKvUYeoEzR1mjnNgxZJS6WtopXTGmgXaPdpr+h0uhHdlR5Ol9BX0svpR+iX6AP0dwwNhhWDx4hnKBmbGAcYZxl3GK+YTKYZ04sZx1QwNzHrmOeZD5lvVVgqtip8FZHKCpVKlSaVGyovVKmqpqreqgtV81XLVI+pXlN9rkZVM1PjqQnUlqtVqp1Q61MbU2epO6iHqmeob1Q/pH5Z/YkGWcNMw09DpFGgsV/jvMYgC2MZs3gsIWsNq4Z1gTXEJrHN2Xx2KruY/R27iz2qqaE5QzNKM1ezUvOUZj8H45hx+Jx0TgnnKKeX836K3hTvKeIpG6Y0TLkxZVxrqpaXllirSKtRq0frvTau7aedpr1Fu1n7gQ5Bx0onXCdHZ4/OBZ3nU9lT3acKpxZNPTr1ri6qa6UbobtEd79up+6Ynr5egJ5Mb6feeb3n+hx9L/1U/W36p/VHDFgGswwkBtsMzhg8xTVxbzwdL8fb8VFDXcNAQ6VhlWGX4YSRudE8o9VGjUYPjGnGXOMk423GbcajJgYmISZLTepN7ppSTbmmKaY7TDtMx83MzaLN1pk1mz0x1zLnm+eb15vft2BaeFostqi2uGVJsuRaplnutrxuhVo5WaVYVVpds0atna0l1rutu6cRp7lOk06rntZnw7Dxtsm2qbcZsOXYBtuutm22fWFnYhdnt8Wuw+6TvZN9un2N/T0HDYfZDqsdWh1+c7RyFDpWOt6azpzuP33F9JbpL2dYzxDP2DPjthPLKcRpnVOb00dnF2e5c4PziIuJS4LLLpc+Lpsbxt3IveRKdPVxXeF60vWdm7Obwu2o26/uNu5p7ofcn8w0nymeWTNz0MPIQ+BR5dE/C5+VMGvfrH5PQ0+BZ7XnIy9jL5FXrdewt6V3qvdh7xc+9j5yn+M+4zw33jLeWV/MN8C3yLfLT8Nvnl+F30N/I/9k/3r/0QCngCUBZwOJgUGBWwL7+Hp8Ib+OPzrbZfay2e1BjKC5QRVBj4KtguXBrSFoyOyQrSH355jOkc5pDoVQfujW0Adh5mGLw34MJ4WHhVeGP45wiFga0TGXNXfR3ENz30T6RJZE3ptnMU85ry1KNSo+qi5qPNo3ujS6P8YuZlnM1VidWElsSxw5LiquNm5svt/87fOH4p3iC+N7F5gvyF1weaHOwvSFpxapLhIsOpZATIhOOJTwQRAqqBaMJfITdyWOCnnCHcJnIi/RNtGI2ENcKh5O8kgqTXqS7JG8NXkkxTOlLOW5hCepkLxMDUzdmzqeFpp2IG0yPTq9MYOSkZBxQqohTZO2Z+pn5mZ2y6xlhbL+xW6Lty8elQfJa7OQrAVZLQq2QqboVFoo1yoHsmdlV2a/zYnKOZarnivN7cyzytuQN5zvn//tEsIS4ZK2pYZLVy0dWOa9rGo5sjxxedsK4xUFK4ZWBqw8uIq2Km3VT6vtV5eufr0mek1rgV7ByoLBtQFr6wtVCuWFfevc1+1dT1gvWd+1YfqGnRs+FYmKrhTbF5cVf9go3HjlG4dvyr+Z3JS0qavEuWTPZtJm6ebeLZ5bDpaql+aXDm4N2dq0Dd9WtO319kXbL5fNKNu7g7ZDuaO/PLi8ZafJzs07P1SkVPRU+lQ27tLdtWHX+G7R7ht7vPY07NXbW7z3/T7JvttVAVVN1WbVZftJ+7P3P66Jqun4lvttXa1ObXHtxwPSA/0HIw6217nU1R3SPVRSj9Yr60cOxx++/p3vdy0NNg1VjZzG4iNwRHnk6fcJ3/ceDTradox7rOEH0x92HWcdL2pCmvKaRptTmvtbYlu6T8w+0dbq3nr8R9sfD5w0PFl5SvNUyWna6YLTk2fyz4ydlZ19fi753GDborZ752PO32oPb++6EHTh0kX/i+c7vDvOXPK4dPKy2+UTV7hXmq86X23qdOo8/pPTT8e7nLuarrlca7nuer21e2b36RueN87d9L158Rb/1tWeOT3dvfN6b/fF9/XfFt1+cif9zsu72Xcn7q28T7xf9EDtQdlD3YfVP1v+3Njv3H9qwHeg89HcR/cGhYPP/pH1jw9DBY+Zj8uGDYbrnjg+OTniP3L96fynQ89kzyaeF/6i/suuFxYvfvjV69fO0ZjRoZfyl5O/bXyl/erA6xmv28bCxh6+yXgzMV70VvvtwXfcdx3vo98PT+R8IH8o/2j5sfVT0Kf7kxmTk/8EA5jz/GMzLdsAAAAgY0hSTQAAeiUAAICDAAD5/wAAgOkAAHUwAADqYAAAOpgAABdvkl/FRgAAGThJREFUeAEAKBnX5gH///8AAAAAAAAAAAAAAAAAAAAAAAGkGgAAAAAAAAAAXAAAAJQAAADsAAEA4gAAANAA/wC9AAAAxAABAPEA/wAAAAABAAABAAAAAQAAAAAAAAAAAQAA/gMAAAH9AAD//gAAAQAAAAAAAAD/AAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAP9b5gAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAAAQAAAAH2AAAADgAAACMA/wBBAP8AcQAAALQAAADHAAAAXAAAAAIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAAAAAAAAAAAAAAAAAAAAv8AAAL/AAAC/9MAAAD2AAAAAAAAAAAAAAAAAAAAAAAAACkA/wCjAAAApgAAAAkAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/wAAAP8AAAD/4gAAANUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABXAAD/rwAAAAoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAkAAAANAAAAAgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAAAAAAAAAAAAAAAAAAAAP8BAAD/AQAA/wH5AAEAuwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABHAAD/gAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAAE0AAACkAAAA0QAAANEAAAAyAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAEAAAABAAAAAQCzAAD/AAAA/wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/wB1AP8ARAD/AAAA/gMAAAAAAAAA/x4AAACuAAAAsgD/AFoAAAAlAAAAGgD/AQAA/wEAAP8BAAD/AQAA/wEAAP8BAAD/AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAAAAAAAAAAAAAD+AgAA/gIAAP4CAAD+AskAAAKfAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAB/wAAAP9gAP8AAAAB/QAAAP0UAP4AtAAAAE0A/wAAAAAAAAAAAAAAAAHiAAD/2gAA/wAAAP8AAAD/AAAA/wAAAP8AAAD/AAAAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAAAAAAAAAAAAAAAAAAAAP8BAAD/AQAA/wEAAP8BAAD/AYcA/wHlAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAP8BAAD/AFQAAP8fAAD+AAAB/YoAAf8tAAAAAAAAAAAAAAAAAAD/AAAAAKcAAALyAAACAAAAAgAAAAIAAAACAAAAAgAAAAIAAAAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA2wAAAGUAAAD6AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABwAAAB0A/gEdAP8BYQAAAAAAAAAAAAAAAAAA/wAAAQDhAAABmgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAtwAAAFkAAADqAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAP8BJwAAAEQAAAAAAP8AAAAAAAAAAP8AAAAB9wD+A2QA/wDlAP8AAAD/AAAA/wAAAP8AAAD/AAAA/wAAAP8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAArgAAAD4AAAG4AAAAAAAAAAAA/wAAAP8AAAAAAAAAAwBHAAEAWAAGAAAABwEAAAIBAAAFAdoA/wJCAP8CvAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAP4A2QAIAE4ACQJAAAIBYAAHAT4ABQEJAP3/9wD8ADcABP8CAPD/zAH//94ACQG4/+//sgARAu0A/QIAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAWBAAAAAAAAAAAAAAAAAAAAP8AAAL+AAAB/wAABwIAAOL8+wDP97sDDgO7CgUBAPTY+jEd4fpgLf0APQcGAPnV6P6u5t/7qfT0/eIAIAQAAWkTAAD1AAD/Af8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABPAAAAAAAAAAAAAAAAAAAAAAAAAf///wAAAAAAAAAAAAAAAAAAAAAAAWMSAAAAAAAAAAAAAAAAAAAAAAAAAf4AAAAAAAAOAgAAy/kAAMT2AAIAAABJAABPRwAAdWAAADsNAAAAAAAAAPwAAACrAADoeQAAfuEAAJsCAAAAAQAAAP0AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA////AAAAAAAAAAAAAAAAAAAAAAAA////AP///wD///8A////AP///wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAOAAAhM0AAP//AAD//wAA//8AAP//AAD//wAA//8AAP/YAAD/JgAAfwAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD///8A////AP///wD///8A////AAD///8A////AP///wD///8A////AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADYAAIXqAAD//wAA//8AAP//AAD//wAA//8AAP//AAD//wAA//8AAP+oAAD/DwAAegAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAP///wD///8A////AP///wD///8AAP///wD///8A////AP///wD///8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAqAACB5QAA//8AAP//AAD//wAA//8AAP//AAD//wAA//8AAP//AAD//wAA/+wAAP+jAAD/MgAAcQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA////AP///wD///8A////AP///wAA////AP///wD///8A////AP///wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAALAAAf90AAP//AAD//wAA//8AAP//AAD//wAA//8AAP//AAD//wAA//8AAP//AAD/4AAA/7gAAP/cAAD/JgAAbwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD///8A////AP///wD///8A////AAD///8A////AP///wD///8A////AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADQAAHjdAAD//wAA//8AAP//AAD//wAA//8AAP//AAD//wAA//8AAP//AAD//wAA//8AAP/oAAD/kgAA/+wAAP/bAAD/JAAAawAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAP///wD///8A////AP///wD///8AAP///wD///8A////AP///wD///8AAAAAAAAAAAAAAAAAAAAAAAAAAAA2AAB14QAA//8AAP/6AAD//wAA//8AAP//AAD//wAA//8AAP//AAD//wAA//8AAP//AAD//wAA/90AAP+UAAD/9gAA//8AAP/TAAD/HwAAXgAAAAADAAAAAQAAAAAAAAAAAAAA////AP///wD///8A////AP///wAA////AP///wD///8A////AP///wAAAAAAAAAAAAAAAAAAAAAADgAAbp8AAP/HAAD/mQAA/5cAAP++AAD/+QAA//8AAP//AAD//wAA//8AAP//AAD//wAA//8AAP//AAD/lgAA/5UAAP//AAD//wAA//8AAP/LAAD+IgAAVSAAAAAUAAAAAAAAAAAAAAD///8A////AP///wD///8A////AAD///8A////AP///wD///8A////AAAAAAAAAAAAAAAAAAgAAGyiAAD/6AAA/9UAAP/ZAAD/xQAA/3sAAP9PAAD/wwAA//8AAP//AAD//wAA//8AAP//AAD//wAA/8YAAP8/AAD/2wAA//8AAP//AAD//wAA//8AAP+9AAD6HwAATwkAAAAAAAAAAAAAAP///wD///8A////AP///wD///8AAP///wD///8A////AP///wD///8AAAAAAAAAAAAYAABcxQAA//8AAP//AAD//wAA//8AAP//AAD//wAA/44AAP8KAAD/dAAA/9sAAP//AAD//wAA//8AAP/AAAD/FQAA/5QAAP//AAD//wAA//8AAP//AAD//wAA//8AAP+oAADxBwAAPAAAAAAAAAAA////AP///wD///8A////AP///wAA////AP///wD///8A////AP///wAAAAAAAAAAG54AAOL/AAD//wAA//8AAP//AAD//wAA//8AAP//AAD//wAA/4YAAP8AAAD/EAAA/0IAAP9hAAD/QwAA/wAAAP9eAAD//wAA//8AAP//AAD//wAA//8AAP//AAD//wAA//8AAP94AADKAAAAAAAAAAD///8A////AP///wD///8A////AAD///8A////AP///wD///8A////AAAAACwuAACI7AAA//8AAP//AAD//wAA//8AAP//AAD//wAA//8AAP//AAD/5QAA/yAAAP8AAAD/AAAA/wAAAP8AAAD/BQAA/9cAAP//AAD//wAA//8AAP//AAD//wAA//8AAP//AAD//wAA/9sAAP0NAABVAAAAC////wD///8A////AP///wD///8AAP///wD///8A////AP///wD///8AGQAAiG0AAOX/AAD//wAA//8AAP//AAD//wAA//8AAP//AAD//wAA//8AAP/9AAD/UAAA/wAAAP8AAAD/AAAA/wAAAP9IAAD/+QAA//8AAP//AAD//wAA//8AAP//AAD//wAA//8AAP//AAD/+gAA/0oAAM0DAABu////AP///wD///8A////AP///wACAAAAAAAAAAAAAAAAAAAAAAAAAAAJAAALCAAABwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAPwAAAD4AAAAAAAAAAAAAAAAAAAAAAAAAB0AAAAGAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAFAAAAEwAAIQcAACcAAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAAAAAAAAAAAAOAAALXPAAC++AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA5wAAAM4AAAAAAAAAAAAAAAAAAAAAAAAA8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAPUAAADiAADI9gAAwwAAAAAAAAAAAAAAAAAAAAAAAAAAAP///wD///8A////AP///wD///8AAAAAAAIAADvSAADz/wAA//8AAP//AAD//wAA//8AAP//AAD//wAA//8AAP+YAAD/AAAA/wgAAP8VAAD/CAAA/wAAAP8MAAD/2wAA//8AAP//AAD//wAA//8AAP//AAD//wAA//8AAP//AAD/0gAA8wEAADsAAAAA////AP///wD///8A////AP///wAA////AP///wD///8A////AP///wAAAAAAAAAAAEkAAKH8AAD//wAA//8AAP//AAD//wAA//8AAP//AAD/1gAA/w8AAP9ZAAD/vQAA/9oAAP++AAD/gAAA/xAAAP87AAD/9AAA//8AAP//AAD//wAA//8AAP//AAD//wAA//wAAP9IAACeAAAAAAAAAAD///8A////AP///wD///8A////AAD///8A////AP///wD///8A////AAAAAAAAAAAAAAAAEnMAAL//AAD//wAA//8AAP//AAD//wAA//8AAP9JAAD/eAAA//8AAP//AAD//wAA//8AAP//AAD/5QAA/2AAAP9eAAD/1AAA//8AAP//AAD//wAA//8AAP/sAAD/VQAAugAAAA4AAAAAAAAAAP///wD///8A////AP///wD///8AAP///wD///8A////AP///wD///8AAAAAAAAAAAAAAAAAAAAAE3UAAMb/AAD//wAA//8AAP//AAD/oAAA/1kAAP/2AAD//wAA//8AAP//AAD//wAA//8AAP//AAD//wAA/78AAP+IAAD/mgAA/64AAP/GAAD/zAAA/zgAAMIAAAAPAAAAAAAAAAAAAAAA////AP///wD///8A////AP///wAA////AP///wD///8A////AP///wAAAAAAAAAAAAYAAAANAAAAAAAAF3cAAM//AAD//wAA//8AAP9/AAD/xwAA//8AAP//AAD//wAA//8AAP//AAD//wAA//8AAP//AAD//wAA//gAAP/SAAD/xAAA//AAAP9kAADLAAAAFQAAAAAAAAAAAAAAAAAAAAD///8A////AP///wD///8A////AAD///8A////AP///wD///8A////AAAAAAAAAAAABAAAABUAAAAVAAAAAAAAHHIAAMr/AAD/4AAA/44AAP/rAAD//wAA//8AAP//AAD//wAA//8AAP//AAD//wAA//8AAP//AAD//wAA//8AAP//AAD/gAAAygkAABsJAAAAAAAAAAAAAAAAAAAAAAAAAP///wD///8A////AP///wD///8AAP///wD///8A////AP///wD///8AAAAAAAAAAAAEAAAAFAAAABYAAAATAAAAAAAAHIAAAMLzAAD/mAAA/+oAAP//AAD//wAA//8AAP//AAD//wAA//8AAP//AAD//wAA//8AAP//AAD//wAA/3cAAMYAAAAeHgAAAAkAAAAAAAAAAAAAAAAAAAAAAAAA////AP///wD///8A////AP///wAA////AP///wD///8A////AP///wAAAAAAAAAAAAQAAAAUAAAAFgAAABUAAAAMAAAAAQAAFHMAAMfFAAD/9QAA//8AAP//AAD//wAA//8AAP//AAD//wAA//8AAP//AAD//wAA//8AAP9+AADNAAAAGREAAAAgAAAACQAAAAAAAAAAAAAAAAAAAAAAAAD///8A////AP///wD///8A////AAD///8A////AP///wD///8A////AAAAAAAAAAAABAAAABQAAAAWAAAAFAAAABQAAAANAAAADQAAF0QAAM/oAAD//wAA//8AAP//AAD//wAA//8AAP//AAD//wAA//8AAP//AAD/hwAA2wMAAB0SAAAAGgAAACAAAAAJAAAAAAAAAAAAAAAAAAAAAAAAAP///wD///8A////AP///wD///8AAP///wD///8A////AP///wD///8AAAAAAAAAAAAEAAAAFAAAABYAAAAUAAAAEgAAABUAAAAiAAAAAAAAHV4AAMv/AAD//wAA//8AAP//AAD//wAA//8AAP//AAD//wAA/4cAANsMAAAnHgAAABkAAAAYAAAAIAAAAAkAAAAAAAAAAAAAAAAAAAAAAAAA////AP///wD///8A////AP///wAA////AP///wD///8A////AP///wAAAAAAAAAAAAQAAAAUAAAAFgAAABQAAAASAAAAFQAAACQAAAAKAAAAAAAAHGsAALz2AAD//wAA//8AAP//AAD//wAA//IAAP9tAAC/DAAAJyQAAAAfAAAAGQAAABgAAAAgAAAACQAAAAAAAAAAAAAAAAAAAAAAAAD///8A////AP///wD///8A////AAH///8AAAAAAAAAAAAAAAAAAAAAAAEBAQAAAAAABAAAABAAAAACAAAA/gAAAP4AAAADAAAADwAAAOcAAAD+AAAA9wAABioAAGtgAABeOQAAHPsAAP/BAADepQAAoNwAAJ4jAAD6AwAAAPkAAAD6AAAA/wAAAAgAAADpAAAA9wAAAAAAAAAAAAAAAAAAAP///wAAAAAAAAAAAAAAAAAAAAAAAQAA//8wabirP4J+hgAAAABJRU5ErkJggg=="
print "---"
print "Status:"
print "---"
print "Open the Pi-Hole GUI" + "| color=red href=" + pihole
print "---"
print "Enable Pi-Hole | color=green href=" + pihole + "api.php?enable&auth=" + passwd
print "---"
print "Disable Pi-Hole | color=red href=" + pihole + "api.php?disable&auth=" + passwd
print "---"
print "Domains Being Blocked: | color=navy"
print str(json['domains_being_blocked']) + "| color=black"
print "Unique Domains Today: | color=navy"
print str(json['unique_domains']) + "| color=black"
print "Ads Blocked Today: | color=navy"
print str(json['ads_blocked_today']) + " or", str(json['ads_percentage_today']) + "%| color=black"
print "DNS Queries Today: | color=navy"
print str(json['dns_queries_today']) + "| color=black"
print "Queries Forwarded Today: | color=navy"
print str(json['queries_forwarded']) + "| color=black"
print "Queries Cached Today: | color=navy"
print str(json['queries_cached']) + "| color=black"
print "---"

except Exception as e:
print e
print "❌"
print "---"
print "Pi-Hole not found | color=red"
print "---"

Log file output [if available]

output

Device specifics

Hardware Type: rPi, VPS, etc
OS:

This template was created based on the work of udemy-dl.

"<name" is parsed as a valid domain

In raising this issue, I confirm the following:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

0

---

[BUG] Expected Behaviour:
When browsing the WebUI or retrieving stats directly from FTL, all the results returned should be domain names

[BUG] Actual Behaviour:
Once in a while, <name is returned as a domain name

[BUG] Steps to reproduce:
No idea. I have seen this occur on multiple days, and I definitely don't have IPv6 enabled on any of my devices or routing hardware.

Log file output
From /var/log/pihole.log:

May  1 05:37:38 dnsmasq[26983]: query[A] Helios from 10.0.0.6
May  1 05:37:38 dnsmasq[26983]: /etc/hosts Helios is 10.0.0.6
May  1 05:37:38 dnsmasq[26983]: query[AAAA] Helios from 10.0.0.6
May  1 05:37:38 dnsmasq[26983]: cached Helios is NODATA-IPv6
May  1 05:37:38 dnsmasq[26983]: query[A] <name unprintable> from 10.0.0.6
May  1 05:37:38 dnsmasq[26983]: forwarded <name unprintable> to 123.456.789.112
May  1 05:37:38 dnsmasq[26983]: validation result is SECURE

Device specifics

Hardware Type: Raspberry Pi 3B
OS: DietPi v149

.

.

FTL crashes with segfault (sqlite3_clear_bindings ())

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

1

---

[BUG | ISSUE] Expected Behaviour:

FTL run without constantly crashing

[BUG | ISSUE] Actual Behaviour:

Whenever FTL tries to write to it's db, it segfaults.

[BUG | ISSUE] Steps to reproduce:

• run FTL for any amount of time
• watch FTl.log for crash messages

Log file output [if available]

• tail pihole-FTL.log

[2017-07-12 10:01:00.064] SQL error (21): (null)
[2017-07-12 10:01:00.064] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-07-12 10:01:00.064] ---------------------------->  FTL crashed!  <----------------------------
[2017-07-12 10:01:00.064] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-07-12 10:01:00.064] > Please report a bug at https://github.com/pi-hole/FTL/issues
[2017-07-12 10:01:00.064] > and include in your report already the following details:
[2017-07-12 10:01:00.064] >
[2017-07-12 10:01:00.064] > Received signal: Segmentation fault
[2017-07-12 10:01:00.064]        at address: 0
[2017-07-12 10:01:00.064]         with code: SEGV_MAPERR (Address not mapped to object)
[2017-07-12 10:01:00.064] > Memory usage (structs): 356540
[2017-07-12 10:01:00.064] > Memory usage (dynamic): 8785
[2017-07-12 10:01:00.064] >
[2017-07-12 10:01:00.064] > Thank you for helping us to improve our FTL engine!
[2017-07-12 10:01:00.064] FTL terminated!
[2017-07-12 10:01:00.602] ########## FTL started! ##########
[2017-07-12 10:01:00.602] FTL branch: master
[2017-07-12 10:01:00.602] FTL hash: v2.9.4
[2017-07-12 10:01:00.602] FTL date: 2017-07-08
[2017-07-12 10:01:00.602] FTL user: pihole
[2017-07-12 10:01:00.602] Starting config file parsing
[2017-07-12 10:01:00.602]    SOCKET_LISTENING: only local
[2017-07-12 10:01:00.602]    TIMEFRAME: Rolling 24h
[2017-07-12 10:01:00.602]    QUERY_DISPLAY: Show queries
[2017-07-12 10:01:00.602]    AAAA_QUERY_ANALYSIS: Show AAAA queries
[2017-07-12 10:01:00.602]    MAXDBDAYS: max age for stored queries is 365 days
[2017-07-12 10:01:00.602] Finished config file parsing
[2017-07-12 10:01:00.602] PID of FTL process: 13366
[2017-07-12 10:01:00.724] Gravity list entries: 111167
[2017-07-12 10:01:00.724] Blacklist entries: 9
[2017-07-12 10:01:00.724] Notice: Increasing wildcards struct size from 0 to 1 (100.00 B)
[2017-07-12 10:01:00.724] Wildcard blocking list entries: 1
[2017-07-12 10:01:00.725] Database initialized
[2017-07-12 10:01:00.725] Starting initial log file parsing
[2017-07-12 10:01:00.725] Reading from /run/log/pihole/pihole.log.1 (rw-r--r--)
[2017-07-12 10:01:00.725] Notice: Increasing queries struct size from 0 to 10000 (320.12 KB)
[2017-07-12 10:01:00.725] Notice: Increasing overTime struct size from 0 to 100 (324.12 KB)
[2017-07-12 10:01:00.725] Notice: Increasing forwarded struct size from 0 to 4 (324.22 KB)
[2017-07-12 10:01:00.730] New forward server: 84.200.69.80 resolver1.ihgip.net (0/4)
[2017-07-12 10:01:00.730] Notice: Increasing domains struct size from 0 to 1000 (356.25 KB)
[2017-07-12 10:01:00.731] Notice: Increasing clients struct size from 0 to 10 (356.52 KB)
[2017-07-12 10:01:00.736] New client: 192.168.178.1 fritz.box (0/10)
[2017-07-12 10:01:00.737] Reading from /run/log/pihole/pihole.log (rw-r--r--)
[2017-07-12 10:01:00.741] New forward server: 85.214.20.141 h1768020.stratoserver.net (1/4)
[2017-07-12 10:01:00.745] New forward server: 213.73.91.35 dnscache.berlin.ccc.de (2/4)
[2017-07-12 10:01:00.750] New forward server: 84.200.70.40 resolver2.ihgip.net (3/4)
[2017-07-12 10:01:00.750] Notice: Increasing forwarded struct size from 4 to 8 (356.83 KB)
[2017-07-12 10:01:00.920] Finished initial log file parsing
[2017-07-12 10:01:00.920]  -> Total DNS queries: 2608
[2017-07-12 10:01:00.920]  -> Cached DNS queries: 56
[2017-07-12 10:01:00.920]  -> Blocked DNS queries: 1439
[2017-07-12 10:01:00.920]  -> Unknown DNS queries: 0
[2017-07-12 10:01:00.920]  -> Unique domains: 373
[2017-07-12 10:01:00.921]  -> Unique clients: 1
[2017-07-12 10:01:00.921] Successfully accessed setupVars.conf
[2017-07-12 10:01:00.921] Listening on port 4711 for incoming connections
[2017-07-12 10:02:00.083] SQL error (21): (null)
[2017-07-12 10:02:00.083] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-07-12 10:02:00.083] ---------------------------->  FTL crashed!  <----------------------------
[2017-07-12 10:02:00.083] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

• (gdb) continue
  Continuing. [New Thread 0x7f8a816200 (LWP 13666)] Thread 4 "DB" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f8a816200 (LWP 13666)] 0x00000055647417f0 in sqlite3_clear_bindings ()

• (gdb) backtrace
  #0 0x00000055647417f0 in sqlite3_clear_bindings () #1 0x0000005564729e80 in save_to_DB () #2 0x000000556472a2cc in DB_thread () #3 0x0000007f8bb30ffc in start_thread () from /usr/lib/libpthread.so.0 #4 0x0000007f8baa39ec in thread_start () from /usr/lib/libc.so.6

Device specifics

Hardware Type: Odroid C2
OS: ArchLinuxARM

This template was created based on the work of udemy-dl.

SQL Issue

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

1

---

[BUG | ISSUE] Expected Behaviour:

[BUG | ISSUE] Actual Behaviour:

FTL crashes after reboot. If pihole-FTL.db is deleted, no further crashes appear to happen.

[BUG | ISSUE] Steps to reproduce:

• Reboot device
• Start Admin Console
• "Connection lost to API" appears, FTL has crashed.
• remove pihole-FTL.db from /etc/pihole/pihole-FTL.log
• restart service pihole-FTL (sudo service pihole-FTL restart)
• FTL doesn't crash anymore until reboot.
• Cannot be fixed by "pihole -r"

Log file output [if available]

[2017-07-30 14:22:03.453] Successfully accessed setupVars.conf
[2017-07-30 14:22:03.454] Listening on port 4711 for incoming connections
[2017-07-30 14:23:00.023] SQL error (21): (null)
[2017-07-30 14:23:00.023] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-07-30 14:23:00.023] ----------------------------> FTL crashed! <----------------------------
[2017-07-30 14:23:00.023] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-07-30 14:23:00.023] > Please report a bug at https://github.com/pi-hole/FTL/issues
[2017-07-30 14:23:00.023] > and include in your report already the following details:
[2017-07-30 14:23:00.023] >
[2017-07-30 14:23:00.023] > Received signal: Segmentation fault
[2017-07-30 14:23:00.023] at address: 0
[2017-07-30 14:23:00.023] with code: SEGV_MAPERR (Address not mapped to object)
[2017-07-30 14:23:00.023] > Memory usage (structs): 396668
[2017-07-30 14:23:00.023] > Memory usage (dynamic): 27410
[2017-07-30 14:23:00.023] >
[2017-07-30 14:23:00.023] > Thank you for helping us to improve our FTL engine!
[2017-07-30 14:23:00.023] FTL terminated!

Device specifics

Hardware Type: Odroid C2
OS: Ubuntu 16.04.2 LTS

This template was created based on the work of udemy-dl.

ftl crashes

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

{replace this text with a number from 1 to 10, with 1 being not familiar, and 10 being very familiar}

---

[BUG | ISSUE] Expected Behaviour:

[BUG | ISSUE] Actual Behaviour:

[BUG | ISSUE] Steps to reproduce:

Log file output [if available]

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-05-05 13:41:53.674] ----------------------------> FTL crashed! <----------------------------
[2017-05-05 13:41:53.674] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2017-05-05 13:41:53.674] > Please report a bug at https://github.com/pi-hole/FTL/issues
[2017-05-05 13:41:53.674] > and include in your report already the following details:
[2017-05-05 13:41:53.675] >
[2017-05-05 13:41:53.675] > Received signal: Segmentation fault
[2017-05-05 13:41:53.675] at address: 139928088481800
[2017-05-05 13:41:53.675] with code: SEGV_ACCERR (Invalid permissions for mapped object)
[2017-05-05 13:41:53.675] > Memory usage (structs): 356420
[2017-05-05 13:41:53.675] > Memory usage (dynamic): 9244
[2017-05-05 13:41:53.675] >
[2017-05-05 13:41:53.675] > Thank you for helping us to improve our FTL engine!
[2017-05-05 13:41:53.676] FTL terminated!

Device specifics

Hardware Type: rPi, VPS, etc
OS:

vmware fusion, debian,

This template was created based on the work of udemy-dl.

lost connection to API occurring randomly

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

{5}

---

[BUG | ISSUE] Expected Behaviour:
pihole FTL log be openable and status returned correctly

[BUG | ISSUE] Actual Behaviour:

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

[BUG | ISSUE] Steps to reproduce:

-latest Developement branch
-run pihole-FTL status

Log file output [if available]

2017-11-03 00:00:03.255] NOTICE: pihole.log has been flushed
[2017-11-03 00:00:03.256]   Resetting internal data structure
[2017-11-03 00:00:03.256]   Queries in memory before flushing: 17694
[2017-11-03 00:00:06.894] Gravity list entries: 1210427
[2017-11-03 00:00:06.895] Blacklist entries: 2
[2017-11-03 00:00:06.895] No wildcard blocking list present
[2017-11-03 00:00:06.895] Reading from /var/log/pihole.log.1 (rw-r--r--)
[2017-11-03 00:00:06.895] Notice: Increasing queries struct size from 0 to 10000 (320.45 KB)
[2017-11-03 00:00:06.895] Notice: Increasing overTime struct size from 0 to 100 (323.65 KB)
[2017-11-03 00:00:06.895] Notice: Increasing forwarded struct size from 0 to 4 (323.72 KB)
[2017-11-03 00:00:06.897] New forward server: 208.67.220.220 resolver2.opendns.com (0/4)
[2017-11-03 00:00:06.897] Notice: Increasing domains struct size from 0 to 1000 (343.76 KB)
[2017-11-03 00:00:06.897] Notice: Increasing clients struct size from 0 to 10 (343.95 KB)
[2017-11-03 00:00:06.897] New client: 172.16.1.100 Sean-Laptop (0/10)
[2017-11-03 00:00:06.898] New forward server: 208.67.222.222 resolver1.opendns.com (1/4)
[2017-11-03 00:00:06.899] New client: 127.0.0.1 localhost (1/10)
[2017-11-03 00:00:06.904] New client: 172.16.1.101 Sean-MBP (2/10)
[2017-11-03 00:00:06.914] New client: 172.16.1.105 Sean-Phone (3/10)
[2017-11-03 00:00:07.141] Notice: Increasing overTime struct size from 100 to 200 (351.59 KB)
[2017-11-03 00:00:07.253] Reading from /var/log/pihole.log (rw-r--r--)
[2017-11-03 09:16:18.638] Notice: Increasing overTime struct size from 200 to 300 (356.80 KB)
[2017-11-03 12:26:47.498] dnsmasq process restarted

-rw-r--r--  1 pihole      pihole     1647 Nov  3 12:26 pihole-FTL.log
-rw-r--r--  1 pihole      pihole     1745 Nov  3 00:00 pihole-FTL.log.1

Device specifics

Hardware Type: rPi, VPS, etc
OS:

This template was created based on the work of udemy-dl.

Memory Leak in insetupVarsArray/setupVars.c

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

1

---

[BUG] Expected Behaviour:
All allocated memory should be freed.

[BUG] Actual Behaviour:
In setupVars.c:156, if the condition is false (ie ststr == NULL), the allocated domain will not be freed before the return and the pointer will be lost.

[BUG] Steps to reproduce:
Essentially, if insetupVarsArray is called with these values (for my own ease, I really just copied the function to my main.c):

int setupVarsElements = 1;
char * setupVarsArray[] = {"*test.com\0"};

int main(int argc, char* argv[])
{	
    insetupVarsArray("");
}

Log file output

==2670== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==2670== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info
==2670== Command: ./test
==2670== 
==2670== 
==2670== HEAP SUMMARY:
==2670==     in use at exit: 9 bytes in 1 blocks
==2670==   total heap usage: 1 allocs, 0 frees, 9 bytes allocated
==2670== 
==2670== LEAK SUMMARY:
==2670==    definitely lost: 9 bytes in 1 blocks
==2670==    indirectly lost: 0 bytes in 0 blocks
==2670==      possibly lost: 0 bytes in 0 blocks
==2670==    still reachable: 0 bytes in 0 blocks
==2670==         suppressed: 0 bytes in 0 blocks
==2670== Rerun with --leak-check=full to see details of leaked memory
==2670== 
==2670== For counts of detected and suppressed errors, rerun with: -v
==2670== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

Device specifics

Hardware Type: rPi, VPS, etc
OS: Ubuntu 17.04, gcc 6.3. There are several other memory leaks also reported by scan-build. The steps to reproduce them are rather complicated, so I might leave that up to someone more familiar with the code base. I could zip up the results, if needed

This template was created based on the work of udemy-dl.

Query Log no longer works on upgrade to FTE 2.9.4

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:
1

[BUG | ISSUE] Expected Behaviour:
PiHole main admin page and Query Log Page show queries

[BUG | ISSUE] Actual Behaviour:
Upgrading to LTE 2.9.4 breaks both. Pihole is working, but Query log is not displaying any queries. I have attempted pihole -r but that has not resolved it.

[BUG | ISSUE] Steps to reproduce:

• Upgrade to 2.9.4

Log file output [if available]

In the log, this happens repeatedly:

[2017-06-23 10:40:03.205] FATAL: FTL received SIGTERM from PID/UID 1/0, scheduled to exit gracefully
[2017-06-23 10:40:09.988] ########## FTL started! ##########
[2017-06-23 10:40:10.021] FTL branch: (no branch)
[2017-06-23 10:40:10.021] FTL hash: v2.9.4
[2017-06-23 10:40:10.021] FTL date: 2017-06-22 23:33:48 +0200
[2017-06-23 10:40:10.021] FTL user: pihole
[2017-06-23 10:40:10.021] Notice: Found no readable FTL config file
[2017-06-23 10:40:10.021] Using default settings
[2017-06-23 10:40:10.021] Starting config file parsing
[2017-06-23 10:40:10.022] SOCKET_LISTENING: only local
[2017-06-23 10:40:10.022] TIMEFRAME: Rolling 24h
[2017-06-23 10:40:10.022] QUERY_DISPLAY: Show queries
[2017-06-23 10:40:10.022] AAAA_QUERY_ANALYSIS: Show AAAA queries
[2017-06-23 10:40:10.022] MAXDBDAYS: max age for stored queries is 365 days
[2017-06-23 10:40:10.022] Finished config file parsing
[2017-06-23 10:40:10.028] Found no other running pihole-FTL process

Device specifics

Hardware Type: Linux raspberrypi 4.9.28-v7+ #998 SMP Mon May 15 16:55:39 BST 2017 armv7l GNU/Linux

This template was created based on the work of udemy-dl.

Restart FTL

There should be away to restart it via web ui like you can whit DNS, FTL is always offline after like 12h for me.

Crash when accessing web interface on Pine64 / dietpi

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

0

---

[BUG | ISSUE] Expected Behaviour:
Stable running pihole

[BUG | ISSUE] Actual Behaviour:
pihole runs fine with FTL, crashes when visiting web interface

[BUG | ISSUE] Steps to reproduce:

• Installed latest updates dietpi
• Updated pihole (coming from 2.5.2)
• Visit web interface / admin page
• FTL Crashes

Log file output [if available]

Starting program: /usr/bin/pihole-FTL debug
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
[2017-05-05 15:36:06.616] ########## FTL started! ##########
[2017-05-05 15:36:06.616] FTL branch: (no branch)
[2017-05-05 15:36:06.616] FTL hash: v2.6.1
[2017-05-05 15:36:06.616] FTL date: 2017-05-05 11:17:04 +0200
[2017-05-05 15:36:06.616] FTL user: root
[2017-05-05 15:36:06.616] Notice: Found no readable FTL config file
[2017-05-05 15:36:06.616]         Using default settings
[2017-05-05 15:36:06.616] Starting config file parsing
[2017-05-05 15:36:06.617]    SOCKET_LISTENING: only local
[2017-05-05 15:36:06.617]    TIMEFRAME: Rolling 24h
[2017-05-05 15:36:06.617]    QUERY_DISPLAY: Show queries
[2017-05-05 15:36:06.617] Finished config file parsing
[2017-05-05 15:36:06.617] PID of FTL process: 20017
[2017-05-05 15:36:06.787] Gravity list entries: 105011
[2017-05-05 15:36:06.787] Blacklist entries: 10
[2017-05-05 15:36:06.787] No wildcard blocking list present
[2017-05-05 15:36:06.787] Starting initial log file parsing
[2017-05-05 15:36:06.787] Warning: Reading of rotated log file /var/log/pihole.log.1 failed
[2017-05-05 15:36:06.788] Reading from /var/log/pihole.log (rwxrwxr-x)
[2017-05-05 15:36:06.788] Notice: Increasing queries struct size from 0 to 10000 (320.08 KB)
[2017-05-05 15:36:06.788]         at query time: May  5 13:52:21
[2017-05-05 15:36:06.788] Notice: Increasing overTime struct size from 0 to 100 (324.08 KB)
[2017-05-05 15:36:06.788]         at query time: May  5 13:52:21
[2017-05-05 15:36:06.788] Notice: Increasing forwarded struct size from 0 to 4 (324.19 KB)
[2017-05-05 15:36:06.788]         at query time: May  5 13:52:21
[2017-05-05 15:36:06.824] New forward server: 208.67.220.220 resolver2.opendns.com (0/4)
[2017-05-05 15:36:06.825] Notice: Increasing domains struct size from 0 to 1000 (356.23 KB)
[2017-05-05 15:36:06.825]         at query time: May  5 13:52:21
[2017-05-05 15:36:06.825] New domain: 0.debian.pool.ntp.org (0/1000)
[2017-05-05 15:36:06.825] Notice: Increasing clients struct size from 0 to 10 (356.49 KB)
[2017-05-05 15:36:06.825]         at query time: May  5 13:52:21
[2017-05-05 15:36:06.825] New client: 127.0.0.1 localhost (0/10)
[2017-05-05 15:36:06.833] New forward server: 208.67.222.222 resolver1.opendns.com (1/4)
[2017-05-05 15:36:06.834] New domain: 1.debian.pool.ntp.org (1/1000)
<snip>
[2017-05-05 15:36:06.848] New domain: ftp.debian.org (35/1000)
[2017-05-05 15:36:06.848] Finished initial log file parsing
[2017-05-05 15:36:06.848]  -> Total DNS queries: 124
[2017-05-05 15:36:06.848]  -> Cached DNS queries: 40
[2017-05-05 15:36:06.849]  -> Blocked DNS queries: 0
[2017-05-05 15:36:06.849]  -> Unknown DNS queries: 0
[2017-05-05 15:36:06.849]  -> Unique domains: 36
[2017-05-05 15:36:06.849]  -> Unique clients: 2
[2017-05-05 15:36:06.849] Successfully accessed setupVars.conf
[New Thread 0x7fb7d3e1f0 (LWP 20020)]
[2017-05-05 15:36:06.865] Listening on port 4711
[New Thread 0x7fb753e1f0 (LWP 20021)]
[New Thread 0x7fb6d3e1f0 (LWP 20264)]
[Thread 0x7fb6d3e1f0 (LWP 20264) exited]
[New Thread 0x7fb6d3e1f0 (LWP 20267)]
[Thread 0x7fb6d3e1f0 (LWP 20267) exited]
[New Thread 0x7fb6d3e1f0 (LWP 20270)]
[Thread 0x7fb6d3e1f0 (LWP 20270) exited]
[New Thread 0x7fb6d3e1f0 (LWP 20273)]
[Thread 0x7fb6d3e1f0 (LWP 20273) exited]
[New Thread 0x7fb6d3e1f0 (LWP 20276)]
[Thread 0x7fb6d3e1f0 (LWP 20276) exited]
[New Thread 0x7fb6d3e1f0 (LWP 20279)]
*** Error in `/usr/bin/pihole-FTL': double free or corruption (out): 0x0000007fa8000b40 ***

Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7fb6d3e1f0 (LWP 20279)]
0x0000007fb7e8e9e8 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
56      ../nptl/sysdeps/unix/sysv/linux/raise.c: Bestand of map bestaat niet.
(gdb) backtrace
#0  0x0000007fb7e8e9e8 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x0000007fb7e8fcf0 in __GI_abort () at abort.c:89
#2  0x0000007fb7eca6bc in __libc_message (do_abort=1, 
    fmt=fmt@entry=0x7fb7f780b8 "*** Error in `%s': %s: 0x%s ***\n")
    at ../sysdeps/posix/libc_fatal.c:175
#3  0x0000007fb7ed02e0 in malloc_printerr (action=1, 
    str=0x7fb7f78248 "double free or corruption (out)", ptr=<optimized out>) at malloc.c:4996
#4  0x0000007fb7ed10b0 in _int_free (av=0x7fb7fa2558 <main_arena>, p=<optimized out>, have_lock=0)
    at malloc.c:3840
#5  0x00000055752d7c04 in clearSetupVarsArray () at setupVars.c:116
#6  0x00000055752d546c in getTopDomains (
    client_message=client_message@entry=0x7fa80008c0 ">top-domains", sock=sock@entry=0x7fb6d3d5c0)
    at request.c:317
#7  0x00000055752d71bc in process_request (
    client_message=client_message@entry=0x7fa80008c0 ">top-domains", sock=sock@entry=0x7fb6d3d5c0)
    at request.c:54
#8  0x00000055752d4870 in connection_handler_thread (socket_desc=0x7fb00008c0) at socket.c:213
#9  0x0000007fb7fafe34 in start_thread (arg=0x7fb6d3e1f0) at pthread_create.c:311
#10 0x0000007fb7f264f0 in clone () at ../ports/sysdeps/unix/sysv/linux/aarch64/nptl/../clone.S:96
(gdb) 

Device specifics

Hardware Type: Pine64
OS: dietpi

This template was created based on the work of udemy-dl.

Change of file system in /var/log

In general, once the handle to /var/log/pihole.log is open, the file is open, and nobody changing the directory structure can change that - the file can be moved, renamed, or put something else in its place - it remains open by construction, as in Linux/Unix there is no real delete for files, but only unlink, which doesn't necessarily delete the file - it just removes the link from the directory.

However, if the underlying device disappears (e.g. /var/log is a ramdisk) then the file handle won't be valid an more and is likely to lead to unpredictable behavior. This is a potential issue for FTL.

Note: Even if the file handle becomes invalid, it can still be used (but will likely give I/O errors) and has also still to be closed!

FTL Crashing after update any time admin console is accessed

Ever since updating this morning, every time I try to access the admin console FTL crashes.

I've tried different browsers. (FF, Chrome and IE) I've rebooted the server, even reverting to the previous kernel to remove the possibility of the Meltdown patch causing problems.

In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:

• I have read and understood the contributors guide.
• The issue I am reporting can be replicated
• The issue I am reporting isn't a duplicate

How familiar are you with the codebase?:

2

[ISSUE] FTL crashes when Admin console is accessed.

Clients, Query Types, and Forward Destinations fields never load, have spinning circle arrows.

New behavior after update.

Pi-hole Version v3.2.1 Web Interface Version v3.2.1 FTL Version vDev (master , vDev-1de2b99)

Error from log:

[2018-01-12 13:12:44.360] Finished initial log file parsing
[2018-01-12 13:12:44.360] -> Total DNS queries: 547248
[2018-01-12 13:12:44.360] -> Cached DNS queries: 356341
[2018-01-12 13:12:44.360] -> Blocked DNS queries: 89694
[2018-01-12 13:12:44.360] -> Unknown DNS queries: 0
[2018-01-12 13:12:44.360] -> Unique domains: 16977
[2018-01-12 13:12:44.360] -> Unique clients: 650
[2018-01-12 13:12:44.360] Successfully accessed setupVars.conf
[2018-01-12 13:12:44.361] Listening on port 4711 for incoming connections
[2018-01-12 13:12:51.667] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2018-01-12 13:12:51.667] ----------------------------> FTL crashed! <----------------------------
[2018-01-12 13:12:51.667] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2018-01-12 13:12:51.667] Please report a bug at https://github.com/pi-hole/FTL/issues
[2018-01-12 13:12:51.667] and include in your report already the following details:

[2018-01-12 13:12:51.667] FTL has been running for 19 seconds
[2018-01-12 13:12:51.667] FTL branch: v2.13.2
[2018-01-12 13:12:51.667] FTL version: v2.13.2
[2018-01-12 13:12:51.667] FTL commit: 1de2b99
[2018-01-12 13:12:51.667] FTL date: 2018-01-07 17:34:24 -0800
[2018-01-12 13:12:51.667] FTL user: pihole
[2018-01-12 13:12:51.668]
Received signal: Segmentation fault
[2018-01-12 13:12:51.668] at address: 0
[2018-01-12 13:12:51.668] with code: Unknown (128),
[2018-01-12 13:12:51.668] Memory usage (structs): 18165668
[2018-01-12 13:12:51.668] Memory usage (dynamic): 428048

[2018-01-12 13:12:51.668] Thank you for helping us to improve our FTL engine!
[2018-01-12 13:12:51.668] FTL terminated!

Debug output:

[2018-01-12 12:54:50.886] New domain: officedepot.scene7.com (2 - 15956/16000)
[2018-01-12 12:54:50.887] New domain: www18.officedepot.com (1 - 15957/16000)
[2018-01-12 12:54:51.089] New domain: e9954.c.akamaiedge.net (3 - 15958/16000)
[2018-01-12 12:54:51.090] New domain: e11287.cd.akamaiedge.net (3 - 15959/16000)
[New Thread 0x7ffff4af3700 (LWP 9574)]
[Thread 0x7ffff4af3700 (LWP 9574) exited]
[New Thread 0x7ffff4af3700 (LWP 9577)]
[Thread 0x7ffff4af3700 (LWP 9577) exited]
[New Thread 0x7ffff4af3700 (LWP 9580)]
[Thread 0x7ffff4af3700 (LWP 9580) exited]
[New Thread 0x7ffff4af3700 (LWP 9583)]
[Thread 0x7ffff4af3700 (LWP 9583) exited]
[2018-01-12 12:54:55.730] New domain: thebusyspatula.files.wordpress.com (2 - 15960/16000)
[2018-01-12 12:54:55.730] New domain: www.getcoloringpages.com (2 - 15961/16000)
[New Thread 0x7ffff4af3700 (LWP 9586)]
[Thread 0x7ffff4af3700 (LWP 9586) exited]
[New Thread 0x7ffff4af3700 (LWP 9589)]
[Thread 0x7ffff4af3700 (LWP 9589) exited]
[New Thread 0x7ffff4af3700 (LWP 9592)]
[Thread 0x7ffff4af3700 (LWP 9592) exited]
[2018-01-12 12:54:58.759] New domain: www.calendarlabs.com (2 - 15962/16000)
[2018-01-12 12:54:58.961] New domain: calendarlabs.com (3 - 15963/16000)
[New Thread 0x7ffff4af3700 (LWP 9595)]
[Thread 0x7ffff4af3700 (LWP 9595) exited]
[New Thread 0x7ffff4af3700 (LWP 9596)]
[2018-01-12 12:55:00.075] Notice: Queries stored in DB: 0
[Thread 0x7ffff4af3700 (LWP 9596) exited]
[New Thread 0x7ffff4af3700 (LWP 9599)]
[Thread 0x7ffff4af3700 (LWP 9599) exited]
[2018-01-12 12:55:01.584] New domain: wcgpjprk.us.bnsflogistics.com (2 - 15964/16000)
[2018-01-12 12:55:01.584] New domain: qatzvefsnjl.us.bnsflogistics.com (2 - 15965/16000)
[2018-01-12 12:55:01.585] New domain: crsmmmxp.us.bnsflogistics.com (2 - 15966/16000)
[2018-01-12 12:55:01.786] New domain: 5cg5450lx4.us.bnsflogistics.com (2 - 15967/16000)
[2018-01-12 12:55:03.399] New domain: eqv-171.eqv-rtb1.rfihub.com (2 - 15968/16000)
[2018-01-12 12:55:03.806] New domain: www.myratelinx.com (2 - 15969/16000)
[2018-01-12 12:55:04.813] New domain: ewuwdnrgjblropj.us.bnsflogistics.com (2 - 15970/16000)
[2018-01-12 12:55:04.814] New domain: bsohrakhfwbint.us.bnsflogistics.com (2 - 15971/16000)
[2018-01-12 12:55:04.814] New domain: fqpcdglakhfscxa.us.bnsflogistics.com (2 - 15972/16000)
[2018-01-12 12:55:04.815] New domain: fqpcdglakhfscxa.bnsflogistics.com (2 - 15973/16000)
[2018-01-12 12:55:04.816] New domain: ewuwdnrgjblropj.bnsflogistics.com (2 - 15974/16000)
[2018-01-12 12:55:05.017] New domain: bsohrakhfwbint.bnsflogistics.com (2 - 15975/16000)
[2018-01-12 12:55:05.018] New domain: trustlist.adobe.com (2 - 15976/16000)
[New Thread 0x7ffff4af3700 (LWP 9622)]
[Thread 0x7ffff4af3700 (LWP 9622) exited]
[New Thread 0x7ffff4af3700 (LWP 9625)]
[Thread 0x7ffff4af3700 (LWP 9625) exited]
[New Thread 0x7ffff4af3700 (LWP 9628)]
*** stack smashing detected ***: /usr/bin/pihole-FTL terminated

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff4af3700 (LWP 9628)]
0x00007ffff40ec688 in ?? () from /lib/x86_64-linux-gnu/libgcc_s.so.1

Backtrace:
#0 0x00007ffff40ec688 in ?? () from /lib/x86_64-linux-gnu/libgcc_s.so.1
#1 0x00007ffff40ed6f8 in _Unwind_Backtrace () from /lib/x86_64-linux-gnu/libgcc_s.so.1
#2 0x00007ffff7909526 in __GI___backtrace (array=, size=64) at ../sysdeps/x86_64/backtrace.c:109
#3 0x00007ffff7833d62 in backtrace_and_maps (do_abort=0, do_abort@entry=2, written=false, fd=6) at ../sysdeps/unix/sysv/linux/libc_fatal.c:47
#4 0x00007ffff78871af in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7ffff7979cb3 "*** %s ***: %s terminated\n")
at ../sysdeps/posix/libc_fatal.c:172
#5 0x00007ffff790caa7 in __GI___fortify_fail (msg=msg@entry=0x7ffff7979c9b "stack smashing detected") at fortify_fail.c:31
#6 0x00007ffff790ca70 in __stack_chk_fail () at stack_chk_fail.c:28
#7 0x000055555556c542 in getClientsOverTime (sock=0x7ffff4af2af0) at request.c:1155
#8 0x2031362038342035 in ?? ()
#9 0x3436203420323831 in ?? ()
#10 0x2034203131203220 in ?? ()
#11 0x3920313120322039 in ?? ()
#12 0x3536312038203520 in ?? ()
#13 0x3020302036203220 in ?? ()
#14 0x2030203631203420 in ?? ()
#15 0x2033312032312037 in ?? ()
#16 0x3520302032312036 in ?? ()
#17 0x3120323120393120 in ?? ()
#18 0x3731203533203820 in ?? ()
#19 0x3120392033203220 in ?? ()
#20 0x3320362033203020 in ?? ()
#21 0x3120372033203420 in ?? ()
#22 0x3120342036203220 in ?? ()
#23 0x2033203320312035 in ?? ()
#24 0x3120342035312035 in ?? ()
#25 0x2034312032312037 in ?? ()
#26 0x3120392034203631 in ?? ()
#27 0x3632203120302032 in ?? ()
#28 0x2030203020383320 in ?? ()
#29 0x2032203220343731 in ?? ()
#30 0x3320323120302032 in ?? ()
#31 0x3820313220303220 in ?? ()
#32 0x2032312036203520 in ?? ()
#33 0x3935203933312037 in ?? ()
#34 0x3320322030203020 in ?? ()
#35 0x2036203732203020 in ?? ()
#36 0x3120382034322030 in ?? ()
#37 0x2032203120342033 in ?? ()
#38 0x3833203020342030 in ?? ()
#39 0x2034203120303520 in ?? ()
#40 0x3220393120362032 in ?? ()
#41 0x3320342030203920 in ?? ()
#42 0x3220352030203020 in ?? ()
#43 0x2030203320352036 in ?? ()
#44 0x3020302031322033 in ?? ()
#45 0x2030203020393120 in ?? ()
#46 0x3020302035312035 in ?? ()
#47 0x3120322030373120 in ?? ()
#48 0x3020302030203120 in ?? ()
#49 0x3020302037203520 in ?? ()
#50 0x3720302036203020 in ?? ()
#51 0x2030203632203020 in ?? ()
#52 0x2032203020312032 in ?? ()
#53 0x3920302038312030 in ?? ()
#54 0x2037332030203320 in ?? ()
#55 0x3733203220372031 in ?? ()
#56 0x3020302030203020 in ?? ()
#57 0x3633203020383220 in ?? ()
#58 0x3220313831203020 in ?? ()
#59 0x2034342030203020 in ?? ()
#60 0x3020302030203232 in ?? ()
#61 0x3720332038203020 in ?? ()
#62 0x3020372034203020 in ?? ()
#63 0x2034312030203020 in ?? ()
#64 0x3431203020302038 in ?? ()
#65 0x3020302030203020 in ?? ()
#66 0x3020302030203020 in ?? ()
#67 0x3020302030203020 in ?? ()
#68 0x3020302030203020 in ?? ()
#69 0x3020302030203020 in ?? ()
#70 0x2030203020383220 in ?? ()
#71 0x2030203020302030 in ?? ()
#72 0x2030203020302030 in ?? ()
#73 0x372030000a322033 in ?? ()
#74 0x2031203020302030 in ?? ()
#75 0x3732203020392030 in ?? ()
#76 0x3020302037203020 in ?? ()
#77 0x2036312031303120 in ?? ()
#78 0x2033342036203033 in ?? ()
#79 0x2030203020302030 in ?? ()
#80 0x2034332030203532 in ?? ()
#81 0x3020302035352030 in ?? ()
#82 0x3331203233203020 in ?? ()
#83 0x3020302030203020 in ?? ()
#84 0x2031322030203320 in ?? ()
#85 0x2030312031312034 in ?? ()
#86 0x3620383120302030 in ?? ()
#87 0x3920302030203820 in ?? ()
#88 0x3020302030203020 in ?? ()
#89 0x3020302030203020 in ?? ()
#90 0x3020302030203020 in ?? ()
#91 0x3020302030203020 in ?? ()
#92 0x3020302030203020 in ?? ()
#93 0x2030203020383320 in ?? ()
#94 0x2030203020302030 in ?? ()
#95 0x3120392033352030 in ?? ()
#96 0x000a302034363320 in ?? ()
#97 0x3020302030203320 in ?? ()
#98 0x3020302030203020 in ?? ()
#99 0x203020302030000a in ?? ()
#100 0x0a30203020302030 in ?? ()
#101 0xffffffffffffff00 in ?? ()
#102 0x0000000000000000 in ?? ()

/var/run/pihole-FTL.port
4711

/var/run/pihole-FTL.pid
9521

Device specifics

Hardware Type: VMWare virtual machine
OS: Debian Jessie 64bit