# Updated to 4.1.1 and now DNS service won't start

**URL:** <https://discourse.pi-hole.net/t/updated-to-4-1-1-and-now-dns-service-wont-start/15329>\
**Category:** Help\
**Tags:** v4-1-1\
**Created:** [December 21, 2018, 7:57pm UTC](https://discourse.pi-hole.net/t/updated-to-4-1-1-and-now-dns-service-wont-start/15329 "2018-12-21T19:57:58Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![badtimebreak](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/badtimebreak/32/5865_2.png) [@badtimebreak](https://discourse.pi-hole.net/u/badtimebreak)\
**Post date:** [December 21, 2018, 7:57pm UTC](https://discourse.pi-hole.net/t/updated-to-4-1-1-and-now-dns-service-wont-start/15329/1 "2018-12-21T19:57:58Z")

</div>

#### Please follow the below template, it will help us to help you!

## Expected Behaviour:

Updated via `pihole -up`, pihole should still be operating normally

## Actual Behaviour:

Updater seemed to work fine, but when checking `pihole status` the DNS service isn't running. tried `pihole restartdns` which says it works, but `status` says otherwise. Rebooted the raspberry pi, didn't help. Tried `pihole -up` again, it said there was an FTL update avaliable, but got "Error: Unable to get latest release location from GitHub  
[✗] FTL Engine not installed". Found [this](https://discourse.pi-hole.net/t/ftl-engine-not-installed/9004) post, followed it; the FTL error went away, but DNS service still wont start after multiple -r and reboots.

## Debug Token:

1egtk9t70t  
This one is from before some of the last few -r and reboots, but when I tried to upload a new one, got `There was an error uploading your debug log.`

---

<div class="post-metadata">

**Author:** ![jfb](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jfb/32/4332_2.png) [@jfb](https://discourse.pi-hole.net/u/jfb)\
**Post date:** [December 21, 2018, 8:07pm UTC](https://discourse.pi-hole.net/t/updated-to-4-1-1-and-now-dns-service-wont-start/15329/2 "2018-12-21T20:07:00Z")

</div>

Your debug log shows that you are on 4.1.1 on all modules, but pihole-FTL is not running.

```
*** [DIAGNOSING]: Core version
[i] Core: v4.1.1 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v4.1.1-0-g8d85d46

*** [DIAGNOSING]: Web version
[i] Web: v4.1.1 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v4.1.1-0-gde7aa5a3

*** [DIAGNOSING]: FTL version
[✓] FTL: v4.1.1

```

After you reset your nameserver to something other than 127.0.0.1, Pi-Hole resets it after each repair or update. Since FTL is not running, you have to reset it each time until fixed.

This error appears at the tail of your pihole-FTL log:

```
   [2018-12-21 13:21:02.687] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
   [2018-12-21 13:21:02.687] ----------------------------> FTL crashed! <----------------------------
   [2018-12-21 13:21:02.687] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
   [2018-12-21 13:21:02.687] Please report a bug at https://github.com/pi-hole/FTL/issues
   [2018-12-21 13:21:02.687] and include in your report already the following details:
   
   [2018-12-21 13:21:02.687] FTL has been running for 12 seconds
   [2018-12-21 13:21:02.687] FTL branch: master
   [2018-12-21 13:21:02.687] FTL version: v4.1.1
   [2018-12-21 13:21:02.687] FTL commit: f5f331b
   [2018-12-21 13:21:02.687] FTL date: 2018-12-21 10:32:10 -0600
   [2018-12-21 13:21:02.687] FTL user: pihole
   [2018-12-21 13:21:02.687] Received signal: Segmentation fault
   [2018-12-21 13:21:02.687] at address: 0
   [2018-12-21 13:21:02.687] with code: SEGV_MAPERR (Address not mapped to object)
   [2018-12-21 13:21:02.688] Backtrace:
   [2018-12-21 13:21:02.688] B[0000]: /usr/bin/pihole-FTL(+0x1a09a) [0x50809a]
   [2018-12-21 13:21:02.688] B[0001]: /lib/arm-linux-gnueabihf/libc.so.6(__default_rt_sa_restorer+0) [0x76d9e6c0]
   [2018-12-21 13:21:02.688] Thank you for helping us to improve our FTL engine!
   [2018-12-21 13:21:02.688] FTL terminated!

```

Several other users have reported this problem as well and the devs are looking into it.

---

<div class="post-metadata">

**Author:** ![jacob.salmela](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jacob.salmela/32/8_2.png) [@jacob.salmela](https://discourse.pi-hole.net/u/jacob.salmela)\
**Post date:** [December 21, 2018, 8:24pm UTC](https://discourse.pi-hole.net/t/updated-to-4-1-1-and-now-dns-service-wont-start/15329/5 "2018-12-21T20:24:02Z")

</div>

We're looking into the issue. You can track progress here:

> <https://github.com/pi-hole/FTL/issues/444>
>
> \*\*In raising this issue, I confirm the following (please check boxes, eg \[X\]) Fa…ilure to fill the template will close your issue:\*\*
> 
> \- \[X\] I have read and understood the \[contributors guide\](https://github.com/pi-hole/pi-hole/blob/master/CONTRIBUTING.md).
> \- \[X\] The issue I am reporting can be \*replicated\*
> \- \[X\] The issue I am reporting isn't a duplicate 
> 
> \*\*How familiar are you with the codebase?:\*\*
> 1
> 
> \---
> 
> \*\*\[ISSUE\] Expected Behaviour:\*\*
> FTL to not crash.
> 
> \*\*\[ISSUE\] Actual Behaviour:\*\*
> FTL crashing after ~15 seconds.
> 
> \*\*\[ISSUE\] Steps to reproduce:\*\*
> Start/restart pihole-FTL service or reboot Pi.
> 
> \*\*Log file output \[if available\]\*\*
> 
> \`\`\`
> \[2018-12-21 13:32:00.478\] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> \[2018-12-21 13:32:00.478\] ----------------------------\> FTL crashed! \<----------------------------
> \[2018-12-21 13:32:00.478\] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> \[2018-12-21 13:32:00.478\] Please report a bug at https://github.com/pi-hole/FTL/issues
> \[2018-12-21 13:32:00.478\] and include in your report already the following details:
> 
> \[2018-12-21 13:32:00.478\] FTL has been running for 16 seconds
> \[2018-12-21 13:32:00.478\] FTL branch: master
> \[2018-12-21 13:32:00.478\] FTL version: v4.1.1
> \[2018-12-21 13:32:00.478\] FTL commit: f5f331b
> \[2018-12-21 13:32:00.478\] FTL date: 2018-12-21 10:32:10 -0600
> \[2018-12-21 13:32:00.479\] FTL user: pihole
> \[2018-12-21 13:32:00.479\] Received signal: Segmentation fault
> \[2018-12-21 13:32:00.479\] at address: 0
> \[2018-12-21 13:32:00.479\] with code: SEGV\_MAPERR (Address not mapped to object)
> \[2018-12-21 13:32:00.479\] Backtrace:
> \[2018-12-21 13:32:00.479\] B\[0000\]: /usr/bin/pihole-FTL(+0x1a09a) \[0x45109a\]
> \[2018-12-21 13:32:00.479\] B\[0001\]: /lib/arm-linux-gnueabihf/libc.so.6(\_\_default\_rt\_sa\_restorer+0) \[0x76d606c0\]
> \[2018-12-21 13:32:00.480\] Thank you for helping us to improve our FTL engine!
> \[2018-12-21 13:32:00.480\] FTL terminated!
> \`\`\`
> 
> \*\*Device specifics\*\*
> 
> Hardware Type: rPi
> OS: Raspbian GNU/Linux 9 (stretch)
> 
> 
> Just updated from 4.1 to 4.1.1 and now FTL won't stay running. I've tried repairing with and without sudo to no avail, including replacing the \`127.0.0.1\` nameserver in the \`/etc/resolv.conf\` file.

---

<div class="post-metadata">

**Author:** ![jacob.salmela](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jacob.salmela/32/8_2.png) [@jacob.salmela](https://discourse.pi-hole.net/u/jacob.salmela)\
**Post date:** [December 21, 2018, 8:34pm UTC](https://discourse.pi-hole.net/t/updated-to-4-1-1-and-now-dns-service-wont-start/15329/6 "2018-12-21T20:34:51Z")

</div>

> <https://github.com/pi-hole/FTL/pull/445>
>
> Fixes #444

---

<div class="post-metadata">

**Author:** ![jacob.salmela](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jacob.salmela/32/8_2.png) [@jacob.salmela](https://discourse.pi-hole.net/u/jacob.salmela)\
**Post date:** [December 21, 2018, 9:16pm UTC](https://discourse.pi-hole.net/t/updated-to-4-1-1-and-now-dns-service-wont-start/15329/7 "2018-12-21T21:16:36Z")

</div>

@badtimebreak please update to v4.1.2 of FTL and let me know if it resolves your issue. If the update fails, then edit `/etc/resolv.conf` and change `nameserver 127.0.0.1` to `nameserver 1.1.1.1` (or third party DNS server of your choice), save and exit, then run `pihole -up`.

---

<div class="post-metadata">

**Author:** ![badtimebreak](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/badtimebreak/32/5865_2.png) [@badtimebreak](https://discourse.pi-hole.net/u/badtimebreak)\
**Post date:** [December 21, 2018, 9:23pm UTC](https://discourse.pi-hole.net/t/updated-to-4-1-1-and-now-dns-service-wont-start/15329/8 "2018-12-21T21:23:44Z")

</div>

Looks like that resolved it. Thanks for the quick fix!

---

<div class="post-metadata">

**Author:** ![system](https://discourse.pi-hole.net/uploads/default/original/3X/7/c/7c8792f649eeb921c5d2b4c41564ffa873d9a2b8.png) [@system](https://discourse.pi-hole.net/u/system)\
**Post date:** [January 11, 2019, 9:34pm UTC](https://discourse.pi-hole.net/t/updated-to-4-1-1-and-now-dns-service-wont-start/15329/10 "2019-01-11T21:34:42Z")

</div>

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.